Philips IntelliVue Series, Installation And Service Manual

Page: 320 / 522

Troubleshooting
7-34
Maintenance, Troubleshooting, and Repair
System Error
Log Files
Some software errors that are significant to system operation (unexpected error events), and
can help the Response Center or factory personnel resolve problems, are logged into
System
Error Log
text files. Examples of these errors are Open failed, socked bind failed, and
registry read/write failed. There are two ways to access these files:
Step 1. Access the !Windows Explorer from the Diagnostics menu in the Service
window
Step 2. Select the path
c:\stardate\log
.
Step 3. The SystemErrors.log will be displayed.
Step 4. Print this file by clicking on
Print
in the
File
menu at the top left corner of the
screen.
or
Step 1. Go to
c:\stardate\bin
and double-click on LogViewer.exe
Step 2. The Log Viewer application opens. Go to File -> Open to select the log files. More
than one log file can be displayed, as shown in Figure 7-9
Figure 7-9 LogViewer Window
System Info
Log Files
Some software errors are not significant to system operation (unexpected cod/data-logic
errors), are logged into
System Error Log
text files that are different from the
System
Error Log
. Examples of these errors are: shutdown, startup local mode, and user went to
service mode. These files can be accessed as follows.