Oninit
Talk to an expert →

Informix Error -5000: CSM error: <text> </text>

Cause and resolution

CSM error: <text> </text>

A CSM (Communications Support Module), in the database server or in the client, detected an error.

This error code is a general CSM error code. It can be used by individual CSMs to reflect different error conditions. The text provides clues about the possible cause of the error.

If the confidentiality option is enabled for a particular CSM, you might see the following example of this error code: "CSM error: CSM: received message of unexpected type." This implies that the CSM on the user's side (either database server side or client application side) cannot interpret the messages it receives. Make sure that the confidentiality option is set for both the database server and the client application.

Check your sqlhosts file and CSS configuration file. Check the error message on the other side (either database server side or client application side) for more clues about the possible cause of the error.

Also make sure that the CSM you are using is supported by the database server or the client SDK. If the problem persists, contact IBM Informix Technical Support or the CSM vendor. Have the following information available: CSS configuration files and sqlhosts information for both the client and the database server.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-5000 is a general CSM (Communications Support Module) error code — per the official guidance, a CSM in the database server or the client detected an error, and this code is used by individual CSMs to reflect different error conditions, with the embedded text providing clues about the specific cause.

  1. A CSM-level communication error, per the official guidance — the general cause; the embedded text identifies the specific condition.
  2. A confidentiality-option mismatch between the database server and client, per the official guidance — a specific, named example: "CSM error: CSM: received message of unexpected type" implies the CSM on one side can't interpret the messages it's receiving, typically because the confidentiality option isn't set consistently on both sides.
Solutions / Resolution
  1. Read the embedded error text for clues about the specific cause, per the official guidance.
  2. If the confidentiality option is enabled, make sure it's set for both the database server and the client application, per the official guidance.
  3. Check the sqlhosts file and the CSS configuration file, per the official guidance.
  4. Check the error message on the other side (database server or client application) for more clues, per the official guidance.
  5. Confirm the CSM in use is supported by the database server or the client SDK, per the official guidance.
  6. If the problem persists, contact IBM Informix Technical Support or the CSM vendor, per the official guidance, with the CSS configuration files and sqlhosts information for both sides available.
Examples
A confidentiality-mismatch CSM error
CSM error: CSM: received message of unexpected type.

This example, per the official guidance, implies the confidentiality option isn't configured consistently on both the database server and client sides.

Diagnostic Checks
  1. Read the embedded CSM error text for the specific condition.
  2. Check sqlhosts and the CSS configuration file on both the database server and client sides, and confirm the confidentiality option (if used) and CSM support are consistent on both.
Related Errors / Related Topics
  • -4986 — "Communication between fgld daemon and application server was closed." A different communications-infrastructure error, for the web-service publishing daemon rather than a database-connection CSM.

A CSM (Communications Support Module) detected an error — read the embedded text for the specific cause, and check sqlhosts/CSS configuration and confidentiality-option consistency on both sides.