Troubleshooting Guide PDF
Troubleshooting Guide PDF
Troubleshooting Guide PDF
h
ü
rM
e
s
u
ä
Event Log
SP
Troubleshooting Guide
System
Service Information
10048590
10047680
08080001
06646900
06601970
© Siemens AG 2005
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.
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 pro-
cedures.
Event log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Enter event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Functional description of the event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Functional description of the event log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Source table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Imaging system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Main systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Source table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
syngo® CSA source table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
syngo® CAP source table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
syngo® Versant source table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Copying files to CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Principle of copying files to CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Creating a new backup package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Back up your created package to CD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
• 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 mes-
sages 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.
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 eval-
uated in parallel with other service functions. It opens with default values and the Function
Frame area is empty.
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.
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 operat-
ing 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® soft-
ware.
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 localisa-
tion).
Warning - A message to alert the user of a possible error condition; will be handled inter-
nally by the system.
Information - Any additional information that could be useful for troubleshooting and mes-
sages announcing that a function was completed successfully (e.g. status message con-
cerning 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 over-
view of the events use “Customer” and for detailed information use “Service.”
Facility Font
Developer Italics
Service Normal
Customer Bold
User-defined Normal
Developer messages classified as developer, service and customer messages are dis-
played.
See chapter on preconfiguration, under "Log only Service Messages".
Service (default) All messages classified as service and customer messages are dis-
played. Developer messages are not shown.
User-defined Each modality (SP, AX, CT, MR,...) may define special (user-defined) addi-
tional 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.
Source name
The source name has the format <BU>_<Component>, e.g. the filming component is dis-
played as CAP_FL. The software factory uses the abbreviation CAP or CSA as the Busi-
ness 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 “Imag-
ing system source table” and “syngo® source table”.
Message ID
Use this option to search for a specific Message ID number. Enter the Message ID num-
ber 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 Mes-
sage 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.
NOTE Please note that this value limits the output of the message lines.
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
For later evaluation, the file can be transferred to headquarters via FTP using the File &
Image Tools function.
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.
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 occur-
rence.
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 conjunc-
tion 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.
Severity abbreviation
Information I
Error E
Warnings W
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 addi-
tional information.
Time Range
This filter limits the output to the number of messages valid for the desired date and time
range.
NOTE The time range should be kept as short as possible to avoid log
files containing several megabytes of data.
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 eval-
uated in parallel with other service functions. This window opens with default values and
with an empty Function Frame area.
Event log 0
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.
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(systemse-
rial#)_(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.
In the Site Directory are all of the files available for extraction.
General 0
With imaging system software version VA13C and later, all important log files of the imag-
ing system are written on a daily basis to a compressed file (LogFile.zip) during boot-up of
the imaging system. Example of a LogFile.zip: ut1005_12_01_2004_LogFiles.zip.
The imaging system manages log files for a max. of 12 consecutive days.
The present imaging system software version VA14X contains this zip file tool which is
installed and activated automatically.
Use the "spsavelogs" command from the command line of the imaging system (Utilities/
Escape to OS) to update the LogFile.zip at any time.
• Log into Local Service or Remote Service (Full Access Mode required).
• Select Utilities.
• Select Escape to OS from the selection bar.
• Enter "spsavelogs" in the parameter line.
• Click Go to update the current LogFile.zip.
Content of LogFile.zip 0
Location of LogFile.zip 0
Source Explanation
ASP_SCU Messages from UROSKOP Access
ASP_GEN Messages from Generator
ASP_XCU Messages from XCU Interface
ASP_BIC Back End Image Chain (image chain, ccd camera,
image disk)
ASP_DIS Messages from Image Chain, also Graphics Display
Manager, (Genesis card)
ASP_MIX Med Com Import/Export, Data exchange Aspia
syngo® (Versantd)
ASP_BSC Messages from image system, task information
ASP_CMN System shutdown messages
Versantd System start message from syngo® Versantd data-
base, only if NT Messages is selected in the event
log
CAP_AN Messages from archive to network, local and CD
Also refer to the chapter on Imaging system source table and syngo® source table.
• Check the system when it starts and how many times it is rebooted each day. (Refer to
"Boot table of imaging system" in this chapter)
• Burning CDs or network messages
! CAP_AN_XXX
• UROSKOP Access messages
! ASP_SCU_XXX
• After each system boot-up, the XCU component sends the message "Generator has
been turned on".
! ASP_XCU_XXX messages
• If the system has to be started twice in the morning (in case the customer switches the
system off in the evening), check to see whether the message CAP_PR_32 (message
text “Shutdown cancelled.“) is logged.
• Image chain messages:
! ASP_DIS and ASP_BIC
The image chain consists of:
- TV camera
- CCI board
- Genesis graphic board
- D1 power supply board from the image container
The boot and shutdown sequences of the imaging system of the UROSKOP Access
VA14X can be followed via the switch "System Messages on" in the event log. This allows
you to determine whether the imaging system is booting up and shutting down correctly.
Since it is not possible to list all start and stop events, the tables below contain the most
important events in chronological order.
Various error messages from network services (e.g. HIS/ RisServer failed) are possible
that are not listed here and are generally not significant.
General 0
Examples:
• Example of an Aspia SaveLog file:
- SaveLog_Service_VB11A_YBFR001210_10000_20040113_0616
- (SaveLog_Service_Software Version_computer ID_System Serial_Date_Time)
For technical reasons, the file extension .zip is not available for data transfer and must be
added to the file when it is to be opened externally. Example:
SaveLog_Service_VB11A_YBFR001210_10000_20040113_0616.zip
NOTE Do not add the “.Zip” extension in the extract folder, because the
“Burn Logs” operation might be prevented.
"Full access" rights are required to create SaveLog files via Remote Service. In addition,
the customer must enable access to the patient data.
The customer can no longer work on the system unless Full access is set to No access or
Limited access (permanent).
• The compressed service save log file contains the following log files.
- Application event log
- System event log
- Configuration files
- System logs
- License information
Usage 1:
To create a Service SaveLog file, press Ctrl+Alt (on the right)+S simultaneously.
! The Developer Savelog file is also generated.
Usage 2:
Create a SaveLog file from the service software
• Log into Local Service or Remote Service (see "Create SaveLog files from remote" in
this chapter).
• Select "Utilities".
• Select "Escape to OS" from the selection bar
• Select, depending on your request:
- "Aspia SaveLog" for Service Save log files or
- "Create Aspia Developer SaveLog" for Developer log files
"Create syngo® SaveLog" is not used for standard system log files.
• Click Go to create the requested SaveLog file.
Usage 3:
See the "Burn Log-Files to CDR" section of this chapter.
General 0
Ticket Id 0
The "TicketId" is located below the date of an event and is an extension of the Extended
Messages.
A "TicketId" is issued if an event in your procedure triggers a request that remains unan-
swered. This "TicketId" is included with all events involved in the procedure.
Source Explanation
ASP_MSY Messages from Main System (Varic / Orbic)
ASP_MSP Messages from Main System (Avantic)
ASP_NTD/TCI/TCA/ Messages from Main System (Orbic 3D)
TSM/TCA/COB
ASP_FIS Messages from Image Chain, also Graphics Display
Manager
ASP_ASM Messages from Aspia State Manager
ASP_MIX Med Com Import/Export, Data exchange Aspia
syngo® (Versantd)
ASP_BSC Messages from image system, task information
ASP_CMN System shutdown messages
MSSQLSERVER System start message from syngo® Versantd data-
base, only if "NT Messages" is selected in the event
log
CAP_AN Messages from archive to network, local and CD
Also refer to the chapters on "Imaging system source table" and "syngo® source table".
Troubleshooting tip 0
• Check the system when it starts and how many times it is rebooted each day. (See
"Boot table of imaging system" in this chapter)
• Database messages
! MSSQLSERVER_XXX (syngo® message)
• Burning CDs or network messages (syngo® message)
! CAP_AN_XXX
• Main System message (ARCADIS Varic / Orbic)
! ASP_MSY_XXX
• Main System message (ARCADIS Avantic)
! ASP_MSP_XXX
• Image chain messages
! ASP_FIS_XXX and ASP_BIC_XXX
• 3D Message (ARCADIS Orbic)
! ASP_TCI_XXX
• System message (Imaging System or Main System)
! ASP_XXX_XXX
General
In the process handling of the imaging system, the process requests are acknowledged
by the addressee. If there is no confirmation of receipt, a "TicketId" is issued and included
in all processes involved.
If a "TicketId" is available in the event log for an event, the earliest event with the identical
"TicketId" must be evaluated as the original event.
The original event has priority in the troubleshooting process in the event log of the imag-
ing system.
Prerequisite
"TicketId"s are issued for error, warning and information messages. Therefore a complete
event log should be available without restrictions when searching to determine how often
a "TicketId" occurs.
• Create an event log as described in the "Creating an event log file" chapter.
• Select a "TicketId" with the mouse.
The boot and shutdown sequences of the imaging system of the ARCADIS system can be
followed via the switch "System Messages on" in the event log. This allows you to deter-
mine whether the imaging system is booting up and shutting down correctly.
Since it is not possible to list all start and stop events, the tables below contain the most
important events in chronological order.
Various error messages from network services (e.g. HIS/ RisServer failed) are possible
that are not listed here and are generally not significant.
General 0
To save a patient image to send to USC or HSC, you need to export this image from the
patient browser to the CD burner.
General 0
To save a patient image to send to USC or HSC, you need to copy this image from the
patient browser to the ImageExport folder. The backup of the ServiceLogFilesExport
saves the content of the ImageExtract folder to CD-ROM.
Prerequisite 0
The import / export function of the service software must be configured. See also the con-
figuration instructions for the relevant product.
• Enter host name: see Configuration/ Local Host/ TCP/ IP/ Computer Name
• Enter TCP/ IP address: see Configuration/ Local Host/ TCP/ IP/ IP address of system
• Select logical HD device: define new
• Enter logical name: DICOMTools
• Enter path: C:\<medhome>\service\dst\img
The name <medhome> varies depending on the product: for UROSKOP Access <med-
home>=Aspia; ARCADIS systems <medhome>=Aspia; Digiscan M <medhome>=ASCR;
Mammomat NovationDR <medhome>=AWS
General 0
All source messages described in this chapter are normally used by the development
department. This chapter explains all messages in detail.
Imaging system 0
Configuration applet
Back end
Central components
Image chain
3D components
Service
Main systems 0
UROSKOP Access
ARCADIS systems
Digiscan M
MAMMOMAT NovationDR
General 0
All syngo® source messages described in this chapter are normally used by the develop-
ment department. This chapter explains all messages in detail.
The syngo® backup function is used for copying or burning data files to CD. To be able to
back up certain files using the backup and restore function, you need to create a new
backup package in Local Service/ Configuration.
Prerequisite 0
A CD burner must be installed and configured. Refer to the product configuration descrip-
tion for syngo® offline devices to find out how to configure a CD device.
To burn log files to CD at a later stage, you have to create a new backup package.
• Select Local Service/Configuration/ [Backup/Restore]
• Enter a new package name in the blank line above: ServiceLogFilesExport
• Click add
The new package name is displayed in the Package List box and is selected.
• Select Package Local.
• Define the directory or file names in the blank line “file & dir" one after the other. Wild-
cards (*) are also possible, e.g. C:\aspia\log\*
- C:\<medhome>\Log
- C:\<medhome>\Service\Extract
- C:\<medhome>\Service\html\Report
- C:\<medhome>\Service\html\GFX
- C:\<medhome>\service\dst\img
The name <medhome> varies depending on the product: for ARCADIS systems <med-
home>=Aspia; Digiscan M <medhome>=ASCR; Mammomat NovationDR <med-
home>=AWS
• Click add after each entry.
The new file or path selection is now visible in the files & directories list box.