Text Search Engine reason codes

Text Search Engine can produce error codes and reasons for the error.

0: Operation performed successfully - no error occurred.
1: An invalid handle was passed to a function.
2: Function could not allocate enough memory.
3: Function could not perform due to access limitations or security restrictions.
4: The operation is not supported for this version of the Text Search Engine run time.
5: The operation is currently not enabled.
6: The application violated the Text Search Engine protocol by calling Text Search Engine functions in illegal order.
7: An unexpected error occurred. Please report this to your service representative.
8: An invalid language was specified.
9: The specified language is valid but not supported by the Text Search Engine run time.
10: An invalid CCSID was specified.
11: The specified CCSID is valid but not supported by the Text Search Engine run time.
12: An invalid document ID was specified.
13: The specified document format is valid but not supported by the Text Search Engine run time.
14: An invalid document format was specified.
15: The operation could not succeed due to access limitation during file input/output.
16: The operation could not succeed due to read errors during file input/output.
17: The operation could not succeed due to read errors during file input.
18: The operation could not succeed due to write errors during file output.
19: The operation could not succeed due to seek errors during file input/output.
20: The operation could not succeed due to tell errors during file input/output.
21: The operation could not succeed due to close errors during file input/output.
22: The operation could not succeed due to errors during rename operations.
23: The operation could not succeed due to errors during remove operations.
24: The operation could not succeed due to errors during mkdir operations.
25: One or more function arguments did have an invalid value (for example, an unexpected null pointer or an invalid enumeration type value).
26: The specified directory does not exist.
27: An unexpected Text Search Engine error occurred. Please examine the Text Search Engine error code in the error info object for further details.
28: An unexpected COS error occurred. Please report this error.
29: An attempt was made to update an empty document.
30: The specified argument is not supported for this operation.
31: The date attribute parser found an invalid value when trying to parse a date attribute.
32: The number attribute parser found an invalid value when trying to parse a number attribute.
33: Attribute name invalid, probably too long.
35: Reserve number for future use.
36: The input document contains an attribute (DATE, NUMBER, or STRING) that exceeds the length limit for attributes. The attribute text has been truncated to that limit.
38: The warning threshold as set by the user has been exceeded. As a consequence, this error has been generated.
39: The input document could not be indexed. It contains too many nested fields.
40: The limit of different attributes for one of the attribute types has been exceeded for this index.
46: The iterator is not (or no longer) valid, because its list is empty or deleted.
47: The function is not supported for the passed kind of handle. This error occurs, for example, when trying to use itlQueryResultEntryObtainData on a list iterator that does not represent a query result iterator.
48: This warning is issued if a stop word file cannot be found for the specified language and resource path.
49: This warning is issued if a stop word file does not contain any stop words.
50: This warning is issued if a stop word file does contain invalid data.
100: The index could not be opened because it does not exist with the specified name and directory.
101: The specified index name is not a valid index name.
102: The specified index directory is not a valid directory name.
103: The operation cannot be performed because the Text Search Engine detected a corruption of the index structure or index file sets.
104: The specified index cannot be created because it already exists with the given name and directory.
109: Before any other operation can be performed on this index, a rollback operation must be performed.
110: The index configuration file does not contain the mandatory section as specified in the error context.
111: The index configuration file does not contain the mandatory option as specified in the error context.
112: The index configuration file contains invalid data in the option as specified in the error context.
113: The index configuration file does not match the Text Search Engine version.
200: The specified document model name is not a valid model name.
201: The specified document model field name is not a valid field name.
202: The specified document model is not known.
203: The specified document model already exists and cannot be redefined.
204: Too many or too large document models have been added to the index.
205: The document model contains too many elements.
206: The document model element contains a parameter (XML attribute) that is not allowed for this type of element.
207: The document model element contains a parameter value that is not allowed for this type of parameter (XML attribute).
208: The document model element does not contain a required parameter (XML attribute), like "name".
209: The document model does not seem to be XML, or starts with an unexpected XML element.
210: The given XPath (locator value) contains an unexpected token.
211: The given XPath (locator value) contains an unexpected axis specifier (name followed by two colons).
212: The given XPath (locator value) contains an unexpected node test.
213: The document model directory file (extension .mdx) is corrupted.
214: The document model index file (extension .mox) is corrupted.
215: The document contains an XML element which is mapped to a document attribute and which contains another document attribute. The inner attribute is ignored.
216: The given parameter value is too long as a GPP or HTML tag.
217: The document model contains a duplicate field definition.
218: The document model contains a duplicate attribute definition.
300: The operation cannot be performed because the Text Search Engine detected a corruption in the index files used for document name mapping.
301: The operation cannot be performed because the Text Search Engine detected an invalid document number.
302: The operation cannot be performed because the Text Search Engine detected an invalid document identifer.
303: The operation cannot be performed because the Text Search Engine found no index entry for the document identifier.
304: The operation cannot be performed because the Text Search Engine found no index entry for the document number.
305: The operation cannot be performed because the Text Search Engine detected an overflow in used document numbers.
306: The document identifier that the application tried to index has appeared already in the list of documents. The Text Search Engine does not support duplicate document identifiers appearing in one indexing sequence, that is, before the update has been committed.
340: The term strength is not valid.
341: The relation number is not valid, must be in.
342: The relation type is invalid, use one of the defines described in API.
343: The phrase (term) is too long.
344: Unexpected end of file encountered while reading.
345: Version conflict detected when reading index/thesaurus files.
346: Overflow in thesaurus buffers.
347: Invalid name, probably too long a name, for file or directory.
348: Lookup did not find term (phrase) in dictionary or entry in definition file does not contain mandatory term.
349: Definition file is empty.
350: Thesaurus dictionary or definition file as specified via input parameter does not exist.
351: Syntax errors in definition file.
352: The Relationship was specified incorrectly.
352: The Relationship number was out of range.
360: An invalid single character masking was used.
361: An invalid multiple character masking was used.
362: Operator arity is smaller than number of operands given in query.
363: Operator value out of range defined by ItlEnOperator enumeration.
364: Value for rank formula out of enumeration range.
365: Number identifying proximity segment is out of range.
366: Query is under construction and cannot be redefined or reset.
367: Scope given as previous search result denotes empty result.
368: Invalid call requesting to add field names before setting the first one.
369: Invalid search flag requesting an invalid comparison with index content is ignored. If, for example, a case-sensitive comparison was requested for an index that was build in a case insensitive manner, this reason code is shown in the error information.
370: Masking of strings is not supported for Thai or DBCS languages.
371: No valid query input. For example, the search terms is available.
372: Invalid comparison operations requested.
373: Invalid comparison operations requested.
374: Search index handle was requested for an empty index.
375: The combination of operator and requested operator mode is not supported.
380: Search result is incomplete, search was discontinued due to threshold.
381: Index lookup revealed that query contained stopwords.
401: The operation cannot be performed because the Text Search Engine detected a corruption in the index files used for field/attribute name mapping.
402: The operation cannot be performed because the Text Search Engine detected an invalid field or attribute name.
403: The operation cannot be performed because the given field or attribute name is unknown.
404: The limit of different attributes for one of the attribute types or of different fields has been exceeded for this index.
500: The document/data contains an invalid character sequence (in a UTF8, UTF16, or DBCS source).
501: The code page converter was in error.
502: The document/data contains an incomplete character sequence (in a UTF8, UTF16, or DBCS source).
503: The code page converter has an invalid descriptor.
600: The XML document contains an asynchronous entity. For example, an unquoted XML attribute value.
602: Invalid character reference, (for example, or).
603: Invalid binary entity reference.
604: XML Parser Expat could not be created.
605: An attribute name in tag must be unique.
607: XML Parser found an invalid external entity reference.
608: Documents includes an incorrect token, like missing a < or >.
609: XML documents must have an enclosing tag, and after this enclosing end tag no text is allowed.
610: A processing instruction is not allowed at its position. For example, the first processing instruction is not the prolog <?xml .. ?>.
611: An element is a sequence of start tag, content, and end tag. This error occurred, for example, from the sequence "<s> text /s>", because the end tag is not correct.
612: Memory allocation failed in XML parser.
614: Invalid parameter entity reference.
615: A non-complete character, maybe only the first byte of a 2-byte UTF8 character.
616: Recursive entity reference.
617: XML Syntax error; for example text outside the enclosing start and end tag.
618: Every start tag needs a matching end tag.
619: Unclosed cdata section.
620: Unclosed token; for example text after the last token in a document.
621: There is an entity in the document that could not be resolved.
622: Unexpected error.
631: Could not parse field or attribute information in meta-tag. Tag must have the format <meta name="abc" content="xyz">; maybe attributes name or content of the meta-tag not correct.
632: The entity could not be transformed to a character.
650: Different field definitions begin with the same start tag.
651: One start tag contains another, so the tags are ambiguous.
652: If a field and an attribute use the same start tag, then they must use the same end tag or both no end tag.
653: A field not yet closed if the document ends.
654: No document model is specified for the structured format. The document will be parsed as plain text document without field or attribute informations.
670: The operation could not be performed, because it requires the "Outside In" (TM) libraries, which could not be found.
671: The operation could not be performed, because a required procedure from the "Outside In" (TM) libraries could not be loaded. Probably the libraries are outdated or corrupted.
672: An error occurred while the document was processed with "Outside In".