Kbase P166061: 4GL/ABL: Errors following the 'Unable to read Compiler Messages file' warning checking syntax in Pro
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
14/05/2010 |
|
Status: Unverified
SYMPTOM(s):
4GL/ABL: Errors following the 'Unable to read Compiler Messages file' warning checking syntax in Procedure Editor.
Warning - Unable to read Compiler Messages file
Invalid preprocessor directive '<directive>' inside &IF or &ELSEIF expression. (2943)
Missing &THEN for &IF or &ELSEIF. (2952)
Missing &ENDIF. (2964)
** Preprocessor could not understand line <line-number> in file '<file-name>'. (2124)
** "<file-name>" was not found. (293)
** <program> Could not understand line <number>. (193)
Invalid preprocessor directive 'to' inside &IF or &ELSEIF expression. (2943)
Missing &THEN for &IF or &ELSEIF. (2952)
Missing &ENDIF. (2964)
** Preprocessor could not understand line 38 in file 'äVÁ Ë0 ö'. (2124)
** "ç1¹?t4äVÁ Ë0 ö¿?" was not found. (293)
** "3°?jì Vf2%. Å?ÀÕ %ù«ÊX Could not understand line 41. 193
FACT(s) (Environment):
IBM AIX
OpenEdge 10.1A
OpenEdge Category: Language (4GL/ABL)
CAUSE:
An encrypted include file was corrupted. The offending encrypted include file have been transferred to the server in ASCII mode, instead of BINARY mode.
FIX:
The 'Warning - Unable to read Compiler Messages file' indicates that the compiler encountered a highly unusual situation. This usually occurs due to code corruption or some other unusual circumstance.
Ensure that the source code of the procedure being compiled or syntax checked is not corrupted. When transferring source code to the server using FTP, ensure to binary transfer mode is selected to avoid code corruption.