Specified Active X Control is not Registered or the .ocx File was Moved from where it was Registered

Typically, this issue occurs if FIMS was not run as admin for the first time on a workstation. After FIMS is setup on a workstation, the first time it is run the user needs to right-click and run as admin.

In order to run FIMS as admin you need to be logged into the computer with a Windows account that has local admin rights.

If you get an error running FIMS as admin, see the following:
Unable to Open Message File PROMSGS when Right Clicking and Running FIMS as Administrator

 If for some reason you cannot run FIMS as admin, here is how you can fix the Active X Control error:

1. Log into the workstation that has the Control Frame error with a Windows account that has full Administrator rights.
2. Go to the shared N drive (NPO) on the computer. If the admin account does not have the N drive mapped, you will need to map it to have access to it.
3. Go to n:\dlc\bin
4. Find the 'prox.dll' file
5. Right-click on the 'prox.dll' file and click copy. Do not cut the file out of this location.
6. Right-click anywhere on the desktop of the computer and click Paste in order to paste the 'prox.dll' file to the desktop of the computer that has the Control Frame error.
7. Go to n:\found\fims
8. Find the 'tview4gl.ocx' file
9. Right-click on the 'tview4gl.ocx' file and click copy. Do not cut the file out of this location.
10. Right-click anywhere on the desktop of the computer and click Paste in order to paste the 'tview4gl.ocx' file to the desktop of the computer that has the Control Frameerror
11. Verify what operating system (OS) the workstation that has the Control Frame error has:

• 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.
• In Windows 10 you would search for 'This PC' in the search function to the right of the Windows button on the bottom left of the computer. Then you would right-click on 'This PC' and select properties. See the System type sub-section in the System section you will see either 32 bit or 64 bit.

12.  Now that you have determined what OS the computer with the Control Frame error has, you will now Cut and Paste the two files that you saved on the desktop of the workstation (prox.dll and tview4gl.ocx) to the appropriate folder.

• If you have determined that the workstation is a 64 bit system then cut both files from the desktop and paste into C:\Windows\SysWOW64
• If you have determined that the workstation is a 32 bit system then cut both files from the desktop and paste into C:\Windows\System32

13. Run Command Prompt as Administrator

• In Windows 10 click the Windows button on the bottom left of the computer and go to the Windows System folder or you can just type in Command in the search function to the right of the Windows button.
• You will see Command Prompt show in the search results
• Right-click Command Prompt
• Choose Run as Administrator

14. Register the 'prox.dll' file:

• If the OS of the workstation that has the Control Frame error is 64 bit type this command into the Command Prompt window and then press Enter on the keyboard.

                           Regsvr32 c:\windows\syswow64\prox.dll

• If the OS of the workstation that has the Control Frame error is 32 bit type this command into the Command Prompt window and then press Enter on the keyboard

                          Regsvr32 c:\windows\System32\prox.dll

You should receive a pop up that states the operation was successful.


15. Register the 'tview4gl.ocx' file:

• If the OS of the workstation that has the Control Frame error is 64 bit type this command into the Command Prompt window and then press Enter on the keyboard.

                             Regsvr32 c:\windows\syswow64\tview4gl.ocx

• If the OS of the workstation that has the Control Frame error is 32 bit type this command into the Command Prompt window and then press Enter on the keyboard.

                           Regsvr32 c:\windows\System32\tview4gl.ocx
 

You should receive a pop up that states that the operation was successful.

16. Close FIMS and re-open it, and navigate through the modules, the error should no longer occur.