Table of Contents
Advertisement
7-10. Using the Logs
7-10-1. Types of Log
The SERVICE TOOL includes 9 logs:
Application Log -- This log records the events controlled and monitored by all system software
•
applications and subsystems.
DICOM Log -- This is a log of Network (DICOM) Subsystem events filtered from the Application
•
Log. The Network Subsystem is part of the DRE application.
Error Tally -- This log records all error events in 2 separate tallies: a Current Tally, which counts
•
and lists errors that have occurred since the last reset of this tally, and a Lifetime Tally, which
counts all errors since installation of the system.
IIS (Internet Information Server) Log -- This log records all attempts to connect to the web server.
•
Local Panel Log -- This is a log of events in the Local Panel Subsystem, filtered from the
•
Application Log. The Local Panel Subsystem is part of the DRE application.
MCS Log -- This is a log of MCS Subsystem events filtered from the Application Log. The log
•
records all transactions between the peripheral MICROS and the MCS Master CPU that are
transferred to the DRE application over the communications link between the MCS and DRE.
NT Event Log (App) -- This log records Windows events in the software applications.
•
NT Event Log (System) -- This log records Windows events in the system software.
•
Print Delivery Log -- This is a log of all Delivery Subsystem events filtered from the Application Log.
•
The Delivery Subsystem is part of the DRE Application.
7-10-2. The Application Log
7-10-2-1. Using the Application Log
The Application Log and the subsystem logs which can be filtered from it are important troubleshooting
resources. When an error occurs, you can search the logs to help locate the problem by checking the
sequence of events leading up to the error. A typical troubleshooting sequence might involve:
Connecting your LAPTOP to the IMAGER and using SecureLink to access the SERVICE TOOL.
•
Searching the Error Tally to determine how many times the error has occurred.
•
Opening the NT Event (System) Log to determine the time at which the last error occurred.
•
Searching the Application Log (or a subsystem log) for data at the time of the error.
•
Examining the data in the log that precedes the error.
•
If necessary, saving the log and sending it to the TSC or Service Engineering.
•
2005 July Rev. B
7F3318
Section 7 - - Troubleshooting
7-71
Advertisement
Table of Contents
Troubleshooting
