Tools to Use for Troubleshooting Connectors

  • Article

Applies To: Operations Manager 2007 R2

You can track the source of a connector error by examining Windows Management Instrumentation (WMI) log files. The following steps describe how to set up and use WMI logging on Microsoft systems.

The log files are created in the directory /Var/Opt/Microsoft/Scx/Log.

For information about WMI logging on Windows operating systems before Windows Vista, see Logging WMI Activity. For information about WMI logging on operating systems running Windows Vista and later operating systems, see Event Tracing. For information about troubleshooting specific WMI error messages, see WMI Troubleshooting.

How to Set Up and Use WMI to Troubleshoot Connectors

Use regedt32 to modify the Logging setting for WMI in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM\Logging = 2

The following values are valid:

  • 0 – No logging

  • 1 – Errors only

  • 2 – Verbose

Increase the log file size for WMI Logging:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM\Log File Max Size = 65536

The WMI log files are located in %Windir%\System32\Wbem\Logs.

The size given is in bytes. You may want to increase the log file size; for example, you can add three zeros to the end of the byte number, making a 65MB log file.

Enable Tracing for the Windows Provider

Provider errors and warnings appear in the file c:\sci.log. You can set the level of detail captured in the sci.log file by using the Advanced System setting to set SCI_LOG_LEVEL as a system environment variable. The following values of SCI_LOG_LEVEL are available:

  • WARNING: Logs errors and warnings – the system default setting

  • TRACE: Most detailed logs

  • INFORMATION: Detailed logs

  • ERROR: Logs only errors

After making the change to SCI_LOG_LEVEL, restart the Windows provider system before the new log level takes effect.

You should reset tracing to the default value after you have determined the cause of specific errors.

Enable Tracing for Connectors

Trace logs for connectors are controlled by settings in the ConnectorService.exe.config file in the connector installation folder. For example: C:\Program Files\System Center Operations Manager 2007 R2 Connectors\OpsMgr Universal Connector\ConnectorService.exe.config. 

Open the appropriate file in Notepad, and edit the following line:

<add name=”SCInterop” value=”3” />

The following values are available for SCInterop:

  • 2 – Errors and warnings

  • 3 – Detailed error information (default)

  • 4 – Debug information

After changing and saving the file, restart the connector service for the new tracing level to take effect. On Windows Server 2003, the log files are located in the following folders:

  • C:\Documents and Settings\<user service runs as>\Local Settings\Application Data\Microsoft\OpsMgr Connector for HP Operations Manager

  • C:\Documents and Settings\<user service runs as>\Local Settings\Application Data\Microsoft\OpsMgr Connector for IBM Tivoli Enterprise Console

  • C:\Documents and Settings\<user service runs as>\Local Settings\Application Data\Microsoft\OpsMgr Connector for BMC Remedy ARS

  • C:\Documents and Settings\<user service runs as>\Local Settings\Application Data\Microsoft\OpsMgr Universal Connector

On Windows Server 2008, the log files are located in the following folders

  • C:\Users\<user service runs as>\Local Settings\Application Data\Microsoft\OpsMgr Connector for HP Operations Manager

  • C:\Users\<user service runs as>\Local Settings\Application Data\Microsoft\OpsMgr Connector for IBM Tivoli Enterprise Console

  • C:\Users\<user service runs as>\Local Settings\Application Data\Microsoft\OpsMgr Connector for BMC Remedy ARS

  • C:\users\<user service runs as>\Local Settings\Application Data\Microsoft\OpsMgr Universal Connector

Enable Tracing for Remedy

Remedy 6.3

  1. Log on to the Remedy Administrator as a user with administrator permissions.

  2. On the File menu, select Server Information.

  3. Click the Log Files tab, and enable the Filter Logs.

Remedy 7.1

  1. Log on to the Remedy User as a user with administrator permissions.

  2. On the home page, click AR System Administration Console.

  3. Click System, click General, and then click Server Information.

  4. Click the Log Files tab, and enable the Filter Logs.

After debugging the problem, clear the Filter Log.

Enabling and Disabling Trace Logging on a UNIX Provider

You can enable trace logging on Unix and Linux systems to capture warnings and errors that occur during forwarding of data and requesting data from the provider.

To enable logging on UNIX-based or Linux-based computers

  1. Log on to the UNIX-based or Linux-based computer with root access.

  2. Open a Command Prompt window, and at the command prompt, type the following command:

    /opt/microsoft/scx/bin/tools/scxadmin -log-set all verbose

To disable logging on UNIX-based or Linux-based computers

  • To disable trace logging, at the command prompt, type the following command:

    /opt/microsoft/scx/bin/tools/scxadmin -log-reset

Enable Trace Logging for scinteropd.exe on HP Operations Manager Windows

You can enable trace logging for the scinteropd.exe service running on an HP Operations Manager Windows system to capture errors that occur during its monitoring.

To enable logging on the scinteropd.exe event consumer service

  1. Open the registry of the HP Operations Manager Windows server and go to the following key

    HKLM\SOFTWARE\Microsoft\OpsMgr to HPOMW Provider

  2. Set DebugLevel to select the level of logging:

    • 5 = Errors and Warnings

    • 1 = Tracing (all)

  3. Set DebugLogFiles to select the number of files that are kept after hitting the DebugMaxSize value.

  4. Set DebugMaxSize to select the maximum size of the log file in MBs (1 = 1 MB)

The log files are created in the <ProviderInstallDirectory>\log directory.