Table of Contents
Advertisement
Chapter 1 Maintenance
4.
Collecting Failure Information
If the server is broken, you can collect failure information by using the following method.
The failure information to be described is to be collected only at the request of your sales representative.
4.1
Collecting Event Logs
Collection for various event logs that occurred on the server follows the steps below.
4.1.1
Windows Server 2008 R2 / Windows Server 2008
1. Select Administrative Tool and then Event Viewer from Control Panel.
2. Select the type of log in Windows Logs.
Application records events related to running applications.
Security records events related to security.
System records events that occur in Windows system components.
3. Select Save All Event As... from Action menu.
4. Enter the file name of the archived log in File name.
5. Select the type of the log file you want to save in Save as type, and then click [Save].
4.1.2
Windows Server 2003 R2 x64 Edition / Windows Server 2003
1. Select Administrative Tool and then Event Viewer from Control Panel.
2. Select the type of log to collect.
Application records events related to running applications.
Security records events related to security.
System records events that occur in Windows system components.
3. Select Save All Event As... from Action menu.
4. Enter the file name of the archived log in File name.
5. Select the type of the log file you want to save in Save as type, and then click [Save].
For more information, refer to Windows help.
20
Important
When the system restarts after a failure has occurred, a message may appear
indicating virtual memory shortage. Ignore this message and proceed with
starting the system. Restarting the system may result in an inability to
properly dump the data.
Tips
If a STOP error, system error, or stall occurs, restart the system and then follow the
steps below.
Express5800/R120d-1E, R120d-2E Maintenance Guide
4. Collecting Failure Information
Advertisement
Table of Contents
