Logging

Content Manager writes logs of its processes - for example, to store system messages and errors regarding the operation of the server - to two destinations, depending on whether it is a local or system log.

To enable Workgroup Server logging, use the command Enable Logging Now. See Working with a Workgroup Server.

There are two types of Content Manager log files:

  • Windows event viewer log files
  • Content Manager log files

You can use the audit log viewer to view any logs except those created by Content Manager Enterprise Studio, for which you can use Notepad.

You can access the audit log viewer from Content Manager Enterprise Studio by right-clicking Datasets - Utilities - Audit Log Viewer.

You can view these event logs through the Event Viewer on Windows systems.

  • System logs for access permission errors
  • Application logs for Content Manager information errors
  • In C:\Micro Focus Content Manager\ServerLocalData\TRIM\Log
    • Workgroup Server logs: TRIMWorkgroup<YYYY>_<MM>_<DD>.txt - for example, TRIMWorkgroup2010_1_15.txt
    • Event logs: TRIMEvent_<DB ID>_<YYYY>_<MM>_<DD>.txt - for example, TRIMEvent_45_2009_02_28.txt

In C:\Micro Focus Content Manager\ServerData\TRIM\<DB_ID>\

  • Audit logs: C:\Micro Focus Content Manager\ServerData\TRIM\<DB ID>\AuditLogs\<Year>\Date_<YYYY-MM-DD>.txt

    For example, C:\Micro Focus Content Manager\ServerData\TRIM\45\AuditLogs\2010\Date_2010-01-17.txt

  • RM DataPort log:C:\Users\<user>\AppData\Roaming\Micro Focus\Content Manager\TRIMDataPort\Logs\tpLog_<DDMMYY>_<HHMMSS>.txt, e.g. tpLog_280210_094459.txt
  • Dataset schema report log: Location specified in Content Manager Enterprise Studio - Dataset - Schema - Report dialog box
  • Dataset schema analysis log: Location specified in Content Manager Enterprise Studio - Dataset - Schema - Analyse dialog box
  • Dataset schema repair log: Location specified in Content Manager Enterprise Studio - Dataset - Schema - Repair dialog box
  • Dataset schema upgrade log: Location specified in Content Manager Enterprise Studio - Dataset - Schema - Upgrade dialog box
  • Workflow upgrade logs: Location specified in Content Manager Enterprise Studio - Dataset - Schema - Upgrade Workflow dialog box
  • Offline Records log: C:\Users\<user>\AppData\Local\Micro Focus\Content ManagerLog\tdrawer.txt
  • Content Manager in Outlook log: Location specified in Content Manager In Outlook Settings dialog box
  • Store transfer log: Location specified in Document Stores - right-click Transfer dialog box
  • Store integrity check log: Location specified in Document Stores - right-click Integrity Check dialog box
  • Restart data and dataset creation SQL logs - location specified in Content Manager Enterprise Studio when first creating a new dataset in the Run Parameters dialog box - the last one before completing the process

    NOTE: Take note of this path as it is only visible here and not elsewhere after the dataset creation process.

The generated logs for actions performed on a dataset, such as creating or registering a dataset, upgrading a schema, schema repairs, etc. are saved to C:\Users\<username>\AppData\Local\Micro Focus\Content Manager\Log

Workgroup Server logs save the search parameters so that searches are easier to identify, for example:

  • 04:47:19 219 IT UserName GetRecordset(main)[2 4294967295 100 Records - ''PICOS'' in Title] SQL statement....
  • 04:47:50 0 IT UserName GetRecordset(main)[2 4294967295 100 Records - Date Registered is on '18/09/2006'] SQL statement...
  • 04:48:21 16 IT UserName GetRecordset(main)[2 4294967295 100 Records - Date Registered is between '18/09/2000' and '18/09/2006'] SQL statement...
  • 04:48:58 329 IT UserName GetRecordset(main)[2 4294967295 100 Records - Not At Home Location is 'Abbott'] SQL statement...
  • Content Manager IDOL Service logs - saved in C:\Micro Focus Content Manager\IDOL\TRIM IDOL Service\logs by default:
    • application.txt - for application activities like startup, shutdown, thread information
    • dah_application.txt - for actions of the Distributed Action Handler (DAH)
    • dih.application.txt - for actions of the Distributed Indexing Handler (DIH)
    • dih_index.txt - for index actions
    • dih_query.txt - for query actions
    • index.txt - for index action commands received from Content Manager
    • query.txt- for query action commands received from Content Manager
    • action.txt - details of all the requests that the IDOL component received
  • Content Manager IDOL Content Services logs - saved in C:\Micro Focus Content Manager\IDOL\TRIM Content Service [number]\logs by default:
    • application.txt - for application actions like startup, shutdown, thread information
    • index.txt - for index action commands received from the DIH
    • query.txt - for query action commands received from the DAH
  • Server local data logs - saved in C:\Micro Focus Content Manager\ServerLocalData\TRIM\Log
    • Workgroup Server logs: TRIMWorkgroup<YYYY>_<MM>_<DD>.txt - for example, TRIMWorkgroup2010_1_15.txt
    • Event logs: TRIMEvent_<DB ID>_<YYYY>_<MM>_<DD>.txt - for example, TRIMEvent_45_2009_02_28.txt
    • IDOL reindexing log: By default, saved in C:\Users\<name>\AppData\Local\Micro Focus\Content Manager45\Log\IdolReindex

You may also find the Windows application logs useful in the event of major issue with the entire system.