B.1 Diagnostic Utility

The Diagnostic Utility gathers information from your Administration server to help diagnose issues with DRA and ExA. Use this utility to provide log files to your NetIQ Technical Support representative. The Diagnostic Utility provides a wizard interface that guides you through setting log levels and collecting diagnostic information.

B.1.1 Accessing the Diagnostic Utility

You can access the Diagnostic Utility from any Administration server computer. However, you should run the Diagnostic Utility on the Administration server where you are experiencing the issue.

By default, the setup program installs the Diagnostic Utility with the Administration server component. You cannot copy the utility to another folder and run the utility from the new folder.

To access the Diagnostic Utility:

  1. Log on to the Administration server computer using the DRA Admin account.

  2. Run DRADiagnosticUtil.exe from the Program Files\NetIQ\DRA folder.

B.1.2 Understanding the Diagnostic Information

You can select which diagnostic information you want to collect or let the Diagnostic Utility collect the recommended data for a specific failure type. Based on the failure type you choose, the Diagnostic Utility gathers the following information from your Administration server:

ADSI logs

Collects diagnostic information about the DRA ADSI provider from Administration registry entries under HKEY_Local_Machine\ Software\Mission Critical Software\OnePoint\ADSI.

APJS diagnostics

Collects diagnostic information about the Accounts Provider Job Scheduler and the tasks this provider controls.

Application Event log

Collects diagnostic information from the Windows 2000 Application Event Log.

Automation scripts

Collects diagnostic information about scripts running for automation triggers.

Domain cache files

Collects the domain cache files on this Administration server.

Domain cache logs

Collects diagnostic information about the domain cache on this Administration server.

DRA registry settings

Collects diagnostic information from the entire Administration registry entry under HKEY_Local_Machine\Software.

Dr. Watson logs

Collects debugging information about applications you run on this computer. To enable this option, install and set up Dr. Watson as your default debugging tool. For more information about using Dr. Watson as your default debugging tool, see the Admnistration Installation Guide.

File times and sizes

Collects the time stamp and size for each file in the Program Files\NetIQ\DRA folder on your Administration server.

IIS service logs

Collects diagnostic information about IIS application settings.

Install information

Collects diagnostic information from a subset of the entire registry.

Licensing information

Collects information about the current effective license.

Server state information

Collects internal Administration server information. If the Administration server is not currently running, the utility is unable to collect any server state information. In addition the data collection process fails. If the collection process fails, deselect Server State Information and re-run the utility.

Server logs

Collects diagnostic information from the Administration server logs. The McsAdminSvc_Startup.nq1 file logs service initialization data and the McsAdminSvc.nq1 file logs general Administration server data.

Services configurations

Collects a list of the services running on the Administration server including the service type, status, and logon parameters.

System Event log

Collects diagnostic information from the Windows 2000 System Event Log.

Web Console logs

Collects diagnostic information about event log entries, performance metrics, and the virtual directory settings for the Web Console.

Win32 console log files

Collects diagnostic information about the Account and Resource Management console and the Delegation and Configuration console.

Win32 console settings

Collects the client options and other settings for the Account and Resource Management console and the Delegation and Configuration console.

B.1.3 Configuring Log Settings

You can configure different log settings, such as logging levels, for individual DRA components on each Administration server computer. The logging level determines the quantity and detail of the diagnostic information you can collect. For example, if you set a high logging level, DRA logs additional information that can be used to help diagnose a more complex issue. Before collecting diagnostic information, ensure the log level is appropriate for the issue you are experiencing.

To configure log settings:

  1. Start the Diagnostic Utility. For more information, see Section B.1.1, Accessing the Diagnostic Utility.

  2. Click Enable or change logging for a DRA component, and then click Next.

  3. Specify the appropriate log level for the DRA component about which you want to collect diagnostic information.

  4. To specify additional settings, such as the log file location, complete the following steps:

    1. Click Settings for the appropriate DRA component.

    2. Specify which settings you want to the Diagnostic Utility to use when logging information about this component.

    3. Click OK.

  5. To apply these settings, click Finish.

B.1.4 Collecting Diagnostic Information

You can select which diagnostic information you want to collect or let the Diagnostic Utility collect the recommended data for a specific failure type. Based on the failure type you choose, the Diagnostic Utility gathers the appropriate information from your Administration server.

By default, the Diagnostic Utility outputs information as a.zip file. When you call NetIQ Technical Support, you may need to provide this file to your Technical Support representative By default, DRA puts log files in the following location on the Administration server computer: C:\Documents and Settings\username\Local Settings\Application Data\NetIQ\DRA\Logs. For more information, see Section B.1.7, Finding Specific Log Files.

For more information about which diagnostics to select, see Section B.1.2, Understanding the Diagnostic Informationor consult your Technical Support representative.

To collect diagnostic information:

  1. Start the Diagnostic Utility. For more information, see Section B.1.1, Accessing the Diagnostic Utility.

  2. Click Collect diagnostics information about a DRA failure, and then select the failure type that best represents your issue.

  3. Click Next.

  4. Review the diagnostic settings for the selected failure type, and then click Next. You can select or clear a setting, or choose another failure type.

  5. Specify the name and location of the zip file.

  6. To begin collecting diagnostics, click Finish.

B.1.5 Viewing APJS Diagnostics

The Accounts Provider Job Scheduler (APJS) is part of the Administration server component. APJS controls schedules and records the status of various domain and server tasks, such as accounts cache refreshes and synchronization across multiple Administration servers. APJS diagnostics provide detailed information about these server and domain activities.

To view Accounts Provider diagnostics:

  1. Start the Diagnostic Utility. For more information, see Section B.1.1, Accessing the Diagnostic Utility.

  2. Click View Accounts Provider Job Scheduler diagnostics.

  3. To update the diagnostic information, click Refresh.

  4. Click Finish.

B.1.6 Viewing Lock Diagnostics

You can use the Diagnostic Utility to view the status of read and write locks on this Administration server. Locks occur during server synchronizations and some cache refreshes. During a lock, an Assistant Admin may not be able to view (read) or modify (write) managed objects. Lock diagnostics provide a count of pending read and write operations, as well as the last time the Administration server successfully released a lock.

To view lock diagnostics:

  1. Start the Diagnostic Utility. For more information, see Section B.1.1, Accessing the Diagnostic Utility.

  2. Click View lock diagnostics for Read/Write and Replication locks.

  3. To update the diagnostic information, click Refresh.

  4. Click Finish.

B.1.7 Finding Specific Log Files

You can use the Diagnostic Utility to find specific log files for a DRA component. By default, DRA puts log files in the following location on the Administration server computer: C:\Documents and Settings\username\Local Settings\Application Data\NetIQ\DRA\Logs. You can configure the log file location for individual DRA components. For more information, see Section B.1.3, Configuring Log Settings.

To find a specific log file:

  1. Start the Diagnostic Utility. For more information, see Section B.1.1, Accessing the Diagnostic Utility.

  2. Click Enable or change logging for a DRA component, and then click Next.

  3. Click Find Logs for the appropriate DRA component.

  4. To view a log file, select the file, and then click File > Open.

  5. To print a log file, select the file, and then click File > Print.

  6. Close the file view window, and then click Finish.