Error: Failed to update FIMS .NET Assemblies configuration on this workstation. ERROR: Runtime error: Access denied. - when trying to launch application

How do I fix this error?
Failed to update FIMS .NET Assemblies configuration on this workstation. 
ERROR: Runtime error. Access denied...
1. Right-click on the FIMS Icon and run as administrator. You may receive the message "msgOpen: Unable to open message file: PROMSGS" when running FIMS as admin. To resolve, see the following:

2. Be sure that the Windows account logged into the computer is a local admin and that the Windows account has rights to install and change folders on the machine.

Other solutions:
On the workstation, close FIMS, then open a Command Prompt with administrator privileges. To do so:
  1. Right click the desktop, go to New > Shortcut.
  2. Enter “cmd” (without quotes) and hit the enter key twice.
  3. Right click on the black “cmd” shortcut on the desktop, and select Run as Administrator.
  4. You may need an Administrator password at this point.  Consult your IT people if needed.
Correcting the Error:

Sometimes Windows updates or operating system upgrades may uninstall the legacy version of Microsoft .NET after installing the latest version 4.X.  FIMS requires the older legacy version Microsoft .NET v2.0.50727.

-You can verify by: in File Explorer, browse to ‘C:\Windows\Microsoft.NET\Framework\v2.0.50727’ and this folder may not exist or be empty

-To reinstall this version in File Explorer, browse to N:\dlc\install\3party and run dotnetfx.exe.  Close the install window when complete.

Then do the following:

  1. 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: \\.
  2. Type: cd found\fims\tools
  3. 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.)
  4. Type: type reports.log
  5. If you see the message “Added union code group with “-url” membership condition to the Machine level.  Success” then the errors should be resolved.
  6. Try logging into FIMS on the workstation and see if the issue is resolved now.
NOTE: Many times the message in step 5 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.



Was this article helpful?