Analyzing task connector logs

If a task failed because, for example, required metadata is missing, examine the log file of the task connectors used in the task route.

Error identification

Search for error messages in the task connector log files to identify why processing was stopped in the task that used the connector. These error messages are logged depending on the log level that you defined for the task connector. If Trace 2 logging is turned on, more detail is available for further diagnosis or debugging. The default log file directory is ContentCollector-install-directory\ctms\Log.

If the Email Connector or the SMTP Connector fails, a log-directory/SUPPORT/CRASH/timestamp directory is created that contains the error information.

Table 1. Task connector log files
Task connectors	Log file name and log level	Example error messages
Email 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>` Log level: Trace	`AFUP0021E A deduplication hash could not be generated for the document {0}. See the following message: {1}`
SMTP Connector	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	`AFUP0021E A deduplication hash could not be generated for the document {0}. See the following message: {1}`
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	`Item {0} has been modified since collector processing.` or `Get versions task failed. Item not found at url {0}.`
IBM® Connections Connector	afu_connections_sysout_`<file number>` Log level: Trace	`AFUR0005E The temporary file {0} could not be deleted. You can try deleting it manually later.`
IBM Content Manager Connector	ibm.ctms.cmv8.Connector-`yyyy`-`mm`-`dd`.log Log level: Trace	Look for `Error` or `Fatal` For example: `2012-03-01T22:15:34Z Error Failed to process CMV8 Store Versions task: com.ibm.icm.exceptions. CMConnectorException: <error reason>`
IBM FileNet® P8 Connector	ibm.ctms.p8connector.p84x.P84xConnector-`yyyy`-`mm`-`dd`.log The message format is: `utc_datetime log_level error_ message immediate_error_ stack thread_id nested_error _stack_traces_and_messages` Log level: Trace	Look for `Error` or `Fatal` For example: `2012-03-21T07:19:16Z Error Missing parameter: ContentTargetPathParamIdReason: address:0579AF4B 0x1648 Stack Trace: (class ibm:: ctms::connector:: MissingParameterException) at ...`
Metadata Form Connector	afu_formconnector_trace_`<file number>`.log afu_formconnector_sysout_`<file number>`.log Log level: Trace	`AFU1003PE Cannot convert from String to Integer`

Action

Table 2. Action after error identification
Result	Action
Error messages were found	If the messages contain a user action, attempt to fix the problem. Otherwise contact IBM Software Support.
No error messages were logged	Contact IBM Software Support.