Kbase P27446: What are the possible reasons for error 51 occur related to r-code issues
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/17/2010 |
|
Status: Verified
GOAL:
What are the possible reasons for error 51 occur related to r-code issues
GOAL:
How to find the cause of erro 51
GOAL:
SYSTEM ERROR: sizditm -- invalid type. (51)
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
There are several reasons the erro 51 occur including:
1) The compiled (.r) file is corrupted in memory.
2) The compiled (.r) file is corrupted on disk.
3) The compiled (.r) file was compiled under a version of Progress different from the version you're using to run it.
To narrow down these possibilities we suggest:
1) Leave PROGRESS session, re-enter and run the same procedure(s) again to see if the compiled (.r) code is only corrupt in memory.
2) If the same error occurs again, then the compiled (.r) code. If this solves the error the cause was .r corrupt on disk.
3) Also verify if the compiled (.r) file was compiled under a different version (you may also want to check the patches level), or if the compiled (.r) file was compiled under a different operating system. In this case, the .r code may be incompatible with your PROGRESS or operating system version.
Note that if there are other r-codes being called by the r-code being executed the corruption/incompatibility might not be in the calling r-code but the called r-code.
Aso note that if the code fire triggers (user defined or database triggers) the called r-codes may include these triggers too.