Checking the IBM Content Collector deployment

If IBM Content Collector is deployed in a cluster and no documents seem to have been archived or if the IBM Content Collector log files contain many errors, the reason might be that the multiple server environment was not configured correctly.

Error identification

Depending on the source system connector that you have defined in the Configuration Manager for the task route, search for the following strings in the respective log files. Errors that occur when IBM Content Collector is installed on multiple servers are logged in the IBM Content Collector Task Routing Engine service log file.

These errors are logged depending on the log level that you defined for the IBM Content Collector Task Routing Engine service in the IBM Content Collector Configuration Manager under Tools > Task Route Service Configuration. Ensure that you set the adequate log level to track this type of error and run the task route again before you begin searching for error strings.
Table 1. IBM Content Collector Task Routing Engine service log files and messages
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 string to check if the server setup is a cluster:
  • Error*
    For example: 
    AFUP0059W The document 
{document} is not in 
the expected state 
{INITIAL}, but in state
 {STUB_ATTACHMENTS}. 
This was caused by 
multithread processing. 
No action is required. 
The document will be 
processed again.
File System Source Connector Check the task route’s event log for event ID 149 which indicates a location error that occurs if you neglect to define the service logon credentials when they are required.
SharePoint Connector This type of error cannot occur.
IBM Connections Connector

afu_connections_sysout_<file number>

Log level: Information

 This type of error cannot occur.
If you found server setup error strings in a connector log file, check the IBM Content Collector Task Routing Engine service log file.
Table 2. IBM Content Collector Task Routing Engine service log file and error search strings
IBM Content Collector Task Routing Engine service log file Log level Search strings
ICC-install-directory\ctms\Log\ibm.ctms.taskrouteservice* where * is a placeholder for the date and possibly a file number. Warning Search for the following string in the log file that indicates that a task failed, filtered by the thread ID:
  • Using machine name
  • Primary node is
  • secondary

Action

Table 3. Action after error identification
Result Action
Search string was found Validate the server setup based on findings in the IBM Content Collector Task Routing Engine service log.
Search string was not found Did a task fail?