13.4.1 In Windows
- Organization of this subsection
(1) Log information about the OS
The following table lists the OS-related information that must be collected.
|
Type of information |
Overview |
Default file name |
Collected by jpcras command? |
|---|---|---|---|
|
System log |
Windows event log |
-- |
Y |
|
Process information |
List of processes |
-- |
Y |
|
System file |
hosts file |
system-folder\system32\drivers\etc\hosts |
Y |
|
services file |
system-folder\system32\drivers\etc\services |
Y |
|
|
OS information |
System information |
-- |
Y |
|
Network status |
-- |
Y |
|
|
Host name |
-- |
Y |
|
|
Dump information (In Windows Server 2003) |
Dr. Watson log file |
|
Y |
|
Dump information |
Log file containing error reports and corrective actions |
user-mode-process-dump-output-folder\program-name.process-ID.dmp
|
N |
- Legend:
-
Y: Can be collected.
N: Cannot be collected.
--: Not applicable.
- #
-
If your setup provides for output of log files to a different folder, make sure that you collect the data from the correct folder.
(2) Information about Performance Management
You should collect information about Performance Management, as listed in the table below. In the case of a network error, you should also collect applicable files from the connection-destination machine.
|
Type of information |
Overview |
Default file name |
Collected by jpcras command? |
|---|---|---|---|
|
Common message log |
Message log output from Performance Management (sequential file method) |
installation-folder\log\jpclog{01|02}#1 |
Y |
|
Message log output from Performance Management (wraparound file method) |
installation-folder\log\jpclogw{01|02}#1 |
Y |
|
|
Configuration information |
Each configuration information file |
-- |
Y |
|
Output results of the jpctool service list command |
-- |
Y |
|
|
Version information |
Product version |
-- |
Y |
|
Historical information |
-- |
Y |
|
|
Database information |
Agent Store service |
|
Y |
|
Trace log |
Trace information for each Performance Manager |
--#2 |
Y |
|
Install log#3 |
Installation message log |
The following files under the system-folder\TEMP\HCDINST folder:
|
N |
|
Information about PFM - Agent for Service Response |
Log files for PFM - Agent for Service Response |
All files under installation-folder\agtv\probe\log |
Y |
|
Definition files for PFM - Agent for Service Response |
All files under installation-folder\agtv\probe\conf |
Y |
|
|
Measurement condition registration and storage files |
All files under installation-folder\agtv\probe\task |
Y |
|
|
Password files |
All files under installation-folder\agtv\probe\passwd |
Y |
|
|
Report files |
All files under installation-folder\agtv\probe\report |
Y |
|
|
User-defined commands |
All files under installation-folder\agtv\probe\user |
Y |
|
|
Temporary files |
All files under installation-folder\agtv\probe\tmp |
Y |
|
|
Certificate files |
All files under installation-folder\agtv\probe\cert |
Y |
|
|
IE scenario file |
All files under installation-folder\agtv\probe\iescena |
Y |
|
|
Web transaction files |
All files under installation-folder\agtv\probe\webtrans |
Y |
|
|
Registry information |
HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\JP1PCAGTV |
Y |
|
|
Environment variable information |
-- |
Y |
|
|
Integrated trace log |
-- |
system-drive\Program Files\hitachi\HNTRLib2\spool\hntr2[n#4].log |
Y |
- Legend:
-
Y: Can be collected.
N: Cannot be collected.
--: Not applicable.
- #1
-
For details about how to output log information to the log files, see the chapter that describes detection of Performance Management failures in the JP1/Performance Management User's Guide.
- #2
-
For details about the trace log storage folder, see 13.3.2 Lists of log files and folders accessed upon troubleshooting.
- #3
-
Collect this log information if installation fails.
- #4
-
n represents a number in the range from 1 to 4.
(3) Operation information
You should collect the following information about the operation that was being performed when the error occurred:
-
Details of the operation
-
Time the error occurred
-
Machine configuration (for example, OS version, host name, and PFM - Manager and PFM - Agent configuration)
-
Whether or not the problem is replicable
-
Performance Management user name used during logon, if the user logged on from PFM - Web Console
-
The argument specified for the command if the error occurred during command execution.
(4) Error information on screen displays
You should obtain printouts of the following:
-
The active screen when the application error occurred
-
The error message dialog box (including the contents of detail information if it is displayed)
-
The Command Prompt window, if the error occurred during command execution
-
Hard copy of the Command Prompt window or Administrator Console window if a problem occurred during command execution
(5) User mode process dump
If a Performance Management process stops due to an application error, obtain a user dump.
(6) Collecting problem reports
If a Performance Management process stops due to an application error, obtain a problem report.
(7) Other information
You should also collect the following information:
-
Contents of System and Application in the Windows Event Viewer window
-
Content of System Information under System Tools under Accessories