How do I setup/install FIMS up on a new workstation?

The following instructions are for setting up FIMS on a workstation running Windows in a networked environment. The workstation must have TCP/IP installed and configured.
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
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.
  2. Then in the command pompt window:
  3. Type in the following 2 commands separately
  4. Regsvr32 c:\windows\syswow64\prox.dll
  5. Regsvr32 c:\windows\syswow64\tview4gl.ocx
  6. You will receive a pop up that states each was successful.
5. Resolving .NET Assemblies Errors
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.
I have seen that a user account in a company setting with higher security settings will have to login to the workstation with a local administrator and launch FIMS (get error) then close out of FIMS.  Then on re-entry they will not receive the error anymore on any user on that workstation.
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?