Oninit
Talk to an expert →

Informix Error -408

-408 Invalid message type received from the sqlexec process.

This internal error indicates a problem in the communication between the database server and the library functions that call it. Make sure that your program software is compatible with the database engine in use.

This error can also occur if the CSM option is enabled on the database server side but not on the client application side, or vice versa. If you want to use a CSM, make sure that the CSM option is set in the sqlhosts file for both the database server and client application.

This error can also occur if the confidentiality option of the CSM is enabled on the database server side but not on the client application side, or vice versa. If you want to use the confidentiality option of the CSM, make sure that the confidentiality option is set for both the database server and client application. Check your sqlhosts file and CSS configuration file.

If the error recurs, note all circumstances and contact IBM Informix Technical Support.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-408 is another internal client/server communications error, but with a specific additional cause beyond the usual version mismatch covered by -407/-368: mismatched CSM (Secure Communication Module) settings between server and client, or inconsistent confidentiality options within the CSM configuration, can also trigger it.

  1. A client library incompatible with the connected server version — the same general root cause as -407/-368.
  2. Mismatched CSM settings between the server and client — one side configured for a different secure-communication module or mode than the other.
  3. Inconsistent confidentiality options within the CSM configuration — a specific configuration-file consistency issue rather than a simple on/off mismatch.
  4. Divergent CSM configuration across the sqlhosts file and the CSM's own configuration file (CSS) — the two need to agree with each other, not just be individually valid.
Solutions / Resolution
  1. Verify client/server software compatibility first, per the official guidance, as with -407/-368.
  2. Check CSM settings on both server and client for consistency — same module, same mode.
  3. Ensure uniform CSM configuration across the sqlhosts file and the CSS configuration file, per the official guidance — a mismatch between these two specific files is called out directly as a cause.
  4. Review confidentiality options within the CSM configuration for internal consistency.
Examples
Checking CSM configuration consistency
-- Compare the CSM entry/options in sqlhosts against the
-- corresponding entry in the CSM's own configuration file (CSS)
-- to confirm they agree — a mismatch between these two files is
-- a specific documented cause of this error.
Diagnostic Checks
  1. Confirm client/server software compatibility.
  2. Compare CSM settings between server and client.
  3. Compare sqlhosts CSM entries against the CSS configuration file for consistency.
  4. Check confidentiality options within the CSM configuration for internal consistency.
Related Errors / Related Topics
  • -407 — "Error number zero received from the sqlexec process." A closely related internal communications error, in the same general client/server-protocol family.
  • -368 — "Incompatible sqlexec module." Another related client/server version-mismatch error.

If client/server versions already match, check CSM (Secure Communication Module) configuration consistency next — specifically between the sqlhosts file and the CSS configuration file, which is a documented specific cause of this error.