I received compile errors when doing a FIMS upgrade. What do I do?

I just completed a FIMS upgrade and during the compile process of the upgrade it said there were errors.
Troubleshooting Upgrade Compile Errors

1. Make sure all other users are logged out of FIMS
2. Be sure that the Assemblies in \npo\found\fims\assemblies are copied to \npo\found\assemblies if they were not already.
  • If you are unable to copy these files it could be because the files are in use and locked. If that is the case, you can either go to system shared folders in Computer Management and clear the locks, or you can reboot the server which will clear all locks.
  • Additionally, after copying the files, you may have to right-click on the DLL files in the Assemblies folder, choose Properties and select Unblock
  • If you are using Progress OE 11.x you may see the error "save-into: .\Prog11\gui\eadvisor" which indicates an issue with the DLL files being locked
  • If the Windows user running the upgrade does not have full rights to the Assemblies folder you will need to right-click on FIMS and Run as Administrator.
3. In 14.60, there is a bat file named CheckCasPol that checks to see if FIMS and dlc\bin has full trust for assemblies. Check and make sure that CheckCasPol shows full trust for FIMS and dlc\bin for assemblies on the drive where FIMS is installed.

4. Log back into FIMS and re-compile and make sure no errors. Go Tools\System Utilities\Admin Utilities\FIMS Compiler and click Compile.

If you still get errors after doing the above steps, do the following:

Identify the errors received during the compile.  The errors are recorded in the following file which can be opened in Notepad:
\npo\found\fims\fcompile.err


For compile errors the most important thing to look at is the root error (see example below):
** Error Compiling D:\data\npo\found\fims\custom\fm-old\62697SRC\fm_profa.p
    ** Error=Unknown or ambiguous table fm_profile. (725)
    ** Error=** d:\data\npo\found\fims\gui\udsys\udtriga.i Could not understand line 88. (198)
So the two errors below it are associated directly with that root file/error and if we take care of the root error/file then the ones below it will follow.


-------------------------------------------------------------------------

I. Compile Error with APCHKPRT.P
** Error Compiling F:\npo\found\fims\gui\AP\APCHKPRT.P
    ** Error=**FILL-IN Address1 will not fit in FRAME check-line in PROGRAM F:\npo\found\fims\gui\AP\APCHKPRT.P. (4028)
  1. In FIMS, go to Tools > System Utilities > System Options, and check AP > CheckForm to make sure you have something other than <None> selected.
    1. If they do have a CheckForm specified, go to the folder "npo\found\fims" and create a new folder called "custom-old" if it doesn't exist already.
    2. Go to the folder "npo\found\fims\custom" and move all the files that start with “apchk” to the "custom-old" folder you just created.
    3. Recompile gui\ap\apchkprt.p
  2. If you have <None> specified in System Options, you will need to select the proper check form from the Lookup button that will work with your checks.

II. Compile Errors for files located within the Custom (npo\found\fims\custom) folder:
Files/Folders containing the word OLD
Any file with a filename "-old" or "old" in it can be deleted and ignored.  The same goes for any folder and the files within that folder.

Files/Folders containing the word COPY
Any file with a filename "- copy" or "copy" in it can be deleted and ignored.  The same goes for any folder and the files within that folder.


III. FieldMaker:
In the past, a common troubleshooting step with FieldMaker issues was to rename the FM folder in the Custom folder to "fm-old".  Then recreate the fm folder within FIMS.  This then would resolve the FieldMaker issue.  The fm-old folder was sometimes left.  This folder and the files within will then cause compile errors.  The folders and files are obsolete and unused by FIMS thus causing the compile errors.  The folder just needs to be deleted.

Example:
** Error Compiling D:\data\npo\found\fims\custom\fm-old\62697SRC\fm_profa.p
    ** Error=Unknown or ambiguous table fm_profile. (725)
    ** Error=** d:\data\npo\found\fims\gui\udsys\udtriga.i Could not understand line 88. (198)


IV. Test Files:
Any file with a developers name in it is fair game that it was created for troubleshooting purposes.

Examples:
** Error Compiling C:\npo\found\FIMS\gam\jane\showEmail.p
  • This is a file inside a folder called "jane".  This is a folder that was created by Jane while troubleshooting an issue and was forgotten & not removed.  This file is not used by FIMS and shouldn't be.  The compiler is trying to use it and causing an error.  We should and can safely delete this "jane" folder and all contents within.
 
** Error Compiling C:\cfdata\fims\npo\found\fims\sf\SFSyncer - Copy.p; save-into: .\Prog11\sf
  • Here someone has created a "copy" of the SFSyncer.p file and forgot to remove it.  Windows automatically names a file "XXXX - Copy" when making a copy.  The FIMS application doesn't use these files.  We should and can safely delete this "SFSyncer - Copy.p" file.

** Error Compiling C:\cfdata\fims\npo\found\fims\sf\TOOLS\SFbob.p; save-into: .\Prog11\sf\TOOLS
  • Here's an example of another file that was created or copied for troubleshooting and not removed after completion.  The file SFbob.p is not a program that FIMS uses and can be deleted.


NOTE: In all these cases above you could create a "temporary" location to put these files if you don't feel safe deleting them.  For instance, create a temp folder on the desktop and move the files/folders there.  In time if no errors are encountered using FIMS then you have verification that those files were not being used and had no function.

Environment

 FIMS

Was this article helpful?