Informix Error -1229
-1229 Incompatible message file.
4GL is trying to look up a message text in a message file, but the file contents do not match the current version of the product. Possibly the file is corrupt; possibly a message file from a prior version is present. The file has a suffix of .iem and exists in the etc subdirectory of the path that the INFORMIXDIR environment variable identifies. Reinstall such files from the distribution materials. If you have started to modify the user-message file, 4glusr.msg, make sure that you are recompiling it with a current version of the mkmessage utility.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-1229 fires when 4GL looks up a message in a .iem file whose contents don't match the current
product version — per the official guidance, this is the 4GL-runtime equivalent of -1122's
form-level case, typically from file corruption or an outdated file left over from a previous
product version.
- A corrupted
.iemmessage file, per the official guidance's named possibility. - An outdated
.iemmessage file from a previous product version, per the official guidance's other named possibility.
Solutions / Resolution
- Reinstall these files from the original distribution materials, per the official
guidance — the
.iemfiles live in theetcsubdirectory referenced byINFORMIXDIR. - If
4glusr.msgwas modified, recompile it using the currentmkmessageutility, per the official guidance.
Examples
Recompiling with the current mkmessage
$ mkmessage 4glusr.msg 4glusr.iem
Diagnostic Checks
- Check the
.iemfiles under$INFORMIXDIR/etcfor corruption or an outdated version, and reinstall or recompile as needed.
Related Errors / Related Topics
- -1122 — "Incompatible message file." A related error, at the form-level
OPTIONS HELP FILElayer rather than 4GL's own runtime message files. - -1227 — "Message file not found." A related error, about the file being missing entirely.
- -1228 — "Message number not found in message file." A related error, about a specific number missing from an otherwise-valid file.
The .iem message file's contents don't match the current product version — reinstall from
distribution materials, or recompile a customized 4glusr.msg with the current mkmessage.