Checking whether the source system collector started

If the task route event log ID 128 was not logged, the collector was not started. Source documents can only be collected if the source system collector is correctly configured and started.

Error identification

Depending on the document collector that you defined in the task route, search for the following strings in the respective source system connector log files. The log level determines what messages are logged to the files. At minimum, errors will be logged to the application event log.

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: Trace

Search for the following strings:
  • Collector working as
For example:
447] Collector working 
as stubbing 
lifecylce collector	
...
2012-01-24T11:19:25.594Z 
FINEST	 [533] 
configuration is:
<xml-fragment name=
"EC Collect Email " 
description="This 
collector collects email 
that is older than one 
week and larger than 1 MB.
Configure one of the 
following collection 
sources: 
All mailboxes in a group, 
All mailboxes on a server, 
Mailbox, Public store" 
id="92f5443c-14b9-4685-
b218-9d59fe295c06" 
ignoreEncrypted="false" 
expandDistributionLists=
"false" xmlns:xsi=
"http://www.w3.org/
2001/XMLSchema-instance" 
xmlns:xsd=
"http://www.w3.org/2001
/XMLSchema" 
xmlns:con="http:
//www.ibm.com/afu/
Mailconnector/Collector/
Config">
...
[com.ibm.afu.
mailconnector.collector.
ArchivingCollector 
createCrawlerConfig
ForAutomatic]
File System Source Connector File system collection errors 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 strings:
Primary collection 
starting.

Container collection 
starting, processing 
{0} urls for container 
{1}.
IBM® Connections Connector

afu_connections_sysout_<file number>

Log level: Trace

Search for the following strings:
  • start items collection

Action

Table 2. Action after error identification
Result Action
Search string was found Were documents submitted for processing by the IBM Content Collector Task Routing Engine service?
Search string was not found or errors were logged Check the source system collector configuration settings, For example:
  • Is the collection source location specified correctly?
  • Is the collection source location accessible? Check the ACL settings.
  • Is the collector schedule practicable?