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 running Windows in a networked environment. The workstation must have TCP/IP installed and configured.

Note that there are additional steps for setting up FIMS on a Terminal Server, for that see the following for Progress 10:

See the following for setting up a terminal server or remote desktop server for Progress 11:

1. Map a Network Drive
  1. Right click My Computer and choose Map Network Drive.
  2. Drive = N
  3. 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).
  4. Make sure Reconnect at Logon is checked.
2. FIMS shortcut
  1. Double click My Computer.
  2. Double click N drive.
  3. Right click the New FIMS Shortcut and choose Send To > Desktop.
3. FIMS Workstation Setup.exe
  1. Find the FIMS Workstation Setup.exe on the FIMS Server (normally in npo\found\fims)
  2. Click to run
  3. 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.
4. Resolving Control Frame widget errors – register 2 files. You must do these steps under a Windows account that has full admin rights.
1. Log out of the workstation
2. Log into the workstation as the Administrator
Note: even if the user is an administrator, log out as the user and log into the workstation as the local Administrator
3. Click Start > All Programs > Accessories and right click the Command Prompt
4. Choose Run as Administrator
5. Type in the following 2 commands separately
Regsvr32 n:\dlc\bin\prox.dll
Regsvr32 n:\found\fims\tview4gl.ocx
6. You will receive a pop up that states each was successful.

If you get an error message then do the following (otherwise skip to step 5):
  1. Copy the two files (n:\dlc\bin\prox.dll and n:\found\fims\tview4gl.ocx) to the c:\windows\sysWOW64 folder if the machine in question is 64bit. If the machine in question is 32bit then copy those DLLs from the N drive to C:\Windows\System32
You can determine if the machine with the issue is 32bit or 64bit by right-clicking Computer and then selecting Properties. Under the System section, you will see a area labeled System type. It will either say 32-bit Operating system or 64-bit Operating system.

      2. Open a command prompt window being sure to right-click and run the command prompt window as administrator
      3. Type in the following 2 commands separately

For 64 bit machines:
Regsvr32 c:\windows\syswow64\prox.dll
Regsvr32 c:\windows\syswow64\tview4gl.ocx
For 32 bit machines:
Regsvr32 c:\windows\System32\prox.dll
Regsvr32 c:\windows\System32\tview4gl.ocx

     4. You will receive a pop up that states each was successful.

5. Resolving .NET Assemblies Errors. You must do these steps under a Windows account that has full admin rights.
1. Open a command prompt and run as administrator.
Type: N:
2. If you receive an error:
Type net use n: \\{server-name}\npo
Type: N:
Type: cd\found\fims\tools
Type: reports.bat n:\dlc\bin\* n:\found\assemblies\* reports.log
Type: type reports.log
If you see the message “Added union code group with “-url” membership condition to the Machine level. Success” then the errors should be resolved.
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.
6. (Optional) Resolving errors running Graphical Reports
  1. In FIMS, select:  Tools > System Utilities > Run Procedure
  2. Click Browse and open N:\found\FIMS\TOOLS\loadClrRegardless.p
  3. Click OK to run the process
  4. Log out of and back in to FIMS
  5. Run the graphical report If the error persists, ensure the workstation has Microsoft .NET v2.0.50727               
  6. In Windows Explorer, verify ‘C:\Windows\Microsoft.NET\Framework\v2.0.50727’ exists               
  7. If the folder does not exist, open N:\dlc\install\3party and run dotnetfx.exe                -
  8. When installation is complete, log in to FIMS and run a graphical report.
FIMS Setup for a New Workstation.docx


 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

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.