Sun Java System Identity Synchronization for Windows 6.0 Installation and Configuration Guide

Log Types

This section describes the different kinds of logs that are available for Identity Synchronization for Windows:

Central Logs

As long as Identity Synchronization for Windows components can access Message Queue, all audit and error messages will be logged in the Identity Synchronization for Windows central logger. Consequently, these central logs (which include messages from all components) are the primary logs to monitor.

The centralized logs are located on the machine where Core is installed, in the following directories:

Table 9–1 Log Types for Identity Synchronization for Windows

Log Name 



Warning and Severe messages are reported here.


A superset of error.log that includes messages about each synchronization event.


Messages generated by the resync command are reported here.

Each central log also includes information about each component ID. For example,

[2003/03/14 14:48:23.296 -0600] INFO 13 
"System Component Information:
SysMgr_100 is the system manager (CORE);
console is the Product Console User Interface;
CNN100 is the connector that manages 
[ (ldaps://];
CNN101 is the connector that manages
[dc=example,dc=com (ldap://];"

In addition to the central logger, each component has it’s own local logs. You can use these local logs to diagnose problems with the connector if it cannot log to the central logger.

Local Component Logs

Each connector, the system manager, and the central logger have the following local logs:

Table 9–2 Local Logs

Log Name 



A superset of error.log that includes messages about each synchronization event. These messages are also written to the central audit.log.


Warning and Severe messages are reported here. These messages are also written to the central error.log.

These local logs are located in the following subdirectories:

Note –

By default, Identity Synchronization for Windows deletes connector logs after ten days. You can extend this period by editing the value in the file and restarting the service daemon.

Local Windows NT Subcomponent Logs

The following Windows NT subcomponents also have local logs:

Directory Server Plug-in Logs

The Directory Server Plug-in logs information through the Directory Server connector to the central log and through the Directory Server logging facility. Consequently, local Directory Server Plug-in log messages will also be saved in the Directory Server error log.

Directory Server saves information into the error log from other Directory Server Plug-ins and components. To identify messages from the Identity Synchronization for Windows Directory Server Plug-in, you can filter out lines containing the isw string.

By default, only minimal Plug-in log messages are displayed in the error log. For example:

[14/Jun/2004:17:08:36 -0500] - ERROR<38747> - isw - conn=-1 
op=-1 msgId=-1 - Plug-ins unable to establish connection to DS Connector 
at attila:1388, will retry later

ProcedureTo Change the Verbosity Level of the Error Logs

You can change the default verbosity level of the Directory Server error log through DSCC as follows:

  1. Log in to Directory Service Control Center.

  2. On the Directory Servers tab page, click the server whose log level you want to configure.

  3. Select the Server Configuration tab, then the Error Logging tab.

  4. In the General -> Additional Items to Log section, select Plug-Ins.

  5. Click Save.

    You can enable plug-in logging using the command line.

    $ dsconf set-log-prop errors level:err-plugins

    For more information about Directory Server logging, refer to Chapter 14, Directory Server Logging, in Sun Directory Server Enterprise Edition 7.0 Administration Guide.