7.4.1 In Windows

Organization of this subsection
(1) Log information about the OS
(2) Performance Management information
(3) Operation information
(4) Error information on the screen
(5) User dump (in Windows Server 2008)
(6) Collecting problem reports (in Windows Server 2008)
(7) Other information

(1) Log information about the OS

Collect the information about the OS. Table 7-6 lists the information about the OS.

Table 7-6 Information about the OS

Type of informationDetailsDefault file nameCollected by jpcras command
System logWindows event log--Y
Process informationList of processes--Y
System filehosts filesystem-folder\system32\drivers\etc\hostsY
services filesystem-folder\system32\drivers\etc\servicesY
OS informationSystem information--Y
Network status--Y
Host name--Y
Windows firewall information--Y
Dump information
(in Windows Server 2003)
Dr. Watson log filesystem-drive\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log#
system-drive\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dump#
Y
Dump information
(in Windows Server 2008)
Problem Reports and Solutions log file

user-mode-process-dump-output-folder\program-name.process-ID.dmp

Example:
jpcagt4.exe.2420.dmp
N
Legend:
Y: Can be collected
N: Cannot be collected
--: Not applicable
#
If you set up Dr. Watson to output log files to a different folder, collect the information from that folder.

(2) Performance Management information

Collect the log information about Performance Management. If the problem relates to a network connection, also collect information from the machine that is the connection target. Table 7-7 lists the log information about the Performance Management:

Table 7-7 Log information about Performance Management

Type of informationDetailsDefault file nameCollected by jpcras command
Common message logMessage log output by Performance Management (sequential files)installation-folder\log\jpclog{01|02}#1Y
Message log output by Performance Management (wraparound files)installation-folder\log\jpclogw{01|02}#1Y
Configuration informationConfiguration information files--Y
Output of jpctool service list command--Y
Version informationProduct versions--Y
Log information--Y
Database informationRemote Monitor Store serviceinstallation-folder\agt4\store\instance-name\STPD
The following files under the
installation-folder\agt4\store\instance-name\STPI folder:
*.DB
*.IDXq\store\instance-name
*.IDX
Y#2
Trace logTrace information for Performance Management services--#3Y
Agent logNormal log for processing related to acquisition of PFM - RM for Microsoft SQL Server recordsinstallation-folder\agt4\agent\instance-name\log\agt4inf{01|02}#4Y#5
Error log for processing related to acquisition of PFM - RM for Microsoft SQL Server recordsinstallation-folder\agt4\agent\instance-name\log\agt4err{01|02}#4Y#5
Install log#6Message logs from installationThe following files under the
system-folder\TEMP\HCDINST folder:
  • HCDMAIN.LOG
  • HCDINST.LOG
  • product-model-name.LOG
N
Legend:
Y: Can be collected
N: Cannot be collected
--: Not applicable
#1
For details about the output format of the log files, see the chapter on detecting errors in Performance Management in the Job Management Partner 1/Performance Management User's Guide.
#2
If you change the default storage folder, you cannot collect database information by using the jpcras command. In this case, manually collect the information from the folder.
#3
For details about the trace log storage destination folder, see 7.3.2(2) Trace log.
#4
For details about the output format of an agent log and how to change the storage folder, see 7.3.2(3) Agent log.
#5
The jpcras command collects agent log information only from the currently specified output destination folder. If you change the output destination folder for agent logs, you need to manually collect data from the agent log files that were output before the change.
#6
Collect this information if installation failed.

(3) Operation information

Collect the following information about the operation that was being performed when the problem occurred:

(4) Error information on the screen

Collect hard copies of the following:

(5) User dump (in Windows Server 2008)

In Windows Server 2008, if a Performance Management process stops due to an application error, obtain a user dump.

(6) Collecting problem reports (in Windows Server 2008)

In Windows Server 2008, if a Performance Management process stops due to an application error, obtain a problem report.

(7) Other information

The following types of information are also necessary: