Error Codes - trillium_quality

When processing errors occur, the SOAP response includes a numeric error code and a text value for that code. For example:

<ax21:trilliumField>ECS_ERROR_MESSAGE</ax21:trilliumField>
<ax21:trilliumValue>Trillum[4401]: Trillium Cleanser or Matcher 
Service Not Available (check Service and/or SystemID/
ServerName).</ax21:trilliumValue>

Table 1. Error Codes
Code	Description
1	Invalid state for request. Matcher session was either never opened or was closed.
2	A street name failure.
6	Out of memory.
7	A line within the field list parameter is missing a description keyword. For example, this code will be returned if the following line: `zip_code scores(100) routines(absolute) fldnames(pr_gout_postal_code)` is missing the word zip_code.
9	The Cleanser was not able to identify the country and it has defaulted to the first one in the list.
102	Unable to attach to the Director. This can occur: If the Director is not running. If the TRILLDIRADDR and TRILLDIRPORT environment variables are not set correctly on the client. If the network connection between the client and server machines is down.
110	Director time out (Linux). This may be caused by a large match window or matcher performance.
145	Linux network error. Connection timed out. The client sent a request to the Director and did not get a response within 10 seconds. You can find this documented in the errno.h file on your server, which should be in a folder such as /usr/include/sys/errno.h.
146	(Linux) The machine on the other end abnormally terminated the connection. Possible causes include: The user turned off or rebooted the system while being connected. The Cleanser or Matcher server is configured to use a different port than the one specified by the Director. The Cleanser went down but the Director is up.
201	The TRILLCONFIG variable is not set.
705	The number of records added to the match window has exceeded the maximum window size.
706	This error can occur if: AddToMatchWindow calls do not use the same list of field names, or the fields are not in the same order. A MatchCandidate call does not use the same field names or field order as those used in the AddToMatchWindow call. When processing an XML request, the name and value tags are reversed. The name and value tags must be the attribute name of the match field and the value for the field, respectively. An element is missing from an XML request, for example, a < is missing in a tag, or a closing tag is missing.
4401	The client application was able to find the Director, but it was not able to locate the Cleanser or Matcher service. This can happen if: The Cleanser or Matcher service is not running. The System ID or the Server Name specified in the client's application does not match what the Cleanser or Matcher is using. The network connection between the Director machine and the Cleanser/Matcher machine is down. The server is currently processing the maximum number of concurrent requests.
5000	One or more parameters are null (not passed in SOAP message).
5001	One or more parameters are invalid (check all parameters).
5002	Exception during processing (check logs).
5003	Project is not available (see your Trillium Administrator). Check to ensure that you have specified the correct project name.
5004	Project specified is not running (see your Trillium Administrator).
5900	Invalid Web Key - Access Denied (see your Trillium Administrator).
5901	Max Request Limit Web Key Reached - Access Denied (see your Trillium Administrator).
5902	Web key is disabled - Access Denied (see your Trillium Administrator).
10048	ListenOnSocket returned an error.
10054	Connection terminated. The most common cause is that the server terminated.
10060	Network timeout. The most common cause is that a server terminated.
65525	The Cleanser or Matcher encountered a memory access error.
65526	The Cleanser or Matcher encountered a data type misalignment.

Error Codes - trillium_quality - 17.2

Trillium TS Web Services Developer Guide