Checking whether documents were submitted to the IBM Content Collector Task Routing Engine service

If the task route event log ID 160 was not listed, nothing was submitted for processing to the IBM Content Collector Task Routing Engine service.

Error identification

Search for the following strings in the source system connector log file to determine whether documents were submitted for processing by the IBM Content Collector Task Routing Engine service. These errors are logged depending on the log level that you defined for the connector.

Ensure that you set the adequate log level to identify this type of error and run the task route again before you begin searching for error strings. The default log file directory is ContentCollector-install-directory\ctms\Log.

Table 1. Source system connector log files and error search strings
Connector	Log file name and log level	Search strings
Email Connector and SMTP Connector	Lotus Domino: afu_mailconnector(Domino)_sysout_`<file number>` afu_mailconnector(Domino)_trace_`<file number>` afu_monitor_sysout_`<file number>` afu_monitor_trace_`<file number>` Microsoft Exchange: afu_mailconnector(MAPI)_sysout_`<file number>` afu_mailconnector(MAPI)_trace_`<file number>` afu_monitor_sysout_`<file number>` afu_monitor_trace_`<file number>` SMTP/MIME afu_mailconnector(SMTP)_sysout_`<file number>` afu_mailconnector(SMTP)_trace_`<file number>` afu_monitor_sysout_`<file number>` afu_monitor_trace_`<file number>` Log level: Information	Search for the following strings: `Beginning flush` `Submitted work` For example: `Queue full, blocking! Insert successfull! Attempting insert of Candidate`
File System Source Connector	Any file system messages are written to the task route event log.
SharePoint Connector	ibm.ctms.spconnector-`YYYY`-`MM`-`DD`.log Log level: Trace 2	Search for the following message per item: `Processing collection item: {0}, {1}.`
IBM Connections Connector	afu_connections_sysout_`<file number>` Log level: Information	Search for the following strings: `Collector callback for` For example: `Collector callback for <id of document>`

Action

Table 2. Action after error identification
Result	Action
Search string was found	Was the document received by the IBM Content Collector Task Routing Engine service?
Search string was not found	Check that the IBM Content Collector Task Routing Engine service was started. Check the filter settings and the collector locations in the task route. Did the collector search the expected source locations? Did documents exist that were eligible for collecting? Check the task route event log for the event ID 148 which indicates that source document locations were skipped and ID 119 which indicates that documents were skipped. If the filter settings and the collector locations appear correct, and no skipped events were logged, contact IBM Software Support.