Siemens Event Log Troubleshooting Guide
Mühlhäusser
Event Log
Troubleshooting Guide
System
SP
Service Information
0660197006646900080800011004768010048590
Print No.:
Replaces: SP00-000.840.01.03.02
SP00-000.840.01.04.02
© Siemens AG
The reproduction, transmission or use
of this document or its contents is not
permitted without express written
authority. Offenders will be liable for
damages. All rights, including rights
created by patent grant or registration
of a utility model or design, are
reserved.
English
Doc. Gen. Date: 10.05
2005
2 Revision / Disclaimer
1Revision / Disclaimer
Document revision level
The document corresponds to the version/revision level effective at the time of system
delivery. Revisions to hardcopy documentation are not automatically distributed.
Please contact your local Siemens office to order current revision levels.
Disclaimer
The installation and service of equipment described herein is to be performed by qualified
personnel who are employed by Siemens or one of its affiliates or who are otherwise
authorized by Siemens or one of its affiliates to provide such services.
Assemblers and other persons who are not employed by or otherwise directly affiliated
with or authorized by Siemens or one of its affiliates are directed to contact one of the
local offices of Siemens or one of its affiliates before attempting installation or service procedures.
Event Log SP00-000.840.01.04.02 Siemens AG
10.05 CS SD 24
Page 2 of 46
Medical Solutions
Table of Contents 3
1- 0Table of Contents
1 _______ Preconfiguration of event log______________________________________ 5
Preconfiguration of event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 _______ Event log ______________________________________________________ 6
Event log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Enter event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Functional description of the event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Functional description of the event log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3 _______ Creating an event log file ________________________________________ 13
Creating an event log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Creating a system event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Finding or sending log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4 _______ Creating service log files for UROSKOP Access_____________________ 17
Service log file for UROSKOP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Creating a service log file for UROSKOP Access. . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Content of LogFile.zip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Location of LogFile.zip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5 _______ Analysis of UROSKOP Access event log ___________________________ 18
Important messages from the imaging system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Troubleshooting tip. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Shutdown and boot sequence of the imaging system . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Shutdown table of the imaging system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Boot table of imaging system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6 _______ Creating service log files from ARCADIS systems ___________________ 23
Service log files from ARCADIS systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Create SaveLog files from remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Content of service SaveLog file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Location of all SaveLog files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Creating a SaveLog file or SaveLog Developer file . . . . . . . . . . . . . . . . . . . . . . . . . 26
Burn Log-Files to CDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7 _______ Analysis of ARCADIS system event log ____________________________ 29
Important messages from the imaging system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Ticket Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Important sources from the imaging system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Troubleshooting tip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Troubleshooting with TicketId . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Siemens AG SP00-000.840.01.04.02 Event Log
Medical Solutions
10.05 CS SD 24
Page 3 of 46
4 Table of Contents
Shutdown and boot sequence of the imaging system. . . . . . . . . . . . . . . . . . . . . . . . 32
8 _______ Saving an image for export ______________________________________ 34
Export an image to CD-ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Export the image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Saving an image for export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Examples from Local Service/ Configuration/ ImportExport Directories:. . . . . . . . . . 35
Saving an image to export: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
9 _______ Source table of imaging and main systems _________________________ 36
Source table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Imaging system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Main systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
10 ______ syngo® source table ____________________________________________ 42
Source table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
syngo® CSA source table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
syngo® CAP source table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
syngo® Versant source table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
11 ______ Copying files to CD _____________________________________________ 44
Copying files to CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Principle of copying files to CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Creating a new backup package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Back up your created package to CD.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
12 ______ Changes to previous version _____________________________________ 46
Event Log SP00-000.840.01.04.02 Siemens AG
10.05 CS SD 24
Page 4 of 46
Medical Solutions
Preconfiguration of event log 5
1Preconfiguration of event log
2-
Preconfiguration of event log 0
The imaging system event log is created preconfigured.
• Select “Local Service/ Configuration/ Service/ Eventlog”.
Fig. 1: Configuration of Event Log Tool
• Configure the event log by selecting the three checkboxes as shown above (default).
Explanation of event log configuration:
Log only service messages
All messages classified as service and customer messages are logged. Developer messages are not logged in the event log.
Display service messages
All messages classified as service and customer messages are displayed. Developer
messages are not shown in the event log.
Display sequence number
The sequence number of an event takes up considerable space in the event log window
and can be removed by deselecting it.
Siemens AG SP00-000.840.01.04.02 Event Log
Medical Solutions
10.05 CS SD 24
Page 5 of 46
6Event log
2 Event log
3-
Event log 0
The event log can be started from the service main menu by clicking the Event Log button
on the Navigation bar. The event log is started in a separate window so that it can be evaluated in parallel with other service functions. It opens with default values and the Function
Frame area is empty.
Enter event log 0
• Log in to Local Service.
• Open the event log.
Fig. 2: Event Log tool
Functional description of the event log 0
Domain
The event log is used to view and manage events. Events are collected in groups also
known as ’domains’. In order to make the event log more easily surveyable, each domain
has its own log file. Normally, only "Application” is used.
The following domains are selectable:
Application
CustomerLog
Security
System
Application (default) Messages from all running applications (e.g.: syngo®, database
applications, modality-specific applications) are recorded in this log file.
Event Log SP00-000.840.01.04.02 Siemens AG
10.05 CS SD 24
Page 6 of 46
Medical Solutions
Event log 7
CustomerLog The customer log shows service activities (e.g. if a local or remote service
session is active or a service application has been activated) to the customer in the
Remote Service Access Control Platform.
Security Security events are recorded in the security log file, e.g. attempts to log on to the
system. The security event trigger is normally turned off. It can be activated via the operating system User Manager application. Log in as administrator and start the User Manager application <Administrative Tools> <User Manager>. Then select the <Policies>
<Audit...> option to enable/disable the security events.
System The system log records events of operating system components. For example, a
driver that failed to launch during startup.
Severity
This is a classification of the error/messages supplied by the standard Windows® software.
Error
Warning
Information
All
Error - A function could not be completed because of a problem within the system; the
problem possibly cannot be handled internally (best search choice for rough error localisation).
Warning - A message to alert the user of a possible error condition; will be handled internally by the system.
Information - Any additional information that could be useful for troubleshooting and messages announcing that a function was completed successfully (e.g. status message concerning disk usage).
All - All severities will be selected (best choice for detail information).
Facility
The facility is a more detailed, syngo®-based classification of errors and messages. Four
facilities have been established and are displayed each in a different format. For an overview of the events use “Customer” and for detailed information use “Service.”
Siemens AG SP00-000.840.01.04.02 Event Log
Medical Solutions
10.05 CS SD 24
Page 7 of 46
8Event log
Facility Font
Developer Italics
Service Normal
Customer Bold
User-defined Normal
Developer messages classified as developer, service and customer messages are displayed.
See chapter on preconfiguration, under "Log only Service Messages".
Service (default) All messages classified as service and customer messages are displayed. Developer messages are not shown.
Customer messages classified as customer messages are displayed as a message box
on the monitor screen. This includes important error messages and also customer indices. These messages are displayed in bold in the event viewer.
User-defined Each modality (SP, AX, CT, MR,...) may define special (user-defined) additional facilities for each of the standard facilities (developer, service, customer) to get an
even more detailed, classified error/message.
Extended
All messages logged with the syngo® message logging mechanisms have additional
information stored as binary data that can be made visible by activating this checkbox.
Recommended for service.
NT Messages
If this option is selected, messages from the operating system (Win NT) are displayed
(e.g. driver initialization failed, process not started, etc.).
Default: Depends on the Domain selection. The NT Messages filter is automatically active
for System, Security and Customer Log. Recommended for service.
Search Pattern
This option is used to search for specific text in the Message Text area of the messages.
The search pattern is not case sensitive.
Event Log SP00-000.840.01.04.02 Siemens AG
10.05 CS SD 24
Page 8 of 46
Medical Solutions
Event log 9
Source name
The source name has the format <BU>_<Component>, e.g. the filming component is displayed as CAP_FL. The software factory uses the abbreviation CAP or CSA as the Business Unit identification. All other business units (divisions) use their regular abbreviations
(SP, MR, CT, AX....).
To reduce the number of messages, use wildcards. For example, ASP* is used to display
all messages where the source name begins with ASP.
Default: *
Examples of sources:
ASP_BIC
ASP_BSC
ASP_ASM
CSA_DB
ASP*
An explanation of source name abbreviations can be found in the chapters entitled “Imaging system source table” and “syngo® source table”.
Message ID
Use this option to search for a specific Message ID number. Enter the Message ID number to look for. This shows you how often a particular Message ID occurred in a certain
time period.
NOTE
You may find the same Message ID number in different sources.
Enter the filter source first (e.g. CAP_FL) and then define the Message ID you are looking for.
Search order
Default: Newest first
Newest first
The most recent of all filtered messages is displayed at the top.
Oldest first
The oldest of all filtered messages is displayed at the top.
Message limit
Defines the maximum number of message lines that are displayed in the output window.
Default: last 100 messages.
Depending on your own requirements, leave this field blank or type in a higher value to
get a larger number of messages.
Siemens AG SP00-000.840.01.04.02 Event Log
Medical Solutions
10.05 CS SD 24
Page 9 of 46
10 Event log
NOTE
Extract to File
Use this function to save the output results of the event log to a file.
Enter a file name like
ut1005_27_10_2003_EventLog.txt
Explanation of file name:
ut1005=product maintenance unit or Rdiag Prefix and system serial number
27_10_2003= creation date of the LogFile (day, month, year)
EventLog = Type of text file
The file is created in the C:\<medhome>\service\extract directory.
The name <medhome> varies depending on the product: for UROSKOP Access <medhome>=Aspia; ARCADIS systems <medhome>=Aspia; Digiscan M <medhome>=ASCR;
Mammomat NovationDR <medhome>=AWS
Please note that this value limits the output of the message lines.
For later evaluation, the file can be transferred to headquarters via FTP using the File &
Image Tools function.
The “maintenance unit” of the product can also be found under
Local Service/ Configuration/ Local Host/ Site Info.
Maintenance Unit/Rdiag Prefix Product
ut UROSKOP Access
MG Digiscan M
ot Siremobil ISO C
cv ARCADIS Varic
co ARCADIS Orbic
ca ARCADIS Avantic
mn MAMMOMAT Novation DR
Functional description of the event log file 0
The event log from the imaging system is based on the Windows® event log.
All entries in the event log are logged in chronological order starting with the system
boot-up.
Events are errors, warnings and information.
Event Log SP00-000.840.01.04.02 Siemens AG
10.05 CS SD 24
Page 10 of 46
Medical Solutions
Event log 11
In the event of an error, SW module processes are repeatedly stopped and restarted.
Thus error messages can occur repeatedly without affecting the user. You must therefore
always evaluate that day's entire event log.
Each event log should contain information, warnings and the error to monitor each occurrence.
Extended messages are also strongly recommended since this is where some software
modules provide detailed information.
The NT messages checkbox is also useful since system messages are logged in conjunction with the operating system.
Another way to get more information about an entry in the event log is to double-click the
ID number. A new information window then appears.
Explanation of the event log file:
The output from the event log is divided as follows:
Severity Date Time ID Source Message Text
Extended Info
Fig. 3: Event Log data
All severity entries are displayed with their abbreviations:
Severity abbreviation
Information I
Error E
Warnings W
Siemens AG SP00-000.840.01.04.02 Event Log
Medical Solutions
10.05 CS SD 24
Page 11 of 46
12 Event log
ID
The ID represents the special message number from the source that released the event. If
you double-click the ID, a detailed message window appears.
Source
The source contains the software component and its software module in a single name
(e.g. ASP_BIC).
Refer to the chapters on "Imaging system source table" and "syngo® source table".
Component Description
ASP_* Messages from system (Aspia)
CSA_* Messages from syngo®
CAP_* Messages from syngo®
Message Text
The message text gives you a general description of the event. If you have previously
selected the Extended checkbox, the extended text line with a time stamp provides additional information.
Time Range
This filter limits the output to the number of messages valid for the desired date and time
range.
Default: current day
From Enter the starting date and time of the range.
To Enter the end date and the time of the range.
Time (Default: previous hour) To enter a time range, select the Time checkbox. The time
fields are displayed.
NOTE
The time range should be kept as short as possible to avoid log
files containing several megabytes of data.
Event Log SP00-000.840.01.04.02 Siemens AG
10.05 CS SD 24
Page 12 of 46
Medical Solutions
Creating an event log file 13
3 Creating an event log f ile
4-
Creating an event log file 0
General 0
The event log can be started from the Service Main Menu by clicking the Event Log button
on the navigation bar. The event log is started in a separate window so that it can be evaluated in parallel with other service functions. This window opens with default values and
with an empty Function Frame area.
Event log 0
• Log into Local Service.
• Open the event log.
Fig. 4: Event Log tool
Creating an application event log
• Log into Local Service and select the “Event Log” from the menu bar.
The application event log consists of all messages of the imaging system components.
The following parameters have to be selected:
• Domain: Application
• Set time range (default, one whole day)
• Facility: Developer
• Severity: All
• Select the Extended checkbox.
Siemens AG SP00-000.840.01.04.02 Event Log
Medical Solutions
10.05 CS SD 24
Page 13 of 46
14 Creating an event log file
• Select the NT Messages checkbox.
• Leave Message Limit empty (default 100 lines).
• If required, extract the application event log to a file, e.g. ut(systemseri-
al#)_(DD_MM_YYYY)_AppEventLog.txt.
Example: “ut1005_27_10_2003_AppEventLog.txt”
Explanation of file name: ut1005= product prefix and system serial number; 27_10_2003=
creation date of the LogFile (day, month, year); AppEventLog= type of event log
• Click Go.
¹ An event log file is generated and written to c:\<medhome>\Service\extract.
Creating a system event log 0
The system event log consists only of messages from the operating system.
The following parameters have to be selected:
• Domain: System
• Set time range (default, one whole day)
• Facility: Developer
• Severity: All
• Select the Extended checkbox.
• Select the NT Messages checkbox.
• Leave Message Limit empty (default 100 lines).
• If required, extract the system event log to a file, e.g. ut(systemseri-
al#)_(DD_MM_YYYY)_SystEventLog.txt.
Example: “ut1005_27_10_2003_SystEventLog.txt”
Explanation of file name: ut1005= product prefix and system serial number; 27_10_2003=
creation date of the LogFile (day, month, year); SystEventLog= type of event log
• Click Go.
¹ An event log file is generated and written to c:\<medhome>\Service\extract.
Event Log SP00-000.840.01.04.02 Siemens AG
10.05 CS SD 24
Page 14 of 46
Medical Solutions
Loading...