Contents x
    Error This version of PROGRESS compiles only encrypted programs
    • 28 Feb 2023
    • Contributors
    • Print
    • Dark
      Light
    • PDF
    Contents

    Error This version of PROGRESS compiles only encrypted programs

    • Updated on 28 Feb 2023
    • Contributors
    • Print
    • Dark
      Light
    • PDF
    Article summary

    When compiling the FIMS database or doing other tasks in FIMS after a Progress 11 upgrade, the following error may occur "This version of PROGRESS compiles only encrypted programs" 

    Answer:
    This error occurs due to the files referenced in the error messages being in clear ASCII text rather than being encrypted.

    For example, let's say you see the following compile error. Your error may be a different path and different file, this is just an example for an error with a custom file.

    ** Error Compiling npo\found\FIMS\Custom\gui\ap\custchk.i
       ** Error=This version of PROGRESS compiles only encrypted programs. (1086)

    This error is telling us that the custchk.i file located in custom\gui\ap is clear text and as such, Progress 11 cannot compile un-encrypted files therefore the error will occur. To double check, you can open the file in question, which is in this example the 'custchk.i' file in Notepad and see if it is in clear text, it most likely will be since you are getting the error message.

    To resolve these errors, do the following. The example below is just for when you have an error that references Custom, your error may reference a different path. If your error file pathway does not refer to the custom folder, do not encrypt the file into custom. Again this is just an example for when you have an error that references the Custom folder.

    1. The first step to resolving this error would be to look at the root of the error, meaning the root folders to determine where the encrypted file needs to go:
    • In this example we know that the file located in the pathway below needs to have an encrypted file rather than the un-encrypted one:
    This is the root folder structure:
               npo\found\FIMS\Custom\gui\ap

               This is the file name:
      custchk.i

    2.     The second step will be to remove the un-encrypted file from the pathway listed in the error, which in this example is npo\found\FIMS\Custom\gui\ap. Remove the file and place it into \npo\found\FIMS\customSRC\gui\ap.
    • Move the clear text 'custchk.i' file from custom and place in the CustomSRC\gui\ap folder. You will need to create the gui and ap subfolders if you do not have them in CustomSRC.
    • The reason why we are moving the file that was listed in the error message is that the encryption utility we will be using will not work if the clear text file is still in the original pathway that was listed in the error message, meaning that the utility will not overwrite the encrypted file over the non-encrypted one so you have to move it out first then the utility will write an encrypted version of that file into the location that you indicate.
    3. Go to Tools\System Utilities\Run Procedure
    4. Run the following, note your NPO folder may be somewhere else on your server besides C: If you are running from a workstation, then the path will be the shared N drive:

    npo\found\FIMS\GUI\Tools\d-BuildFIMS.w

    5. You will see the following window appear: 

    6. Leave the radial button set for 'Protect One File' then search for the file in question that needs to be encrypted which will be one of the files listed in the error messages that appeared on your screen while doing a function in FIMS or while compiling.

    Using our same example from above, we are choosing the 'custchk.i' file located in customSRC\gui\ap and then the utility will put the encrypted version of the file in custom\gui\ap which is the destination folder:

    Notes:
    • If you have multiple errors, you will run this again each time for each file. Do not use the options to Protect Whole folder or Complete Build.
    • The utility will not work if there is a clear ASCII text file with the same name in the destination folder. If you do find that there is a clear text file in the destination folder you will need to move it per the instructions in step 2.
    • As an added precaution you also may want to verify if a newer version of that clear text file exists somewhere in a backup folder that was done during an upgrade or something similar. You will want to check the dates on the files and use the most recent to move to the CustomSRC to then encrypt into Custom. Again though, no clear text files can be in Custom.
    • If the file being protected is a .p or .w file then the utility will prompt to compile that file immediately. If you protecting a .p or .w file be sure to delete any backups of those files first. Many times those .p. or .w file backups will be located in the found\fims folder and will be renamed including old, copy, save, etc.:
    What this utility is doing is taking the un-encrypted file, creating an encrypted version of that same file and then placing it in the file pathway that you are indicating, again, the file pathway in the error message will tell you where the encrypted file needs to go:

    7. Re-compile the Custom folder to see if errors disappear. In this example, you can just re-compile Custom as below. We are compiling just custom for this example, your file may be different and may not be located in Custom, it may be elsewhere as such you would need to compile different folders according to where you placed your encrypted file: 


    Was this article helpful?
    What's Next