12.2.1 getlog_server.bat (acquiring the failure information without the database backup from the server)/getdetaillog_server.bat (acquiring the failure information with the database backup from the server)/getlog_client.bat (acquiring failure information from a client)
- Organization of this subsection
(1) Function
Acquire failure information of JP1/DH - Server from the server or client machine. These commands enable you to acquire the following information in the machine environment where JP1/DH - Server operates:
-
OS information
-
Hardware information
-
Running process
-
Network configuration
-
Installed application
-
Event logs (For applications and system)
-
Setting information for Internet Explorer
-
Setting information for Java
-
Log information for linked products
-
Configuration files for JP1/DH - Server
-
Database information
Before using the getlog_client.bat command, change the following item in the batch file:
rem ---------------------------- rem User-set items rem ---------------------------- set SERVERNAME=FQDN-of-JP1/DH-Server-machine
Example:
rem ---------------------------- rem User-set items rem ---------------------------- set SERVERNAME= jp1dhserver.foo1.foo2,co.jp
(2) Executor
A user with a built-in Administrator account or with Administrator permissions executes the command from the command prompt.#
- #
-
Do not execute a command directly. Use the command prompt to execute a command.
(3) Format
-
To acquire failure information from the server machine:
getlog_server.bat or getdetaillog_server.bat DB-password
-
To acquire failure information from a client machine:
getlog_client.bat
(4) Arguments
- DB-password
-
Specify the database password.
The default value for the database password is set to p@ssw0rd.
(5) Execution results
The files with the command execution results are stored in the logdata folder created immediately below the current directory where the command is executed.
The following figures show the configuration of output files.
Note that some of the files to be output in Linux are different from those in Windows. Files with differences are as follows:
-
Output destination of registry information
logdata/reg/.HTC_xxxx.inf
Note: xxxx represents a value output differently depending on your product.
-
Output destination of \logdata\netstat\ipconfigall.txt (a file that includes TCP/IP configuration for all adapters)
logdata/reg/ifconfiga.txt
-
\logdata\netstat\ipconfigdisplaydns.txt (a file that includes DNS cache) is not output.
-
Output destination of the event log data
logdata/event/messages
logdata/event/messages-yyyymmdd
In Linux, corresponding system log data is acquired.
(6) Return codes
Return code |
Description |
Operation after an event occurrence |
Occurrence condition |
---|---|---|---|
0 |
Normal |
-- |
Information is collected successfully. |
4 |
Warning (information level) |
Interrupts command processing. |
|
8 |
Error |
Interrupts command processing. |
Information collection failed. |
16 |
Error |
Interrupts command processing. |
|
(7) Output message (Output destination: stdout)
No. |
Message |
Return code |
Operation after an event occurrence |
Action to be taken by the operator |
Occurrence condition |
---|---|---|---|---|---|
1 |
Failure information will be collected. |
-- |
Starts command execution. |
None |
When a command is executed |
2 |
Successfully collected the failure information. Press any key. |
0 |
Terminates command execution. |
None |
When information is collected successfully |
3 |
Did not successfully collect the failure information. Check the following items:
|
8 |
Terminates command execution. |
Check the following and re-execute the command:
|
When collecting information failed |
4 |
Did not successfully collect the failure information. Could not find the configuration file to be copied. |
8 |
Terminates command execution. |
Make sure that the collection target file exists. |
When the collection target configuration file is not found |
5 |
An output folder for the collected information exists. Overwrite the output information? (y/n) |
-- |
Waits for user response. |
Select y to continue execution, or n to cancel execution. |
When a log output destination folder already exists |
6 |
Canceled command execution. Press any key. |
4 |
Terminates command execution. |
If you selected n in No. 5, delete or move the log output destination folder, and then re-execute the command. |
When n is selected in No. 5 |
7 |
Specify the DB password in the argument. Press any key and try again. |
16 |
Terminates command execution. |
Specify the database password as the argument, and then re-execute the command. |
When a command is executed without the database password specified as the argument |
8 |
Did not successfully collect the failure information. Press any key and try again. |
16 |
Terminates command execution. |
Check the following and re-execute the command:
|
When backing up the database with the backup command failed (Only when the getdetaillog_server.bat command is executed) |
(8) Notes on using the command
Do not execute a command directly. Use the command prompt to execute a command.
If you have enabled UAC (User Account Control) in the operating system, use one of the following ways to execute a command:
-
Log in as a built-in Administrator user, start the command prompt, and then execute a command.
-
Log in as a user with Administrator permissions, start the command prompt by clicking Run as Administrator, and then execute a command.
-
Execute a command from a shortcut for the command prompt with the elevated privileges created at the time of JP1/DH - Server installation.#
- #
-
If you use a command prompt in this way in Windows Server 2012, Windows Server 2012 R2 or Windows Server 2016, you need to install Microsoft .NET Framework 3.5. For details about how to install Microsoft .NET Framework 3.5, see D. Installing .NET Framework 3.5.
If the command is interrupted due to an error in the database, a backup file with a size of 0 bytes is created.
In an execution environment such as the ones described below, acquiring failure information might take a while.
-
Where there are many connections to the network
If the machine has many definitions of network connections, acquiring network configuration information might take time.
-
Where there are many output logs
If you execute the getlog_client.bat command in the 32-bit command prompt on a client with a 64-bit operating system, you cannot acquire the information about the 64-bit application. Make sure that you execute the command in the 64-bit command prompt.
Simultaneous executions of commands on the same machine are not supported.