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. How do I fix those? 

Answer:

A. Troubleshooting Upgrade Compile Errors
 
 1. Re-run the upgrade following the steps in this article before running:
Recommended Practices for Upgrading FIMS to the Latest Version
 
 2. If you still get errors, do the following:

a. If you are running a FIMS patch, right click on the FIMS shortcut and run as administrator then run the patch again. Many times, when running as admin errors will not occur.

b. If you are running a full upgrade on the server, be sure that you are logged into the server with an admin account and also right-click on the installer and run as administrator.

c. Check and make sure that the DLLs are not blocked.

• Go to \npo\found\Assemblies and npo\found\FIMS\Assemblies.
• Right-click on the DLL files in those folders, choose Properties and select Unblock.
• There is no way to mass do this, you will have to go to each file and see if it is blocked. Once you un-block any files that were blocked, run the upgrade again and see if the compile errors go away.
• 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

d. Run the bat file named CheckCasPol located in npo\found\FIMS that will check 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.

e. Check and see if there is anything in the Custom folder located in \npo\found\FIMS\custom that may be interfering with the compile process.

• These would be any files relating to any of the compile errors. Take note of the files in that folder.

f. Check the Propath in the FIMSNT.ini file location in npo\found\ConfigFiles and make sure there are no non-standard paths or folders listed there.
 
 g. Make sure that the FIMS shortcut on the server or workstation is configured correctly. 

• If you are doing a full upgrade, then you would be running that on the FIMS database server so as such you check the FIMS shortcut on the server. 
• If you are running a patch, you are probably running that on a workstation and then in that case you would check the FIMS shortcut on the workstation.
   
  How do I create a FIMS shortcut on a workstation, terminal server or the database server?

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

 1. Identify the errors received during the compile.

• The errors are recorded in the following file which can be opened in Notepad. Be sure to sort the columns by date modified to get the most recent file:

                       \npo\found\fims\fcompile.err

 2. Common Compile Errors

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)

• In FIMS, go to Tools > System Utilities > System Options, and check AP > CheckForm to make sure you have something other than <None> selected.
• 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.
• 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.
• Recompile gui\ap\apchkprt.p
• 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.

2. 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.
   

c. FieldMaker compile errors

• 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)

d. Test Files compile errors

• Any file with a developer’s 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.

e. Errors with copied files

 ** 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.  

If you have any questions on these steps, it is best to create a support case.