You can obtain the latest FIMS upgrade here:
2. Make sure that the FIMS shortcut on the server has the absolute path to the install directory, not UNC paths. The upgrade installer cannot work with UNC paths.
- You may have a different drive other than C where FIMS is installed on the server.
- If you make a change in the ini file, or the shortcut on the server, you will need to launch FIMS and let the log in screen load so that the FIMS folder is set in the registry to use the new start in folder path and any other path changes that are made. You do not have to actually log into FIMS, the log in screen just needs to appear, you can click cancel after that.
- The upgrade installer looks at the Fimsnt.ini file, not the fims.ini file.
C:\NPO\dlc\bin\prowin32.exe -pf c:\npo\found\configfiles\wfound.pf -ini c:\npo\found\configfiles\fimsnt.ini
\\servername\NPO\dlc\bin\prowin32.exe -pf \\servername\found\configfiles\wfound.pf -ini \\servername\npo\found\configfiles\fimsnt.ini
3. Make sure that the files in the NPO directory are not read-only (the installer will automatically do this and will remove any Read Only Attribute in existing FIMS files).
4. Make sure that the files in the NPO directory are not hidden as this could potentially affect the upgrade if any critical files are hidden.
5. When ready to run the upgrade installer, make sure that no users are logged into FIMS by running the Show Live Users shortcut on the desktop. Instruct users to not attempt to log into FIMS until advised.
6. Make sure all shared files relevant to NPO are closed. Go to Computer Management\Shared Folders\Open Files and make sure that any files in the NPO directory are not open. If they are open, close them.
7. During the upgrade process, note any errors that take place and resolve at that time.
8. After a successful upgrade, make sure that the users right-click and run FIMS as administrator the first time they run FIMS after the upgrade if UAC is turned on on the workstations.
9. Also make sure that both the FIMS version and the DB version are both 14.61; you can view that information in Help\About FIMS. If they both do not say that then that means that the upgrade did not take place correctly.
10. Review the upgrade log in \npo\found\FIMS called fims-upgrades-year.log where year would be the year you ran the upgrade an review that to make sure there were no issues with the upgrade and that all steps completed. At the very bottom of the log, it should read the following, ""tools\upfims.p - UPFIMS.P completed - date and time".
11. Review the FIMS compile log to make sure there were no compile errors located in \npo\found\FIMS called 'FCOMPILE.ERR'.