Error Messages

The Calais Web Service response may indicate errors in submission or processing stages.

Error messages will be returned as an XML response in the following format:

<Error Method="ProcessText" CalaisSessionID="(Session ID here)" CalaisVersion="(Version Number here)">
<Exception> (Error Message Here) [SID= (Session ID here)]</Exception>

</Error>

If you find it necessary to report errors, please include the calaisRequestID, which will help us investigate the problem.

Error messages are summarized here:

Error Message Description
Illegal Content-Type. The field content type (file extension – like XML, txt, HTML, etc.) is not known and includes characters that are forbidden in file name.
paramsXML is invalid. The params XML is invalid format. Either it is a NULL string or not legal XML string.
Missing a mandatory paramsXML item. Specifically - The content type in the Params XML is missing.
Length has exceeded the allowed size. For content it is limited to 100,000 characters.
Calais Backend-Server is Busy. Please try again later. The Calais tagging server is not responding. Try resubmitting the document.
Calais Backend-Server has accepted the document and has already started to process it, but was unable to finish its processing within the time limit. The timeout is 25 seconds. The message will include the internal resource ID of the document as it is stored in Calais.
Error while communicating with Calais Backend-Server. Error in the Calais tagging server. The error message returns also the internal module name that caused the problem.
Document conversion error. Please make sure that the content-type (passed through the paramsXML) matches this document contents. The actual content sent to Calais does not match the type of content specified in the content type field. Or the content string is NULL.
Internal Calais Backend-Server Error. Internal error in the Calais tagging server.
Calais Backend-Server has accepted the document and has already started to process it, but was unable to finish its processing within the time limit. Processing timeout; large documents (above 80K may reach the timeout)
Provided content has a wrong format. The exception occurs in case of SOAP serialization-deserialization error, for example when the user submits binary content such as PDF.

Back to Top