How do I setup FIMS on a New Workstation or Terminal Server?

The following instructions are for setting up FIMS on a workstation\terminal server\remote desktop server running Windows in a networked environment. The workstation must have TCP/IP installed and configured. Note that FIMS does not actually get installed anywhere but the database server. Workstations\TS\RDS operate FIMS from the shared network folder; the N (NPO) drive.

Note that there are additional steps for setting up FIMS on a terminal server\remote desktop server, for that see the following for Progress 11 which is the current recommended version of Progress:

https://kb.blackbaud.com/articles/Article/121344


 
1. Map a Network Drive
  • Right click My Computer and choose Map Network Drive.
  • Drive = N
  • Folder: = \\servername\npo - servername = the name of the server.  If you do not know the name of the server, go to a workstation that has FIMS and look at the N drive in My Computer. It will say NPO on xxxx (xxxx is the name of the server).
  • Make sure Reconnect at Logon is checked.
 
2. Create FIMS shortcut
  • Double click My Computer.
  • Double click N drive.
  • Right click the New FIMS Shortcut and choose Send To > Desktop. 
There is usually a shortcut to FIMS in your npo folder. (usually mapped as the N: drive on workstations or terminal servers. On the database server itself it would be the absolute path on the server like C for example) If it is not located there, then you should be able to find it in the "found" folder. 
 
See the following article for more detail:
https://kb.blackbaud.com/articles/Article/104533
 
3. FIMS Workstation Setup.exe
  • Find the FIMS Workstation Setup.exe on the FIMS Server (normally in npo\found\fims).
  • Click to run
  • This installer checks for and installs the following required components to a workstation:
Microsoft .NET 3.5
Visual C++ 2005
Adobe Flash Player 10 ActiveX
 Components already installed will display a notification and skip installation.

If you cannot find the FIMS Workstation Setup.exe, you can contact support and the analyst can give you the executable.
 
4. Netsetup (note that if you upgrade Progress to a new service pack or version, you will need to un-install netsetup from the workstation and re-install using the instructions below. See section at the end after the install instructions for how to un-install):

Run NetSetup on the workstation located in npo\dlc\netsetup. DO NOT run this on the terminal server\remote desktop server, this is just for workstations. The netsetup installation is not a full install of Progress, it installs Progress components needed for workstations that run software off of a shared network drive.
 
  • Run the setup.exe located in npo\dlc\netsetup by navigating to the that folder from the shared N drive on the workstation.

 
On this screen, your IT person can decide what is best for your foundation from a security perspective if they would like to grant full trust or not. Many times without granting full trust, the netsetup will function correctly:



On the next screen:
  • Leave the Group Name field the same as it pre-populates.
  • Type the absolute path or browse to find the file to identify as the client-based working directory in the Working Directory field. The Working Directory is a local folder on the workstation in which OpenEdge places the files you create on the client. You will need to create that folder first.
For example, you can create a folder on your local machine called Progress Netsetup. You can place the folder where ever you wish like on the C drive then in the Working Directory field you would navigate to that folder.
 
  • The Network Installation Directory field always appears grayed out, confirming that the information that appears in this field cannot be changed. The pathname that appears in this field identifies two pieces of information: where OpenEdge is installed on the network server and the type of connection that you are using to share the network installation (that is, mapped drive or UNC pathname).
  • Choose Install. As noted above, in the working directory field you would need to browse to the local folder that you created on the workstation, for example, C:\Progress Netsetup. You would click Browse and navigate to your local C drive to that new folder that you created.
  • You may see a series of messages saying files are already in use or something similar, just click Yes to all of those.



To un-install Netsetup from a workstation after a Progress upgrade, do the following:
  • Go to Control Panel\Programs\Programs and Features
  • Find the OpenEdge Shared Network Installation.
  • Choose Change/Remove
  • Remove the installation
  • Be sure to re-install it again now that Progress was updated on the server.
If you have issues un-installing, see the following:
https://knowledgebase.progress.com/articles/Article/21698


5. Resolving Control Frame widget errors. Please see the following article:
https://kb.blackbaud.com/articles/Article/26213

 
6. Resolving .NET Assemblies Errors. You must do these steps under a Windows account that has full admin rights.

On the workstation, close FIMS, then open a Command Prompt being sure to right-click and run as admin:
   
  • In the Command Prompt window, Type: N: (If you receive an error, type: net use n: \\{server-name}\npo )
           You will need to have a space between n: \\
  • Type: cd found\fims\tools
  • Type: reports.bat n:\dlc\bin\* n:\found\assemblies\* reports.log (There should be a space between each argument - it may work best to copy and paste this into the Command Prompt Window.)
  • Type: type reports.log
  • You should see the message “Added union code group with “-url” membership condition to the Machine level.  Success”.
  • Try logging into FIMS on the workstation and see if the issue is resolved now.


NOTE: Many times the message above will say successful but really will not be. If the issue or error messages still occur after doing these steps that means that the Windows account under which these steps were done did not have full permission. You will need to log into the workstation with a Windows account that for sure has full admin rights and then do the steps then test the issue under that admin Windows account meaning stay logged in with that admin Windows account but log into FIMS being sure to right-click and run as admin and then test the issues and errors that were occurring. If the errors now do not occur under the full admin account you can then have the end user log back into the machine with their Windows account and the issues and error messages should no longer occur.

 
7. (Optional) Resolving errors running Graphical Reports
  • In FIMS, select:  Tools > System Utilities > Run Procedure
  • Click Browse and open N:\found\FIMS\TOOLS\loadClrRegardless.p
  • Click OK to run the process
  • Log out of and back in to FIMS
  • Run the graphical report If the error persists, ensure the workstation has Microsoft .NET v2.0.50727               
  • In Windows Explorer, verify ‘C:\Windows\Microsoft.NET\Framework\v2.0.50727’ exists               
  • If the folder does not exist, open N:\dlc\install\3party and run dotnetfx.exe                -
  • When installation is complete, log in to FIMS and run a graphical report.
FIMS Setup for a New Workstation.docx

Environment

 Windows 7 (32-bit);Windows 7 (64-bit);Windows 8 (32-bit);Windows 8 (64-bit);Windows 8.1 (32-bit);Windows 8.1 (64-bit);Windows 10 (32-bit);Windows 10 (64-bit);Windows Server 2003 (32-bit);Windows Server 2003 (64-bit);Windows Server 2003 R2 (32-bit);Windows Server 2003 R2 (64-bit);Windows Server 2008 (32-bit);Windows Server 2008 (64-bit);Windows Server 2008 R2;Windows Server 2012;Windows Server 2012 R2
 FIMS

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.