You are here:

Exception Types Reference

Access denied: If found with class: Access; Access to original files failed, or writing temporary data during buffering failed.; If found with class: Unexpected; Reading failed for temporary files during buffering.
Archive entry processing
Content modified: Often found with class: Corrupt; Corrupt archives might need a fix. Password protected or unsupported archives might need external extraction or conversion.
Attachments removed from Native: Often found with class: Corrupt; This exception marks corrupt attachments to Outlook mails. When a native file is created, corrupt attachments are omitted.
Content size not applicable for connector: Often found with class: System, Not supported; Data is too big to retrieve, e.g. data is likely to produce an out of memory exception.; If a file size limit is defined for the connector, — and, maybe, also for a parser — change it and re-crawl.
Corrupt Outlook item property: Often found with class: Corrupt; System failed to decode a value, due to an unknown encoding in an Internet header.; The encoded parts that cannot be read are ignored. There may be some email display addresses missing. E.g., if the complete email address is "Niklas Müller" <niklas.mueller@rheinbach.de>, Niklas Müller may be missing. Document content is not affected.
Crawler out-of-memory: Often found with class: Fatal; This normally comes along with a FatalCrawlError that is logged in the crawler.log file and that will stop the whole crawler. After an out-of-memory, the system is too instable to proceed.; Depending on the out-of-memory reason, one of these actions may be recommended:
Csv parser error: Often found with class: Corrupt; The content of a field in the CSV load file is not compatible with the mapped field in (Undefined variable: recommind_products.Ing application). This might be, e.g., a date field that has invalid content, or a wrong reference to native files.
Database processing: Often found with class: Corrupt, Not supported, File format; Database protocol exceptions, e.g. a connection to Notes, Domino, or a JDBC-based database (like Ringtail, Worksite,...) fails, or SQL statements are wrong or cannot be transmitted.; If a connection failed, re-establish it and reprocess the files.
Datasource problem: Often found with class: various classes; Unexpected record/item found.
Date Parsing: Often found with class: Corrupt; A reason for this may be that the date format is not known.; In the data source configuration, in the Date settings node, add it to the Input date format table.
Directory not found: Often found with class: Access; Missing directories in file system, database, or archive.
Disk full: Often found with class: System; Writing temporary data during buffering failed due to full disk.; Change data source server or add disk space.
Document in use by other application: Often found with class: Unexpected, Access; Reasons may be:
Document too large for indexing: Often found with class: System; Data exceeds a certain limit. In such cases, the system automatically starts an indexing re-try for the metadata only and omits the content.; You can change the internal configuration option Maximum peak memory usage in the index engine configuration, in the Common > Engine parameters node.
Document too large for parser: Often found with class: System; A maximum document size is exceeded.; Possible resolution: Change the size limit or byte input for the respective parser in the data source configuration, in order to avoid OOM exceptions.
Engine out-of-memory: Often found with class: Fatal; This normally comes along with a FatalCrawlError that will stop the index engine and, consequently, the crawler. FatalCrawlError will be logged in the engine or crawler log files.
Error during communication with MindServer: Often found with class: various classes; Reasons may be:
Error during post-processing: Often found with class: Unexpected; Post processing of parsed/resolved data failed, either due to data source misconfiguration, in the Property Postprocessing node, or due to internal problems during XML document creation.; Check and correct Property Postprocessing settings, if possible, or contact Recommind support.
Error during SQL execution: Often found with class: Fatal or others; SQL errors are critical and can mean large data losses.
Error in native code: Often found with class: Corrupt; Possible reason: incorrect installation. Read the Exception field.
Error resolving URI: Often found with class: Unexpected; Resolving URI failed. This is a critical issue, because a huge amount of data may be missed.
External process execution: Often found with class: System; Exceptions produced by third party or external processes/services etc.
File corrupt: Often found with class: Corrupt; File is corrupt. If the file is a MSG or PST file, run PSTValidator.exe for details.
File not found: Often found with class:Unexpected or Access; Standalone file or archive entry not found.
General storage error: Often found with class: Unexpected; Native files could not be stored in the configured storage.
Getting storable data failed: Often found with class:; Exception for fetching storage data; Examples:
Invalid characters: Often found with class: File format, Corrupt and others; Examples:
Invalid XML: Often found with class: Corrupt; Error in producing indexable XML file.; This exception should be avoided by the system, but is sometimes caused by corrupt emails.; Contact Recommind support.
Job exception: Often found with class: various classes; This exception can be thrown by the crawler job framework. Exceptions can be runtime exceptions, for example.; For more information on a job exception, look up the crawler.log file or ask Recommind Support.
Large junk percentage: Often found with class: Corrupt; File contains large percentage of junk characters, detected by junk detectors, e.g. BASE64.; MIME types checked for junk characters are listed in the data source configuration, under Exception handling > Base64 junk removal
MIME type could not be detected/set: Often found with class: File format; MIME type detection failed.; Possible reasons:
Miscellaneous error: Often found with class: Unexpected; Exception is difficult to identify. Ask Recommind support.
Miscellaneous errors resolving resource: Often found with class: Unexpected, Fatal; If resolution of data source URI fails, a fatal error is only logged in the crawler.log file. No documents will be indexed.; Another reason my be a connector or parser exception, e.g. server is not accessible, 404 page not found.
Miscellaneous indexing error: Often found with class: Unexpected; Exception is thrown by internal crawler components. More information can be found either in the crawler.log file or in the exception document.
Miscellaneous I/O error: Found with class: Unexpected; This is often a buffer exception. Reading temporary data failed.; Found with class: Access; This is often a buffer exception: Reading original data or writing temporary data failed.
Miscellaneous parser error: Often found with class: Unexpected; Exception during document parsing.
Not supported: Often found with class: File format; File format that none of the parsers supports.
Parent document PGP secured: Often found with class: Password protected/encrypted; Used for attachments of encrypted PGP MIME messages. PGP stores the encryption in an attachment. The attachment is tagged with this exception type.
Password protected files: Often found with class: Password protected/encrypted; Encrypted and password protected data are not searchable and not readable.; Can be combined with PGP or S/MIME exceptions.
PGP encrypted: Often found with class: Password protected/encrypted; This exception is only shown if the PGP detector is enabled.; An email only contains encrypted PGP content. PGP encrypted content and signature are removed by default.; No action is required, except if you can decrypt PGP externally.
This item is suspected to have caused a crash in the last run. It is skipped in resume mode.: Often found with class: corrupt; This exception occurs if a file that cannot be processed causes the data source crawler to stop, and if the crawler automatically resumes afterwards.
S/MIME encrypted: Often found with class: Password protected/encrypted; Flags S/MIME encrypted emails if S/MIME certificates have not been imported.; You can import certificates and then re-crawl the emails.
SOAP message oversized: Often found with class: Corrupt; Exception for large messages that cannot be handled, thrown by the optional Mindserver SOAP interface.
SOAP message zero size: Often found with class: Corrupt; Exception for empty messages thrown by the optional Mindserver SOAP interface.
Stellent: Often found with class: Access; Stellent is not able to open the file. Temporary files like ~wm54154.tmp that are automatically generated, can be the reason.
Storing data failed: Often found with class: Access; Error for missing write access to store data.
Stream access: Often found with class: Access; A connector’s data access via remote connection is affected.; Read the message in the Exception field.
Temp file access: Often found with class: Access; Issues with temporary files.
Timeout: Often found with class: Timeout; Timeouts can be configured in the data source configuration for some connectors or parsers, and in the index engine configuration.
Traversing links: Often found with class: Unexpected; This may be an exception for traversing issues, missing items, "get next", etc.; There may be large amounts of data missing if this exception occurs.
Unknown MIME type: Often found with class: File format; MIME type detection failed.; Possible resolution: You may enable another detector in the data source configuration.
Unsupported MIME type: Often found with class:; A MIME type that does not figure on the supported MIME types list.

Exceptions Detected by Attachment Processing