Error You May not Compile Programs that Update the Database in this Version 490 when updating FIMS
- 16 Apr 2024
- Contributors
- Print
- DarkLight
- PDF
Error You May not Compile Programs that Update the Database in this Version 490 when updating FIMS
- Updated on 16 Apr 2024
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
When updating FIMS the error, "You may not compile programs that update the database in this version (490)" occurs at the end of the compilation process.
Answer:
This can occur if the programs that are being compiled are not encrypted. This can also occur if there are .r files missing in the file pathway where the error occurs which means that the .i files were not compiled.
To resolve this error, do the following:
Solution A:
Check the files mentioned in the errors to see if they are encrypted. If you open them in notepad and you see odd, unreadable characters, that means it is encrypted. If the file is readable in plain English, that means its not encrypted.
See the following article on encrypting files.
Error This version of PROGRESS compiles only encrypted programs
Solution B:
Check the file pathway listed in the error messages. If you are getting these errors in .p or .w files it means that the .i files that are also getting errors were not compiled. You should see .r files in the pathway where the errors are, if not, then the .i files were not compiled.
For example, let's say you were getting these errors below. Three of these are .i files, but the key file is the .w file. If you look in fims\app\profiles, you most likely would see that there are no .r files which means that the .i files in the other messages were never compiled.
To resolve these errors in this specific example, you would compile the APP folder and then after that the errors should go away. You will need to look at the pathway of your .w or .p errors to know which area to recompile:
Go to Tools\System Utilities\Admin Utilities\FIMS Compiler, then click Compile. If you do not know which folder to compile, then you can go ahead and just compile all folders.
In the case of the specific errors below, we are only going to compile APP because the Profiles folder is within that folder which was shown in the error message:
To resolve this error, do the following:
Solution A:
Check the files mentioned in the errors to see if they are encrypted. If you open them in notepad and you see odd, unreadable characters, that means it is encrypted. If the file is readable in plain English, that means its not encrypted.
See the following article on encrypting files.
Error This version of PROGRESS compiles only encrypted programs
Solution B:
Check the file pathway listed in the error messages. If you are getting these errors in .p or .w files it means that the .i files that are also getting errors were not compiled. You should see .r files in the pathway where the errors are, if not, then the .i files were not compiled.
For example, let's say you were getting these errors below. Three of these are .i files, but the key file is the .w file. If you look in fims\app\profiles, you most likely would see that there are no .r files which means that the .i files in the other messages were never compiled.
To resolve these errors in this specific example, you would compile the APP folder and then after that the errors should go away. You will need to look at the pathway of your .w or .p errors to know which area to recompile:
Go to Tools\System Utilities\Admin Utilities\FIMS Compiler, then click Compile. If you do not know which folder to compile, then you can go ahead and just compile all folders.
In the case of the specific errors below, we are only going to compile APP because the Profiles folder is within that folder which was shown in the error message:
Solution C:
If the file paths in the error message reference FieldMaker folders, for example found\fims\custom\fm\, then recommitting FieldMaker should resolve the issue. To recommit FieldMaker go to Tools > System Utilities > FieldMaker Configuration > Processes tab > Commit changes and click Run Now.
Once the compiler completes test the process that was originally generating the error message.
If the file paths in the error message reference FieldMaker folders, for example found\fims\custom\fm\, then recommitting FieldMaker should resolve the issue. To recommit FieldMaker go to Tools > System Utilities > FieldMaker Configuration > Processes tab > Commit changes and click Run Now.
Once the compiler completes test the process that was originally generating the error message.
If the steps above do not resolve the issue. Copy and zip up the custom and custom src folders and send to support.
Was this article helpful?
