Kbase 3915: Errors that mean you may have a corrupt .r file
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/12/2002 |
|
Errors that mean you may have a corrupt .r file
900717-gfs01
INTRODUCTION: Date Last Modified: 8/24/90
=============
This Product Service Knowledgebase entry describes errors that indicate
you have corrupt compiled (.r) code.
PROGRESS ERROR NUMBER: PROGRESS ERROR TEXT:
====================== ====================
8 Unsupported r-code operation
58 fmconv - bad source type
51 sizditm -- invalid type
POSSIBLE CAUSE OF ERROR:
========================
There are several reasons these errors may occur:
1) The compiled (.r) file is corrupted in memory.
2) The compiled (.r) file is corrupted on disk.
2) The compiled (.r) file was compiled under a version of Progress
different from the version you're using to run it.
DOES ERROR INDICATE CORRUPTION: IF SO, WHAT TYPE:
=============================== =================
Probably Object (.r) file
CORRECTIVE MEASURES:
===================
Leave PROGRESS, re-enter and run the procedure(s) again to see
if the compiled (.r) code is only corrupt in memory.
If the error occurs again, then the compiled (.r) code is most likely
corrupt on disk. Recompile the procedure(s).
If the compiled (.r) file that you are running was compiled under a
different version (check the patches level), or if the compiled (.r) file was compiled under a different
operating system, the .r code may be incompatible with your PROGRESS or
operating system version. You need to recompile in your environment.
ONLINE PROCEDURES OR UTILITIES:
===============================
UNIX 'sum' utility - used to indicate if a file is corrupt.
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
PROGRESS Reference Manual - Compile statement
Progress Software Technical Support Note # 3915