Checking event logs

After checking the dashboard for error messages, check the Windows event logs.

Error identification

Use the event logs to attempt to locate the source of the problem. After you have located the potential problem area, use the relevant source or target connector log files to determine error details.

Begin by checking the following event logs in the Windows Event Viewer.

Table 1. IBM Content Collector event log errors
Event log Action
Application Check for errors or warnings issued by any IBM® Content Collector components. All Content Collector related errors or warnings have the string CTMS in the log name.
CTMS_task route name Check the following task route event IDs in the given order. If an event ID is not logged, check the user actions in Table 2
  1. Did the collector start? Look for the event ID 128.
  2. Did the collector search the right locations? Look for event ID 144 and event ID 145.
  3. Did the collector submit anything to the IBM Content Collector Task Routing Engine service? Look for event ID 160.
  4. Did the IBM Content Collector Task Routing Engine service receive any input? If no input was received, event ID 161 is logged.
  5. Were source locations or documents skipped? Look for the event ID 148 and event ID 119.

Action

Table 2. Action after error identification
Result Action
If there are CTMS Application errors: Fix the errors that you can, otherwise contact IBM Software Support.
If event ID 128 is not logged:
  1. Check the collector schedule in the task route. Is the collector schedule practicable?
  2. Check that the source system connector is correctly configured and started.
  3. Check that the collector is correctly configured and started.
If event ID 144 and 145 are not logged:
  1. Is the collection source location specified correctly in the task route?
  2. Is the collection source location accessible? Check the ACL settings.
If event ID 160 is not logged:
  1. Check the collector filter settings in the task route.
  2. Check the IBM Content Collector Task Routing Engine service log.
If event ID 161 is logged:
  1. Check why no input was received by the IBM Content Collector Task Routing Engine service.
If event ID 148 is logged (source location was skipped) or ID 119 (document was skipped):
  1. Check if the location contains collectable documents, that is documents actually exist that can be collected based on the criteria that you defined.
  2. Check if the right task route was assigned.