HEALTHCARE Chapter 9

Imaging Services Troubleshooting

NX 3.0.9000
Type 4406/303

► Purpose of this Document

This document provides troubleshooting information, answers frequently asked

questions and supports with useful service activities.

► Document History

Edition. Release Changes

Revision Date
1.0 12-2016 • Initial version
• Changes compared to chapter 9, NX 3.0.9000: Added
following symptoms:
o NX does not start-up anymore after reboot of the
PC.
o NX Workstation in grace period after the Network
Adapter name has been renamed.
o NX upgrade or NX installation fails with SQLServer
2014 SP2 error message.

► Referenced Documents

Document ID Title
57082877 NX 3.0.9000 Service Manual

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0
12-2016 printed in Germany Document Node ID: 57096423
troubleshooting_chapter_e_template_v01_modified
Agfa Company Confidential Copyright © 2016 Agfa HealthCare N.V.
 Troubleshooting

► Manufacturer
Agfa HealthCare N.V.

Published by
Agfa-Gevaert HealthCare GmbH
Tegernseer Landstraße 161
D - 81539 München
Germany
Copyright  2016 Agfa HealthCare N.V.
All rights reserved.
Technical modifications reserved.
Agfa and the Agfa rhombus are trademarks of Agfa-Gevaert N.V., Belgium, or its
affiliates.
All other trademarks mentioned in this document are held by Agfa HealthCare N.V. or
the respective owners and are used in an editorial fashion with no intention of
infringement.
Nothing contained in this legal notice nor in any text in this document shall be
construed as granting by implication, estoppel or otherwise, any license or right to use
any of the trademarks, service marks, trade names or logos appearing in this document
without the express prior written consent of their respective owner.

WARNING:
Improper operation or service activities may cause damage or injuries.
(1) Read the "Generic Safety Directions" prior to attempting any operation, repair or
maintenance task on the equipment.
Refer to Document ID 11849633.
(2) Strictly observe all safety directions within the "Generic Safety Directions" and on
the product.

IMPORTANT:
The installation and service of the product(s) described herein is to be performed
by qualified personnel who are employed by Agfa HealthCare N.V or one of its affiliates
or who are otherwise authorized by Agfa HealthCare N.V. or one of its affiliates to
provide such services.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 2 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting

LIST OF CONTENTS

1 ISSUES AND SOLUTIONS ......................................................................................................8

1.1 Digitizer/ID-Tablet ..................................................................................................................... 8

1.1.1 Issue when trying to resend Images ......................................................................................... 8

1.1.2 Sometimes it takes a long Time to write an Image Plate (Cassette) ........................................ 8

1.2 Configuration Tasks .................................................................................................................. 9

1.2.1 Print Sheet Text Boxes empty and inaccessible in NX Configuration Tool .............................. 9

1.2.2 Configuration Tool start-up Error "Missing or wrong initial configuration of the database" ..... 9

1.2.3 Activating a Configuration gives Error about wrong Settings for partial Exposure ................. 10

1.2.4 When using the Digitizer Emergency Button, Images do not arrive on NX Workstation ........ 10

1.2.5 Error Message "Incorrect AE Title" ......................................................................................... 11

1.2.6 Test Connection to XRG-Modality returns Application Error .................................................. 11

1.2.7 Access denied to Agfa Dicom Bridge (ADB) Tool................................................................... 11

1.2.8 Changes made in the Agfa Dicom Bridge (ADB) Tool running on Windows 7 are active after
a Reset only ............................................................................................................................ 11

1.2.9 Error Messages when starting NX Viewer or Configuration Tool after Installation or Upgrade12

1.2.10 Configuration Tool not startable after Power Cut during Configuration Restore .................... 12

1.2.11 Test Connection does not work after AE Title or Port Number Change of the MUSICA MCE
Engine ..................................................................................................................................... 13

1.2.12 Images from Digitizer arrive but cannot be modified: All Buttons grayed out ......................... 13

1.2.13 CCM Tool not compatible with Windows 7, 64 bit .................................................................. 14

1.3 Upgrades................................................................................................................................. 15

1.3.1 Slow Performance after Upgrade from NX 1.0 (SU1) ............................................................. 15

1.3.2 NX doesn't start when logging in as User with Operator Rights ............................................. 15

1.3.3 Unable to activate XRDI Logging ............................................................................................ 16

1.3.4 Incorrect Accession Numbers are generated ......................................................................... 16

1.3.5 Configuration Data Import Message: Exception caught during import [Padding is invalid and
cannot be removed.] ............................................................................................................... 17

1.3.6 Recovering Data after failed automatic Import during Software Upgrade .............................. 17

1.3.7 Error when loading the License File before Activation ........................................................... 19

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 3 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting

1.3.8 Failure to start Licensing Service and to import Configuration, Image and Dose Data during
Software Upgrade starting from NX 2.0.8000 / 3.0.8000 ........................................................ 19

1.3.9 NX upgrade or NX installation fails with SQLServer 2014 SP2 error message ..................... 21

1.4 RIS .......................................................................................................................................... 22

1.4.1 RIS Query may become slow after Upgrade from NX 1.0 ...................................................... 22

1.4.2 RIS Query results in MESS27................................................................................................. 22

1.4.3 RIS Option “User Program” does not work ............................................................................. 23

1.4.4 Accession Number cannot be edited after Image has been received .................................... 24

1.4.5 Issue with DICOM Species and Breed description ................................................................. 24

1.5 Printing/Archiving .................................................................................................................... 24

1.5.1 Suboptimal Image Quality when printing 12 Bit OD................................................................ 24

1.5.2 Drystar 3000 true Size Printing ............................................................................................... 24

1.5.3 Logfile contains Errors concerning Printing or Archiving Jobs ............................................... 25

1.5.4 Wrong Characters on PACS (e.g. ' º ', ' cm² ') ........................................................................ 25

1.5.5 Image Appearance on PACS after Upgrade........................................................................... 26

1.6 Operating System (Windows XP) ........................................................................................... 26

1.6.1 Every Restart or Shutdown takes a very long Time................................................................ 26

1.6.2 Unable to log in using “crservice” Account ............................................................................. 27

1.6.3 Secure Dicom Communication stops working ........................................................................ 27

1.6.4 Windows Task Bar in front of NX ............................................................................................ 28

1.6.5 NX Installation or Activation fails with Application Error Messages ........................................ 28

1.7 NX User Interface ................................................................................................................... 29

1.7.1 NX Application does not start up anymore due to a corrupted Database .............................. 29

1.7.2 Double Cursor when adding Markers or Annotations ............................................................. 29

1.7.3 Scale Factor not shown in Status Box .................................................................................... 30

1.7.4 NX doesn't start after activating Configuration ....................................................................... 30

1.7.5 Fast Preview Image is not shown: Error Messages about AE Title are displayed ................. 31

1.7.6 Inverting Collimation Area is not working................................................................................ 31

1.7.7 Missing W/L Markers in the Histogram of MUSICA 2 processed Images ............................... 31

1.7.8 NX CMS Lock-up when switching between Thumbnails ........................................................ 32

1.7.9 After initiating a Shutdown of the NX Workstation the System keeps in Shut-Down State .... 32

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 4 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting

1.8 Exporting/Importing ................................................................................................................. 33

1.8.1 Opening Repeat/Reject Analysis File in Microsoft Excel ........................................................ 33

1.8.2 No Filename Extension for Dose Monitoring Export File ........................................................ 33

1.8.3 DICOM Export fails for "Unknown error" ................................................................................. 33

1.8.4 DVD burn Process stops......................................................................................................... 34

1.8.5 Exporting DICOM images fails ................................................................................................ 34

1.9 Licenses .................................................................................................................................. 34

1.9.1 Socket Error in License Manager Tool ................................................................................... 34

1.9.2 Grace Period starts if the Dongle is removed ......................................................................... 35

1.9.3 Error about “License service is not running” when going back to previous Windows Restore
Point ........................................................................................................................................ 37

1.9.4 NX does not start-up anymore after reboot of the PC ............................................................ 38

1.9.5 NX Workstation in grace period after the Network Adapter name has been renamed........... 39

1.10 Offline Config Tool .................................................................................................................. 40

1.10.1 Error saving new Configuration File on Offline Config Tool.................................................... 40

1.11 Viewing Priors ......................................................................................................................... 41

1.11.1 Unable to log in to Web1000 for viewing Priors ...................................................................... 41

1.11.2 Additional Internet Explorer Windows are displayed when retrieving Priors in Web1000 ..... 41

1.11.3 "Fatal exception" Error when refreshing the Internet Explorer ............................................... 41

1.12 Monitors .................................................................................................................................. 42

1.12.1 Installation of Barco Diagnostic Monitor fails .......................................................................... 42

1.12.2 Barco MFCD1219 TS does not work due to wrong Driver ..................................................... 44

1.13 Networking .............................................................................................................................. 44

1.13.1 NX CMS Lock-up when switching between Thumbnails ........................................................ 44

1.13.2 No Connection between CMS and NX in DX-D 100 ............................................................... 44

1.13.3 No Network Communication with DICOM Digitizer................................................................. 45

1.14 Image Processing ................................................................................................................... 45

1.14.1 Mammograms processed with "Mammo" or "Mammo T2" sporadically show Black Burn
Areas in the Skin Line ............................................................................................................. 45

1.14.2 NX User Manual does not give Instructions how to proceed if "Autocollimation" fails with
MUSICA 2................................................................................................................................ 46

2 FREQUENTLY ASKED QUESTIONS (FAQ) .........................................................................47

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 5 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting

3 USEFUL SERVICE ACTIVITIES ............................................................................................49

3.1 Cloning a NX System .............................................................................................................. 50

3.2 Resolving Port Conflicts .......................................................................................................... 51

3.3 Image Storage Capacity ......................................................................................................... 53

3.4 Running Internet Explorer ....................................................................................................... 53

3.5 Schedule an automatic weekly Reboot on the System .......................................................... 54

3.6 Checking Version Information with “About NX” (only available as of NX 2.0.6805) .............. 58

3.7 Check the ID Tablet Firmware Version Number ..................................................................... 58

3.8 Checking if an ALF matches a NX Workstation ...................................................................... 59

3.9 Forced Delete.......................................................................................................................... 60

3.10 Configuring the Auto Log Off / Screen Saver ......................................................................... 61

3.10.1 Lock the Screen by Password Protection of the current User (default Configuration after
Installation) .............................................................................................................................. 61

3.10.2 Configuring the Screensaver to log out the current User ....................................................... 62

3.11 Enabling the Service Mode for Digitizers ................................................................................ 63

3.12 Enabling the Service Mode for Archiving ................................................................................ 63

3.13 Saving the Adjustments of Musica 1 Settings (via NX GUI) to the Backup File ..................... 64

3.14 Recovering from Disk Failure on a RAID System ................................................................... 65

3.15 Recovering from a corrupted Database after Power Failure .................................................. 68

3.16 Handling Issues occurring during automated Data Import/Export .......................................... 69

3.16.1 Best Practices ......................................................................................................................... 70

3.16.2 One of the Exports fails........................................................................................................... 70

3.16.3 Import of the Configuration Data fails due to Verification Errors in the Data .......................... 70

3.16.4 Interrupted Import ................................................................................................................... 71

3.16.5 Images show red Crosses after Upgrade ............................................................................... 71

4 FAULT FINDING.....................................................................................................................72
4.1 NX System Snapshot .............................................................................................................. 73

4.2 System snapshot tool for the user (CTRL-ALT-I) ................................................................... 75

4.3 Attention Keys ......................................................................................................................... 76

4.4 View Logging........................................................................................................................... 76

4.5 Log Viewer Configuration........................................................................................................ 77

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 6 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting

4.6 Logging Namespaces ............................................................................................................. 78

4.7 Configure Logging ................................................................................................................... 79

4.8 Exporting and Importing Images ............................................................................................. 80

4.9 DICOM Validation ................................................................................................................... 81

4.10 Operational Statistics .............................................................................................................. 81

4.10.1 Viewing operational Statistics ................................................................................................. 81

4.10.2 Resetting a relative Counter ................................................................................................... 82

4.11 Finding Configuration Information on the ELMS ..................................................................... 83

4.12 Database Icon ......................................................................................................................... 83

4.13 NX Health Icon ........................................................................................................................ 83

4.14 Check installed Certificates..................................................................................................... 84

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 7 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1 Issues and Solutions

1.1 Digitizer/ID-Tablet

1.1.1 Issue when trying to resend Images

Symptom For example, a scrambled image is received from the digitizer. When trying to
resend it an error occurs.
Cause The error occurs because the software is implemented to ignore images being
sent twice.
Solution (1) Remove the original image from the study via image transfer and then resend
the image from the digitizer. NX gives following message:

Figure 1

(2) Click <OK>.

Result: The image is now received in an emergency study.

1.1.2 Sometimes it takes a long Time to write an Image Plate (Cassette)

Symptom Sometimes it takes several seconds to write a cassette.

More specific: Meant is the time between pressing the "ID" button and when it is
really written on the cassette.
Cause The software architecture only processes one operation on a session at a time.
While receiving an image on a session (i.e. storing the session and image data),
a simultaneous ID command will have to wait.
Solution Solution not applicable, normal behaviour

DOCUMENT CONTROL NOTE:

The controlled version of this document resides on the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 8 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.2 Configuration Tasks

1.2.1 Print Sheet Text Boxes empty and inaccessible in NX Configuration Tool

Symptom In the NX Configuration Tool, the print sheet text box configuration is lost and
configuration is not accessible anymore.
Cause Software bug
Solution Restore the factory default text box configuration:
(1) Go to: Device Configuration  Printers

Figure 2

(2) Click <Restore>. Following message appears:

Figure 3

(3) Click <Yes>.

1.2.2 Configuration Tool start-up Error "Missing or wrong initial configuration of

the database"

Symptom When starting the Configuration Tool, this error appears: "Missing or wrong initial
configuration of the database".
Cause Possible cause is a interrupted procedure to restore configuration
(e.g. power failure).
Solution (1) Go to: Start  Agfa  NX  Service  Install tools 
Reset NX Configuration Factory Defaults
(2) Start the Configuration Tool.
(3) Select Restore again.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 9 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.2.3 Activating a Configuration gives Error about wrong Settings for partial Exposure

Symptom Following error message is generated when activating the configuration:

"Error, check the exposure settings, modality settings, and printer settings of the
partial exposure. These settings can be wrong."
Cause From NX 1.0.3203 on, all partial exposure attribute settings of a FLFS (Full Leg Full
Spine) examination must be identical. An error in NX 1.0.2405 causes speed class
settings to be different for partial images of the same FLFS exmamination. When
activating this configuration, the error will be generated.
Solution (1) Navigate to the exposure type.
(2) Click: "View FLFS partial exposure" (at the top)
(3) Check that all settings are correct (e.g. Speed class) and correct them
if necessary.

1.2.4 When using the Digitizer Emergency Button, Images do not arrive on NX
Workstation

Symptom When using the digitizer emergency button, the images are not arriving on the NX
workstation.
Cause The digitizer CPF file contains the destination on the NX where emergency images
should be sent to. If the hostname of the NX Workstation is changed and the CPF
file is updated using the NX Configuration Tool, the emergency destination is not
updated and the digitizer cannot send to this emergency destination anymore.
Solution After changing the hostname of an NX workstation that is configured as emergency
destination, update the emergency destination in the CPF file manually, to reflect the
new hostname.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 10 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.2.5 Error Message "Incorrect AE Title"

Symptom When receiving images, an error is displayed about an incorrect AE Title.

Cause An AE Title of 16 characters or longer has been configured, e.g. for a digitizer.
Solution Modify the configuration to have only AE titles of maximum 15 characters
Reference HQ_0710220006

1.2.6 Test Connection to XRG-Modality returns Application Error

Symptom Testing the connection to an XRG-modality in the NX Configuration Tool returns an

application error.
Cause This happens if an ID Tablet is configured, but it is not connected or switched off.
Solution Switch on the ID Tablet and test the connection to the XRG-modality again.

1.2.7 Access denied to Agfa Dicom Bridge (ADB) Tool

Symptom When trying to start the Agfa DICOM Bridge (ADB) Tool, it cannot be started and an
error message is displayed.
Cause The logged on user has not sufficient rights to access the ADB tool folder.
Solution Log in using the “crservice” account to be able to use the ADB tool.

1.2.8 Changes made in the Agfa Dicom Bridge (ADB) Tool running on Windows 7 are
active after a Reset only

Symptom Changes made in the Agfa Dicom Bridge (ADB) Tool running on Windows 7 are not
taken into account.
Cause Different behavior of Windows 7 compared to Windows XP.
Solution After changes in the ADB Tool on Windows 7 either restart the ADB Service or
reboot the NX Workstation.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 11 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.2.9 Error Messages when starting NX Viewer or Configuration Tool after Installation
or Upgrade

Symptom After the installation or upgrade starting the NX viewer or the Configuration Tool
fails. One of these messages is displayed:
• Windows Event properties dialog:
".NET Runtime 2.0 Error for the System.data.sqlclient.sql"
• MESS279 "NX has encountered an internal error"
• MESS310 "The system has encountered an unexpected error"
• "Provider services not yet ready. Please try restarting the application."
• "An exception has occurred, please check the following error messages"
Cause After installation or upgrade there may be a delay in the startup of the database.
This causes this error.
Solution Start the NX viewer or Configuration Tool after some minutes waiting time.

1.2.10 Configuration Tool not startable after Power Cut during Configuration Restore

Symptom If a power cut occurs during restoring a configuration in the NX Configuration Tool,
the Configuration tool cannot be started anymore after the reboot. An Application
Error is displayed.
Cause Cutting of the power during the restore process is in progress leaves the database in
an inconsistent state.
Solution Reset the configuration data to factory settings and repeat the restore procedure:
(1) Go to: Start  Agfa  NX  Service  Backup Restore  Restore
Configuration Data
(2) Follow the instructions in the DOS prompt.
(3) Repeat the restore procedure in the NX Configuration Tool.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 12 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.2.11 Test Connection does not work after AE Title or Port Number Change of the
MUSICA MCE Engine

Symptom After adapting the AETitle or Port Number in the configuration of the MUSICA MCE
Engine as an Archive (Refer to Mammo Solution Manual chapter 3.04 - Appendices -
Configuration of the CR Mammography Musica MCE Image Processing Software) the
Test Connection does not work.
Note: Normally it is not required to change the default AE title or port number.
Changing the port number might be required if e.g. a port number conflict occurs (port
is also used for another application).
Cause The MUSICA MCE Engine must be restarted to start using the adapted AETitle or
Port Number
Solution For NX 2.0.8300 / 3.0.8300: Do not change the port number. This is not
supported.
For NX ≥ 2.0.8400 / 3.0.8400: Activate the configuration after change of AE-title
and port number. After this the test connection of the
archive will work.

1.2.12 Images from Digitizer arrive but cannot be modified: All Buttons grayed out

Symptom The images from the digitizer (DICOM digitizer DX-G, DX-M, CR 30-X 2nd) arrive
but cannot be modified: All Buttons are greyed out.
Cause In the “Workstation settings” in the configuration tool the “Performed Station AE
Title” is set equal to the “AE Title” for Fast Preview. In this case only the fast preview
images arrive on the NX.
Solution For DICOM digitizer DX-G, DX-M and CR 30-X 2nd: Give different names for
“Performed Station AE Title” and “AE Title” for fast Preview.
As of NX 2.0.8600 / 3.0.8600 following text is displayed in configuration tool menu
General Settings > Workstation settings:
(see red marked text in Figure 4)

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 13 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

Figure 4
Reference HQ_1011090001

1.2.13 CCM Tool not compatible with Windows 7, 64 bit

Symptom Following error is displayed if starting the CCM (Configuration and Customization
Manager) tool on a 64 bit Windows operating system:
The version of this file is not compatible with the version of
Windows you're running. Check your computer's system
information to see whether you need an x86(32-bit) or x64 (64-
bit) version of the program, and then contact the software
publisher.
Cause CCM tool not compatible with Windows 7, 64 bit
Solution Install the CCM tool on 32 bit operating systems only.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 14 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.3 Upgrades

1.3.1 Slow Performance after Upgrade from NX 1.0 (SU1)

Symptom Upon an upgrade from NX 1.0 (SU1) to a higher NX version, it is possible that the
system is initially a bit slower because it has a lot of clean-up work to do.
Cause On some sites, the cleanup in NX 1.0 (SU1) fails to work because of duplicate
date/time combinations.
Solution After one day, performance is back to normal.
The clean-up can be monitored in the 'closed exam' screen where the number of
sessions decreases.

1.3.2 NX doesn't start when logging in as User with Operator Rights

Symptom After upgrade of NX 1.0.3203 to , when logging in to the NX workstation as user with
operator rights. The NX application doesn't start up and the error message 278 is
shown.
Cause This error happens sporadically and is probably related to corrupted
Regional Settings data.
Solution Workaround 1:
(1) Log in to the defective user account.
(2) Open Regional Settings Panel.
(3) Select in the language drop-down any language, other than the intended
language.
(4) Select in the language drop-down the intended language for the user.
(5) Click <Apply>.
(6) Click <OK>.
It is required to select another language to force windows to correct the underlying
data for the correct language.
Workaround 2:
Remove and recreate the user with operator rights on Windows level.
Reference HQ_0706080013

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 15 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.3.3 Unable to activate XRDI Logging

Symptom The shortcut to "Activate XRDI logging" is not available in the Start menu.
Cause The XRDI (X-Ray Device Integration) installer adds the following item to the start
menu "Activate XRDI logging". When activating the NX workstation, this item is
removed from the Start menu within the list of possible debug loggings.
Solution This logging can still be activated via the folder C:\Agfa\Healthcare\NX\Bin\Service.

1.3.4 Incorrect Accession Numbers are generated

Symptom When the ADB tool is in use, incorrect accession numbers are generated after the
upgrade to ≥ .
Cause If no accession number is present in the image sent from NX, the default values in
the ADB configuration file (database.txt) can cause incorrect accession numbers to
be generated.
Solution (1) Log in as “crservice”.
(2) Go to: C:Agfa\Healthcare\ADB
(3) Open the ADB configuration file database.txt in a text editor.
(4) Remove the lines that mention the attributes:
ACCESSION-NUMBER-PREFIX and ACCESSION-NUMBER-MAPPING
(5) Save and close the file: database.txt

NOTE:
This issue can be seen on all versions of NX, but from
on, the default settings in the ADB configuration file do not contain these
attributes. However when upgrading an NX workstation to , the old settings
are copied.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 16 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.3.5 Configuration Data Import Message: Exception caught during import [Padding is
invalid and cannot be removed.]

Symptom Messages during Upgrade from NX 2008 and NX 2.0.8000 / 3.0.8000:

• Configuration data Import Status: FAILURE.
• Configuration Data Import Message: Exception caught during
import. [Padding is invalid and cannot be removed.]
At the end of the installation message the (wrong) message "The installation
was completed successfully" is displayed.
Cause Spoardic error in the licensing service.
Solution Workaround:
Step 1: Reload the license file.
Step 2: Reload the configuration data manually from directory:
Agfa\Healthcare\NX\Configuration\UpgradeData\Configura
tionData\ConfigurationExport.xml
Step 3: Activate the configuration.

1.3.6 Recovering Data after failed automatic Import during Software Upgrade

Symptom The upgrade installer wizard or the windows registry ImportAfterUpgradeInfo informs
about a failed automatic import of data.
Cause The automatic import of data was not completed successfully.
Solution Recover the system and import the data manually according to the failed import type.

IMPORTANT:
Perform the following actions only if the respective data import has failed:

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 17 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

• If the import of the Image data failed:

(1) Move the image pixel files from
D:\Agfa\Healthcare\NX\DataFiles\PreprocessedPixelFiles to
D:\Agfa\Healthcare\NX\DataFiles\UpgradeData\PreprocessedPixelFiles.

(2) Reset the NX to factory settings:

For Windows XP: Go to: Start  Agfa  Service  Install Tools  Reset
NX Completely to Factory Settings for <system type>
For Windows 7: Go to: Start  All Programs  Agfa  Service  Install
Tools  Reset NX Completely to Factory Settings for <system type>
(3) Import Configuration data manually. Refer to the instructions given in chapter
4, “Installation and Configuration Appendices”. The data to import is located
in folder:
C:\Agfa\Healthcare\NX\Configuration\UpgradeData\ConfigurationData
(4) Import Dose Statistic data manually:
Refer to the instructions given in chapter 4, “Installation and Configuration
Appendices”.
The data to import is located in folder:
C:\Agfa\Healthcare\NX\Configuration\UpgradeData\DoseStatistics
(5) Import the Image data manually. Refer to the instructions given in chapter 4,
“Installation and Configuration Appendices”.

• If only the import of the Configuration data failed:

(1) Import the Configuration data manually Refer to the instructions given in
chapter 4, “Installation and Configuration Appendices”. The data to import is
located in folder:
C:\Agfa\Healthcare\NX\Configuration\UpgradeData\ConfigurationData
(2) Reload the license file. For details refer to chapter 4, Installation.

• If only the import of the Dose Statistics failed:

(1) Import the Dose Statistic data manually. Refer to the instructions given in
chapter 4, “Installation and Configuration Appendices”. The data to import is
located in folder:
C:\Agfa\Healthcare\NX\Configuration\UpgradeData\DoseStatistics

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 18 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.3.7 Error when loading the License File before Activation

Symptom When you load the license file before upgrading to NX 2.0.8900 / 3.0.8900 following
error message appears: “License Mgr Exception: There is an error in XML document”.
Cause License Manger of software < NX 2.0.8800 / 3.0.8800 not compatible with license file
for ≥ NX 2.0.8800 / 3.0.8800.
Solution Do not load the license file before starting the upgrade, but load it during activation. For
details refer to NX Service Manual chapter 7, Upgrade Installation.

1.3.8 Failure to start Licensing Service and to import Configuration, Image and Dose
Data during Software Upgrade starting from NX 2.0.8000 / 3.0.8000

Symptom When performing a software upgrade starting from NX 2.0.8000 / 3.0.8000 following
software issue may appear:
NX Activation Utility Helper brings up messages:
- “Unable to connect to the Agfa Licensing service !”
- “ActivationHelper failed to install additional software” and only the close button is
enabled
After clicking the close button, the Activation Utility continuous.
At the end of the installation, failure to import configuration, image and dose data is
reported (Reason: Cannot start service Agfa.Licensing on computer).

Cause Installation of .NET3.5SP1 is occasionally (depending on timing) incomplete, due to locks

on the .NET runtime component. Installation will only be completed by rebooting the
system. As a result, the License Manager and the Licensing Service cannot execute prior
to the reboot..

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 19 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

Solution To prevent the issue:

Manually install .NET3.5SP1 and reboot the system prior to starting the upgrade
installation.
.NET3.5SP1 (Dotnet35x86.ZIP) is available on the Agfa HealthCare Library for download.
To repair the issue:
(1) After the failed NX upgrade installation, reboot the system. This will finalize the
.NET 3.5 SP1 installation.
(2) Stop the NX by selecting: Start > Agfa > NX > Service > Stop NX
(3) Start the License Manager and load the new license file.
(4) If additional software (e.g. XRDI or MCE) needs to be installed, launch the
Activation Utility Helper: Start > Agfa > NX > Service > Install Tools
> NX Activation Utility Helper”
IMPORTANT: DO NOT LAUNCH the NX Activation Utility, as this would
delete all image data.
(5) When the activation utility helper installed additional software, go to following
directory via Windows Explorer: C:\Agfa\Healthcare\NX\bin
(6) Doubleclick following file:
NX.Application.Visual.CommonTools.ImportAfterUpgrade.exe
(depending on the Windows explorer settings, the file may be displayed as
NX.Application.Visual.CommonTools.ImportAfterUpgrade)
(7) Select the type of data you want to import (Acquired dose records will not be
selectable when upgrading from an NX 8000 system).
(8) Click Import.

Figure 5

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 20 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.3.9 NX upgrade or NX installation fails with SQLServer 2014 SP2 error message

Symptom The installation of SQLServer 2014 SP2 fails sporadically, causing the NX installation
to stop with message that not all dependencies could be installed.
Cause Software issue.
Solution Restart the NX installation.
For upgrades from below NX 3.0.8950 reboot the PC before applying the update.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 21 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.4 RIS

1.4.1 RIS Query may become slow after Upgrade from NX 1.0

Symptom This issue only occurs on networks that do not use a DNS server and consequently
have the IP addresses configured in the Device Configuration of the Configuration
Tool:
When performing a RIS worklist query on a , it may take longer than on NX 1.0
systems. Independent from the number of worklist items, the query time is longer by
20-30 seconds.
Cause Normally, DNS queries should only be done for hostnames, not for IP addresses.
performs a DNS query although the IP address is configured for the RIS.
Result: The DNS query fails as there is no DNS server (this action takes about 20 -
30 seconds). After the DNS query will use the configured IP address and the
connection succeeds. NX1.0 did not show this behavior.
The issue is linked to the installed version of the .NET framework that is delivered
with the NX Software.

Solution (1) The local hosts file of the must be updated with IP addresses and hostnames
of the RIS/PACS.
(2) The hostnames of the RIS/PACS must be used in the Device Configuration of
the Configuration Tool instead of the IP-addresses.
For the detailed procedure refer to Service Manual chapter 04 “Installation and
Configuration”, section “Configuring Devices”.
Reference HQ_0707230004

1.4.2 RIS Query results in MESS27

Symptom RIS Query results in MESS27. This mainly happens if automatic query is configured
in the NX and several RIS devices are queried.
Cause A new RIS query request was received while a previous one was still busy (due to a
slow RIS or slow network),
Solution Workaround: Close the error message and wait for the RIS query which is still
running to finalize and return its results.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 22 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.4.3 RIS Option “User Program” does not work

Symptom The RIS option type “User program” is configured. When clicking the button
<RIS query> in the NX user interface to create the worklist, the user program does
not start up.
Cause The “User program” (.exe file) cannot be started from the NX application
(<RIS query> button).
Solution (1) Create a batch file somewhere on the NX that calls the executable file (exe) of
the RIS user program.
(2) Open the Configuration Tool and go to:
User Interface Configuration  Configure External Applications
(3) Check the checkbox: Worklist Environment
(4) Enter a caption for the button that is related to the function of the
user program.
(5) Set the path to the batch file by clicking the <Browse> button.
(6) In the Configuration Tool go to: Device Configuration  RIS
(7) Change the option in the drop-down menu from User Program to Data File.
(8) Check the checkbox: Remove DataFile
(9) If the path to the Data file is not entered yet, click the button <Browse> and
navigate to the data file that is generated by the User program.
(10) Activate the Configuration.
Test following procedure and inform the customer about the new procedure to query
the RIS:
(1) In the NX application Worklist window click the new button.
The user program is started.
(2) Perform the tasks requested from the user program (e.g. choose patient, enter
accession number, etc.). The user program generates the data file.
(3) Click the button <RIS Query>. The NX will fetch the data file and enter the
data into the Worklist.
Reference HQ_0610050006, HQ_0701310002

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 23 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.4.4 Accession Number cannot be edited after Image has been received

Symptom After the image has been received, it is not possible to modify the accession
number.
Cause This is normal behavior if MPPS is used.
The issue also appears if MPPS is not used on site but configured.
Solution Use the Configuration Tool to remove the configuration of the MPPS if it is not used
at the site.

1.4.5 Issue with DICOM Species and Breed description

Symptom When receiving the RIS list, the values in TAG 0010,2201 (Species Description) and
the TAG 0010,2292 (Breed Description) are correct. But when the values are shown
at the worklist or closed exams lists the values have changed place
Cause Software issue.
Solution In NX 2.0.8800 / 3.0.8800 SU1 the issue is solved. Note, that it is required to undo
the RIS mapping, if this was done to solve the issue in NX 2.0.8800 / 3.0.8800 (i.e. if
BreedDescription was explicitly mapped onto SpeciesDescription and vice versa).

1.5 Printing/Archiving

1.5.1 Suboptimal Image Quality when printing 12 Bit OD

Symptom When configuring NX to send 12 Bit OD (optical density) image data to the printer,
the printed image quality is not optimal.
Cause Some printers don't support the default NX pixel representation of '1' for this output
type, e.g. Drystar 3000.
Solution Configure NX to send 8 Bit image data.

1.5.2 Drystar 3000 true Size Printing

Symptom True size prints on Drystar 3000 are not true size.
Cause Drystar 3000 requires installation of PMS-file for true size printing from NX.
Solution Refer to the Drystar 3000 Service Documentation for installing the PMS-file.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 24 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.5.3 Logfile contains Errors concerning Printing or Archiving Jobs

Symptom After finishing a print job cycle, the log sometimes shows:

2005-12-06 12:47:30,786 [ 4592] - Dicom Printer status =

'ERROR'
2005-12-06 12:47:30,802 [ 4592] - printerStatusInfo (0x2110,
0x0020) = PRINTER DOWN
Or
Originator : DPM
Log severity : Error
Message : Dicom Printer status = 'ERROR'
Or
Originator : DPM
Log severity : Warning
Message : PrintJob ID associated with jobInstanceUID
'1.3.51.0.1.978593.20051024105101.8 ' not found in JobTable!
Or
Error : unacceptable PDU : reason = 1
Error : Close association to NNN failiure: A-RELEASE REQUEST
not confirmed 11.
Cause DICOM Library behavior
Solution This error can be ignored, because there is no effect on application behavior.

1.5.4 Wrong Characters on PACS (e.g. ' º ', ' cm² ')

Symptom Special characters may not be visible on the PACS, or may be displayed wrongly, or
may even cause the rest of a text to be cut off.
Cause For annotations the NX uses international symbols such as ° (degree sign), cm², ....
In some character sets this character is not available and thus cannot be translated
to DICOM.
Solution Configure the NX system to use extended character sets and combine the character
set to be used with ISO 2022 IR 6 (DICOM default repertoire, which contains these
characters).
An alternative is to use UTF-8 encoding (Unicode) ISO_IR 197, which also contains
these characters. Check whether the connected PACS system also supports this.
If one of the solutions described above are used, no information will be lost in the
GSPS when sending it to the PACS. It is still possible that the PACS viewer is using
a font that cannot display a certain character!

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 25 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.5.5 Image Appearance on PACS after Upgrade

Symptom The Windows Level (W/L) settings of images on the PACS are not in a ratio of
“50% - 50%”. This can result in:
• A very bright and less in contrast image appearance on the PACS compared to
the appearance before the upgrade.
• A very bright and less in contrast image appearance of normal Mammography
images compared to Micro Calcification Enhancement (MCE) images on the
PACS.
Cause Enabling the license NX MUSICA2 VOILUT WINDOWLEVEL in combination with
PACS archives that do not support or follow the DICOM standard can lead to the
described symptoms regarding the image appearance on the PACS.
Solution Workaround:
(1) Check the Connectivity Release documents of the PACS and of the
NX 3.0.9000 for mismatching DICOM settings.
(2) If the PACS cannot be setup to support and follow the DICOM standard,
disable the NX MUSICA2 VOILUT WINDOWLEVEL license in the NX
Configuration Tool.
Reference HQ_1003010001, HQ_1003260002

1.6 Operating System (Windows XP)

1.6.1 Every Restart or Shutdown takes a very long Time

Symptom Every restart or shutdown takes a very long time.

Users press the button to shut the system down and press it again too early to start it
up again.
The shutdown takes 2 to 3 minutes.
A blank screen appears during shutdown for half a minute or more.
Cause What causes this, is the enabled Windows setting:
“Clear Virtual Memory Pagefile = enabled.”
Solution This setting was introduced for security reasons, but it can be disabled again
manually in case a slow shutdown is considered as a problem:
(1) Open the Control Panel.
(2) Click Administrative Tools.
(3) Click Local Security Policy.
(4) Click the "+" next to “Local Policies”.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 26 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

(5) Click Security Options.

(6) Double-click Shutdown: Clear Virtual Memory Pagefile.
(7) Disable it.
This is the default setting from XOS version 1.0.20 onwards.

1.6.2 Unable to log in using “crservice” Account

Symptom Password is not accepted.

Cause The login dialog is sensitive to keyboard settings. A different keyboard layout might
have to be used when typing the password.
Solution (1) Go to Start  Settings  Control Panel  Regional & Language Settings.
(2) In the Languages tab, click <Details>.
(3) In the Settings tab, select the appropriate 'Default input language'.

1.6.3 Secure Dicom Communication stops working

Symptom Secure Dicom communication stops working (failing print/archive jobs). There are
different causes for this fault:
Cause 1 The public certificate of the NX has expired on the external Dicom device with which
the NX needs to communicate over SSL or has been removed accidentally. Refer to
section Fault Finding sub-section 4.14 “Check installed Certificates”.
Solution 1 Get a new certificate from a CA (Certification Authority) for the NX device and
upload it to the external DICOM device.
Cause 2 The public certificate of the external device with which the NX needs to
communicate over SSL has expired on the NX. Refer to section Fault Finding sub-
section 4.14 "Check installed Certificates”.
Solution 2 Get a new certificate from a CA (Certification Authority) for the external device and
install it on the NX (see chapter 5 Appendices, section ‘Secure Communication').

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 27 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.6.4 Windows Task Bar in front of NX

Symptom The Windows Task bar stays in front of the NX.

Cause If the Task Bar is "unlocked", it can be moved around.
Once moved to the right it will:
• Change the resolution of the NX screen and hide e.g. the LgM value in the
Edit screen.
• Not hide until user interface is restarted.
Solution (1) Go to: Start  Run and type gpedit.msc
(2) Go to: User configuration  Administrative Templates  Start Menu and
Taskbar
(3) Lock the Taskbar and enable it.
No need to reboot. This should lock the task bar immediately and grey out this
setting in the task bar properties.
Reference HQ_0712190001

1.6.5 NX Installation or Activation fails with Application Error Messages

Symptom Installation of the NX application or activation of the NX application fails and

database error messages are displayed. Running Configuration Tool or Activation
Utility also raises error messages.
Cause Network has been disconnected during installation or activation.
Solution (4) Reboot the system.
(5) Reset the system to factory defaults: Start  Agfa  NX  Service  Install
Tools  Reset NX Completely to Factory Settings prior to first Activation
(6) Restart the Activation Utility.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 28 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.7 NX User Interface

1.7.1 NX Application does not start up anymore due to a corrupted Database

Symptom Corrupted NX database after power failure: The NX application does not start up anymore.
In the Windows Event logging (part of the NX System Snapshot or accessible via Control
Panel > Administrative Tools > Event Viewer) an error message is displayed indicating a
severe problem with the NX database "ADC_QSdat.mdf".
Example error messages:
• SQL Server detected a logical consistency-based I/O error: incorrect checksum
(expected: 0xdfe952; actual: 0x1846eef2). It occurred during a read of page
(1:38305) in database ID 5 at offset 0x00000012b42000 in file
'C:\Agfa\Healthcare\NX\Configuration\SQLServerExpress\ADC_QSdat.mdf'.
Additional messages in the SQL Server error log or system event log may provide
more detail. This is a severe error condition that threatens database integrity and
must be corrected immediately. Complete a full database consistency check (DBCC
CHECKDB). This error can be caused by many factors; for more information, see
SQL Server Books Online.
• File ADC_QSdat.mdf appears to have been truncated by the operating system.
Cause The connected UPS is not configured properly or the user has shut down the system
without proper shutdown procedure.

Solution Preventive action:

• Configure the UPS as defined in Service Manual chapter 4, Installation and
Configuration Appendices.
• Inform the customer that an improper shutdown may lead to a corrupted database.
Corrective action: Perform the actions as described in section 3.15, Recovering from a
corrupted Database after Power Failure.

1.7.2 Double Cursor when adding Markers or Annotations

Symptom When adding markers or annotations, a double cursor is seen (a copy of the correct
one but a little grayer). This is seen in the Editing environment and in the
Examination environment.
Cause Only applicable to Dell 670 with Matrox cards: The video card settings are wrong.
Solution (1) Go to Display Properties  Settings and click <Advanced>.
(2) Set the Hardware Acceleration to the 3rd notch from the left
(Disable all DirectDraw and Direct3D Accelerations, etc.).

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 29 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.7.3 Scale Factor not shown in Status Box

Symptom Scale factor is not shown in the status box when NX is configured.
Cause This happens if:
• "True Scale" is configured in the Device Configuration  Printer  Sheet Text
Box and
• "Show true scale factor" is checked in the User Interface  Editing Settings 
Configure Normal Mode & Print Mode.
This can happen on a workstation with Dutch language settings because the default
label text is too long.
Solution Change the label from "Schaal aanpass..." to "Schaal:".

1.7.4 NX doesn't start after activating Configuration

Symptom Clicking Start NX Viewer doesn't start the NX application.

Cause The NX Workstation Service has been shut down and should be running before the
NX Viewer can be started.
Solution Restart NX: Start  Agfa  NX  Restart NX Completely

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 30 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.7.5 Fast Preview Image is not shown: Error Messages about AE Title are displayed

Symptom After digitizing an exposure, the Fast Preview image is not shown. Following error
messages are displayed:

Figure 6
Cause A Fast Preview AE Title length of 16 characters generates this error.
Solution Workaround: Use Fast Preview AE Titles shorter than 16 characters in the
CCM Tool and the Configuration Tool.
Reference HQ_0710220006

1.7.6 Inverting Collimation Area is not working

Symptom Draw two (or more) collimation areas (any shape), invert all of them and apply
collimation.
Cause The collimation areas are drawn as if they were not inverted, but with an extra
border added.
Solution Only a single collimation area can be inverted.

1.7.7 Missing W/L Markers in the Histogram of MUSICA 2 processed Images

Symptom Missing W/L Markers in the Histogram of MUSICA 2 processed Images.

Cause Due to new requirements as of NX2.0.8200/3.0.8200 there are no W/L markers in
the histogram of MUSICA 2 processed images anymore.
Solution Communicate the change to the users.
Reference HQ_1004060001

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 31 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.7.8 NX CMS Lock-up when switching between Thumbnails

Symptom The NX CMS is locking up when switching between thumbnails. The lock-up may
take half a minute or longer.
Cause Network adapter setting "Link speed & duplex" not set to "Auto Negotiation" but e.g.
to 100 Mbps Full Duplex at CMS and NX.
Solution Set parameter "Link speed & duplex" at all NX and CMS network adapters to "Auto
Negotiation".
Reference HQ_1004080003

1.7.9 After initiating a Shutdown of the NX Workstation the System keeps in Shut-
Down State

Symptom • After initiating a shutdown of the NX workstation, the system keeps in shut-
down state: The background is black and one can move the mouse. It is
possible only to switch-off the NX by holding the on/off switch on the PC front
panel long enough
or
• The NX workstation does not perform the shutdown or log-off command but
remains operational.
Cause Interaction with wrong LanSafe software.
Solution (1) De-install the LanSafe software that came with the UPS.
(2) Install the Lansafe software which is part of DVD2 of the corresponding NX
release: This is the NX compatible and tested Lansafe software.
Reference HQ_1009070003

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 32 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.8 Exporting/Importing

1.8.1 Opening Repeat/Reject Analysis File in Microsoft Excel

Symptom Depending on the MS Excel version observe the following situations:

• Excel 2000: The file cannot be opened.
• Excel 2002: The file can be opened without problems.
• Excel 2003: The file can be opened, but an error is shown: "There is a problem
with the specified XML or schema source. Click <OK> to have Excel create a
schema based on the XML source".
Cause Excel 2000: Not supported
Excel 2003: Date format incompatibility: See Solution.
Solution Workaround (Excel 2003): When exporting analysis data from NX, two files are
generated: The XML file containing the data and an XSD file containing the XML
schema of the data file.
Make sure to have both files available when opening the XML file in Excel 2003.

1.8.2 No Filename Extension for Dose Monitoring Export File

Symptom When exporting Dose Monitoring statistics, the export file has no default
filename extension.
Cause Software issue
Solution The export file contains data in XML format, so the user should explicitly provide a
filename with the extension ".xml".

1.8.3 DICOM Export fails for "Unknown error"

Symptom DICOM Export fails with error message "Unknown error occurred during export."
Cause This happens when McAfee Anti-Virus v8.0 is installed because it defines a security
rule: Prevent remote creation of autorun.inf files. This means copying a file called
autorun.inf to a mapped drive is forbidden.
This is part of the DICOM export process.
Solution (1) Go to McAfee VirusScanConsole  Access Protection  File  Share 
Folder Protection.
(2) Disable the security rule Prevent remote creation of autorun.inf files.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 33 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.8.4 DVD burn Process stops

Symptom Intermittently the DVD burning process started via the NX user interface stops and
the error message “Unknown error RefMess 163” is displayed.
Cause DVDs with insufficient quality have been used.
Solution Only use high-quality DVD media. For a recommendation of high-quality DVDs refer
to: http://www.digitalfaq.com/reviews/dvd-media.htm
Reference HQ_0910270001

1.8.5 Exporting DICOM images fails

Symptom Exporting DICOM images fails: No images on the DVD, despite the NX shows
“Done” at the end of the export process.
Cause Issue with DVD-RW media after a DVD-RW has been formatted.
Solution To prevent the fault observe following recommendations:
- Use of recordable media is preferred over rewriteable media
- DVD+R/RW is preferred over DVD-R/RW
- To reuse a DVD-RW, always choose "Format Disk" instead of "Erase Disk"

1.9 Licenses

1.9.1 Socket Error in License Manager Tool

Symptom When running the License Manager Tool, this error is displayed:

Figure 7

As a consequence of this error, the indication of remaining days in the Grace Period
may be wrong.
Cause Software issue
Solution Reboot the NX Workstation.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 34 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.9.2 Grace Period starts if the Dongle is removed

Symptom The user does not constantly use the application and removes the licensing dongle
for the time the application is not used.
The licenses for the application falls into status: Grace

Figure 8
Cause The Licensing service is automatically started as soon as the PC is started. Since
there is no dongle detected, the licenses fall into status Grace.

Solution A checkbox has been created in the License Manager tool to toggle between
enabled and disabled grace functionality.
Communicate following procedure to users who want to temporarily remove the
licensing dongle from the NX workstation:

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 35 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

(1) Log in to the NX workstation.

(2) Start up the License Manager tool from:
Start  AGFA  Service  License manager
(3) Go to the tab License Info.
(4) Uncheck the checkbox: Enable Grace Functionality:

Figure 9

(5) Click <Yes>:

Figure 10

(6) Close the License Manager tool.

(7) Remove the dongle from the USB port of the NX workstation.

NOTE:
When reconnecting the dongle, follow the procedure in reversed order:
(1) Reconnect the dongle.
(2) Check the checkbox: Enable Grace Functionality.
Reference HQ_0811200002

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 36 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.9.3 Error about “License service is not running” when going back to previous
Windows Restore Point

Symptom When going back to a previous Windows restore point, in some cases the licensing
service cannot be started.
NX does not start-up, but gives error message: License service is not running.
Please start the service.
When trying to start the licensing service manually, following error message is
displayed: “Windows could not start the Agfa License Service on local computer.
Error 1053: The service did not respond to the start or control request in a timely
fashion.”

Cause Cx licensing uses CodeMeter from Wibu since NX 2.0.8800 / 3.0.8800.

This Wibu CodeMeter in some cases shows following behavior: When going back to
a previous restore point (eg. triggered by FSE), the internal Codemeter license gets
invalid.

Solution (1) Download file “Protection_Only-License.WibuCmRaU” from the Agfa

HealthCare Library.
(2) Copy the file to the NX (e.g. D: partition).
(3) Click the codemeter icon in the
taskbar.

Figure 11

The codemeter screen opens.

Status: Activation invalid.

Figure 12

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 37 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

(4) Drag and drop the file to the

codemeter control center:
The status changes to: “License
activated”.
(5) Close the Codemeter control
center.
(6) Restart the computer.

Figure 13

1.9.4 NX does not start-up anymore after reboot of the PC

Symptom NX does not start-up anymore after reboot of the PC. The error message displays
“internal error”.
Cause System clock set back to default (e.g. 1.1.1970) because battery on motherboard is
empty.
Solution Replace battery on motherboard. Consider to replace the PC. Refer to the existing
NX hardware upgrade programs.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 38 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.9.5 NX Workstation in grace period after the Network Adapter name has been
renamed

Symptom After renaming the network adapter from default “Local Area Connection” for
example to “Connection to Hospital” the NX Workstation is in grace period.
The issue appears in NX 3.0.8950 and may also appear in NX 3.0.9000
Cause As of NX 3.0.8950 the software looks for the network adapter name "Local Area
Connection XYZ" to determine the MAC Address of the network adapter on the PC's
motherboard. In case of a different name the licensing service fails to retrieve the
MAC address of that adapter.
Solution When renaming the network adapter hosted by the motherboard make sure its name
starts with “Local Area Connection”, for example “Local Area Connection to hospital”.
Reference PRB0054680; NX 3.0.9000 SB01, Document ID 57096072.

NOTE:
In case several network adapters are installed on NX it can be useful to rename the
adapters to meaningful names. This makes it easy to identify the purpose of the network
adapter. The network adapter can be renamed in menu Control Panel > Network and
Sharing Center > Change Adapter Settings.
The adapter belonging to the motherboard is usually the first in the list. This can be double-
checked by executing "ipconfig /all" in a command window and checking the IP address
assignment for that adapter.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 39 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.10 Offline Config Tool

1.10.1 Error saving new Configuration File on Offline Config Tool

Symptom After creating a new configuration file from scratch on the Offline Config Tool, this
error is listed when trying to save the file:

Figure 14
Cause Licenses are read from the database representation on the Offline Config Tool
system. Only when the file is deployed on an NX Workstation, the licenses are read
from the ALF.
Solution Workaround: Manually disable one of the licenses in the Offline Config Tool before
saving the configuration file.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 40 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.11 Viewing Priors

1.11.1 Unable to log in to Web1000 for viewing Priors

Symptom Error message when viewing priors using Web1000: "Unable to log in: An unknown
error occurred, check the local log".
Cause Limitation on number of logged in users (max. 50), when using EPR demo license
on Web1000.
Solution Retry when less users are logged in.

1.11.2 Additional Internet Explorer Windows are displayed when retrieving Priors
in Web1000

Symptom When retrieving prior images from IMPAX using Web1000, additional
Internet Explorer windows are temporarily appearing.
Cause Normal behaviour
Solution None, the windows can be closed without disturbing the operation.

1.11.3 "Fatal exception" Error when refreshing the Internet Explorer

Symptom After retrieving the studies from IMPAX and transferring them to WEB1000, the prior
list is not automatically updated. Refreshing the Internet Explorer screen will end in a
"fatal exception" error.
Cause Normal behaviour
Solution (1) Close the Internet Explorer window.
(2) Press the <Priors> button again.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 41 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.12 Monitors

1.12.1 Installation of Barco Diagnostic Monitor fails

Symptom After installing the drivers for a Barco diagnostic monitor, following error message is
displayed:

Figure 15

The installation of the Barco diagnostic monitor fails.

Cause Improper application of the installation process
Solution 1 The complete process is described in the Service Manual chapter 5 Monitor Options
and has been updated with supporting information.
If the process still fails try to uninstall and re-install the drivers:
(1) Go to: Start  Settings  Control Panel
(2) Choose: Add or Remove Programs
(3) Select the Barco nio Display Driver and click <Change/Remove>.
(4) Follow the instructions on the screen to uninstall the driver. If the driver cannot
be uninstalled refer to Solution 2.
(5) Repeat the driver installation procedure described in the
Service Manual chapter 5 Monitors Options.
Solution 2 If the driver cannot be uninstalled from the system the dialog Add or Remove
Programs displays following error:

Figure 16

In this case following procedure is recommended:

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 42 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

WARNING:
Electrical device. Electric shock possible.
Always switch off the equipment and unplug the power cord, before
disconnecting or connecting cables on printed circuit boards.

Static discharge! Electrical components may be destroyed.

For the repair on electrical components, wear a grounding strap
(CM+9 9999 0830 0) around the wrist and connect the other end of this
strap on a grounded conducting metal piece.

(1) Open the NX PC housing.

(2) Remove the already installed Barco display controller from the
PCIe expansion slot.
(3) Install the original display controller in the PCIe expansion slot.
(4) Close the PC housing.
(5) Perform a Clean Installation according to the procedure describe in the
Service Manual chapter 5 Clean Install Procedure.
(6) Repeat the installation of the monitor according to Service Manual chapter 5
Monitor Options.

Reference HQ_0902230002

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 43 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.12.2 Barco MFCD1219 TS does not work due to wrong Driver

Symptom After installation the Barco MFCD1219 Touchscreen does not work.
Cause The wrong driver is installed. During installation of the driver the Windows dialog
New Hardware found is displayed. If multiple drivers are found, the wrong driver may
be highlighted by default.
Solution (1) Go to: Computer Management  System Tools  Device Manager  Mice
and other pointing devices
(2) Uninstall the installed touchscreen driver.
(3) Install the correct driver according to the procedure in chapter 5 Monitor
Options.

1.13 Networking

1.13.1 NX CMS Lock-up when switching between Thumbnails

Symptom The NX CMS is locking up when switching between thumbnails. The lock-up may
take half a minute or longer.
Cause Network adapter setting "Link speed & duplex" not set to "Auto Negotiation" but e.g.
to 100 Mbps Full Duplex at CMS and NX.
Solution Set parameter "Link speed & duplex" at all NX and CMS network adapters to "Auto
Negotiation".
Reference HQ_1004080003

1.13.2 No Connection between CMS and NX in DX-D 100

Symptom A CMS is active in the LAN network. The DX-D100 starts up when LAN and WLAN
are connected. The CMS reports the following error: "The recieved in room station
IP address differs from retrieved address by in room hostname".
There is no connection possible CMS to NX.
Cause The NX gives the IP address of the WLAN istead of the LAN to the CMS when CMS
sends out his broadcast.
Solution Workaround to solve the problem: Disable the wireless connection at the NX in the
DX-D 100 and reboot the NX: Now the CMS can connect to the NX.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 44 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

1.13.3 No Network Communication with DICOM Digitizer

Symptom Case 1: No network communication with a DICOM digitizer, if two network interfaces
are used in NX (2nd network interface for connection to DR detector in a mixed
CR/DR system)
OR
Case 2: No network connection to a DICOM digitizer if used in a point-to-point
network connection (direct network cable connection between digitizer and NX).
Cause Case 1: Wrong assignment of IP addresses.
Case 2: In a point-to-point network connection with the digitizer, the NX PC has no
activate network connection at boot time if the digitizer is not switched on. Windows
reports the LocalHost 127.0.0.1 address as the system’s IP Address.
As a result, in both cases, the NXWorkStation service is listening on the wrong IP
address for SYNC messages coming from the digitizer.

Solution Following solution is available in NX < NX 3.0.8950 only (as of NX 3.0.8950 the
configuration of a fixed IP address is not required anymore): Set a fixed IP address
for the NX workstation in the Config Tool > General Settings >
Workstation Settings > IP address > Advanced ... window.
In case of a point-to-point network connection with the digitizer: Configure this fixed
IP address also in the Windows network properties of the NX.

1.14 Image Processing

1.14.1 Mammograms processed with "Mammo" or "Mammo T2" sporadically show

Black Burn Areas in the Skin Line

Symptom Mammograms mostly of big breasts sporadically show black burn areas in the skin
line of the breast. Images as of NX 2008 (NX 3.0.7000) are affected, where
examinations are processed with package "Mammo" or "Mammo T2" and the
license NX_MAMMO_DARKENING is enabled.
This issue is visible on the NX workstation monitor, and in exceptional cases also
on hardcopy prints and on the softcopy monitor.

Prerequisite that the symptom appears at a hardcopy print:

• The user changes Window/Level at the processed image.
Prerequisites that the symptom appears at a softcopy station:

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 45 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Issues and Solutions

• Archive output type configured for 8 bit PVAL or 12 bit PVAL.

• The user changes Window/Level at the processed image.

Cause Already saturated (overexposed) pixels e.g. in the skin line of big breasts, will be
highlighted when using “background darkening” function when examinations are
processed with the "Mammo" or "Mammo T2" package.
This issue will be even more highlighted if the Window/Level function is used. For
more information about the cause of this, read the following background
information:
Background The image processing for background darkening of a mammography image is
Information based on two techniques:
• If no Window/Level is applied or if the Window/Level is adjusted slightly, the
pixel padding range technique defines a range of pixel values containing the
pixel values of the background regions in the image.
• If Window/Level is applied extensively, the background region is defined by a
bitmask. I.e. a mask that indicates for every pixel in the image whether the pixel
is part of the background region or not.
If the image contains clipped pixels in the diagnostic area (e.g. the breast edge),
these pixels may be darkened together with the background when Window/Level is
adjusted slightly. This becomes visible if the image is inverted.
This behavior has no impact on diagnosis.
Solution Instruct the customer not to combine Window/Level with background darkening.
The NX user manual is adapted accordingly.
Reference HQ_0911050001

1.14.2 NX User Manual does not give Instructions how to proceed if "Autocollimation"
fails with MUSICA 2

Symptom Musica 2 image processing ("Autocollimation") may fail rendering very dark images.
With Musica 1 users were told to apply "Manual Collimation" to recover good image
quality, but this does not work with Musica 2.
Cause User Manual does not give instruction how to proceed if "Autocollimation" fails.
Solution The workaround to apply manual W/L to recover good image contrast is described in
the user manual for NX 2.0.8400 / 3.0.8400 (and higher versions).
Reference HQ_0907170001

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 46 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Frequently Asked Questions (FAQ)

2 Frequently Asked Questions (FAQ)

Question 1 What to do in case of Musica pre-processing Failures?

Answer In case of a Musica pre-processing failure, the image will be put in a separate folder.
In the viewer and in the logging, there will be a clear indication that this has occurred.
The image itself (for analysis by the MEDICAD team) can be found at the
following locations:
D:\Agfa\Healthcare\NX\DataFiles\DicomAcquiredFiles\Refused (Dicom digitizers) or
D:\Agfa\Healthcare\NX\DataFiles\Refused (Twain digitizers)
These images can be attached to the report for further analysis, when reporting the
case via the escalation channels.
The image is stored as a DICOM file without patient-demographic information in case
the image came from a DICOM digitizer (e.g. ADC Solo). It is composed out of a pixel
file and a demographics file in case that image came from a Twain digitizer.

NOTE:
• Musica pre-processing failures should rarely occur. However, it was of utmost
importance to foresee how the system will react on this, because otherwise the
system would come into a state where it constantly retries to acquire the image.
• In NX, a message will pop up on the screen asking the operator whether or not to
retry the image-processing, prior to actually refusing the image. If the issue is
caused by a temporal problem, the retry can work and the image will not be
refused. In case the issue is data-related, every subsequent retry will fail
(resulting in the refusal of the image).

Question 2 What to do in case of Digitizer Connectivity Issues?

On the digitizer (Tablet ID), the following message is displayed:
‘Station xxxx is not known’.

Or in case of Fast ID: Red light is flashing and the message:

‘Service error 8 (ERR_WTC, WaitC in progress…’ is displayed on the display of the
digitizer.
Answer 1 This is most likely caused by the fact that the processing station name defined in NX
and the processing station name in the CPF file of the digitizer are not identical.
Note that ‘identical’ also means that the same capitalization should be used.
Answer 2 There are too many stations defined in the CPF file, causing the digitizer not to import
all of them. Note that it is undefined which ones will fall out.
To resolve, reduce the number of processing stations in the digitizer CPF file.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 47 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Frequently Asked Questions (FAQ)

Question 3 How to trace the CR Cassette/Detector an Image has been exposed on?
Answer If there are doubts about the origin of artifacts on an image, it is useful to determine
the respective CR cassette/detector, the image has been exposed on:
(1) Select the image in the Image Overview of the Main Menu in the NX Viewer.
(2) Click the link View All Image Attributes.
(3) Find the label Detector ID and note it down.
(4) For CR Cassettes:
Compare the Detector ID
with the Cassette Number
of the CR cassettes and
find the matching one.
The Cassette Number of
the CR cassettes can be
read out using the RF Tag
Initialization Tool:

Figure 17

NOTE:
For detailed information about the RF Tag Initialization Tool refer to the
Service Manual chapter 5 Using the RF Tag Initialization Tool.

For Detector Cassettes (DX-S / DX-G):

Compare the Detector ID with the IP
serial number written on the label of the
IP chip of the cassettes and find the
matching one. The IP serial number is the
second part of the number printed on the
label. In the example below, the IP serial
number is “7CBQMK0002”:
Figure 18: Example for IP serial number

NOTE:
For detailed information about the pane View All Image Attributes refer
to the NX User manual on NX Startekit DVD 1.

Result The CR cassette/detector that contains the matching Cassette Number/IP serial
number is the CR cassette/detector the image has been exposed on.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 48 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

3 Useful Service Activities

Overview: See section:

1. Cloning a NX System 3.1

2. Resolving Port Conflicts 3.2

3. Image Storage Capacity 3.3

4. Running Internet Explorer 3.4

5. Schedule an automatic weekly Reboot on the System 3.5

Checking Version Information with “About NX” 3.6

6.
(only available as of NX 2.0.6805)

7. Check the ID Tablet Firmware Version Number 3.7

8. Checking if an ALF matches a NX Workstation 3.8

9. Forced Delete 3.9

10. Configuring the Auto Log Off / Screen Saver 3.10

11. Enabling the Service Mode for Digitizers 3.11

12. Enabling the Service Mode for Archiving 3.12

Saving the Adjustments of Musica 1 Settings (via NX GUI) 3.13

13.
to the Backup File

14. Recovering from Disk Failure on a RAID System 3.14

Recovering from a corrupted Database after Power 3.15

15.
Failure

Handling Issues occurring during automated Data 3.16

16.
Import/Export

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 49 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

3.1 Cloning a NX System

NOTE:
Do not try to clone a system using NX backup and restore. Instead, it is advised to use
the Configuration Tool:

On the main system:

(1) Load the active configuration.
(2) Use the Save as… option to export the full configuration to a file that can be
loaded on the ‘clone’ system.

On the ‘clone’ system:

(1) Install the ‘clone’ system’s certificate and the certificates of the other DICOM
systems (SSL only). See NX 3.0.9000 Service Manual chapter 4 Installation and
Configuration Appendices, section 'Secure Communication', for more information
on how to do this.
(2) In the Configuration Tool Select Load the configuration via an external file and
browse to the file that has been exported from the main system.
(3) The Configuration Tool will now load the file into its workspace.
(4) Browse to workstation settings, and change:
• ID Station name
• Performed station AE title
• Fast preview AE title (If enabled)
• Performed location (optional)
(5) Browse to Device configuration / RIS (RIS only).
(6) Change the list of scheduled AE titles (when needed).
(7) Browse to Security / Configure SSL settings.
(8) Enter the common name of the clone’s certificate (SSL only).
(9) Activate the settings.

NOTE:
The ‘clone’ system will only look ‘identical’ to the master system in case that on both
systems the same licenses are available. Also the authorization of the logged in user
can cause the system to look differently (certain options are disabled).
Example:‘Print’ view was configured on the master system ‘Normal’ view is shown on
the cloned system, because there is no Print license available on the machine.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 50 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

3.2 Resolving Port Conflicts

In case of port conflicts, typically the NXWorkstation service will not start up, and when
opening the log file NX.Application.NonVisual.NXWorkstation.exe.log the error:
‘java.BindException’ can be found.
It is possible that after configuring NX one or more of its services are not able to open a
DICOM port for listening. This means that another program has taken control over one
of these ports, for example a RIS client.
TCP/IP port conflicts on the local NX PC can be caused by:
• Standard Windows applications such as Remote desktop.
• 3rd party applications (e.g. RIS) installed on the NX PC.

NOTE:
Many applications assign ports dynamically.
This does normally not cause a problem because the NX backend starts up when the
system starts up. But when started up from the Configuration Tool (or when another
application is using the same fixed port), a conflict can occur.

NX has a listening port for Fast–ID, storage SCP and storage/commit SCP, so it is
advised to check whether no other applications are claiming any of these ports.
Following simple DOS commands can help to find the conflicts:
(1) Go to Start  Programs  Accessories  Command Prompt to open a DOS
command window.
(2) Type ‘netstat /a’ in a command window to see the list of ports in use.
If running this prior to running NX (make sure that the NX workstation service is
not running), the free ports on the system become visible:

Figure 19

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 51 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

(3) Type NetStat /a /o into a command window to display the process ID (PID)
next to each port that is used:

Figure 20 – Command window

(4) Find out which process is using the ID in the Windows task manager:

Figure 21 – Task Manager

(5) Additionally: It is possible to verify which application is claiming a certain port

using a tool such as: TCPView (downloadable at http://www.sysinternals.com/.
Agfa cannot distribute this tool freely, but it can be downloaded at no cost).

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 52 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

3.3 Image Storage Capacity

The Image storage capacity depends on preferences, such as the set number of days
an image will be kept on the system.

NOTE:
• Sessions are deleted from the system if they are older than the configured
maximum number of days or if room on the disk is low, meaning less space
than 2 GB.
• Only closed sessions for which printing or archiving is done, not just requested,
can be deleted automatically.
Sessions cannot be deleted automatically if:
• They are locked.
• They are younger than 24 hours.
Manual cleanup may be necessary for sessions that do not properly end printing or
archiving (e.g. pending storage commitment) or that are younger than 24 hours in case
disk size is very critical.

IMPORTANT:
On manual cleanup:
• Pending jobs will be removed from the queues.
• Active jobs will be continued.
The maximum number of days to keep sessions can be configured in the
NX Configuration Tool  Workflow Management  Identification-Examination 
Storage pane.

3.4 Running Internet Explorer

Windows Internet Explorer is started by running the Windows Explorer (file browser)
and typing an http URL (http://...) in the address bar.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 53 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

3.5 Schedule an automatic weekly Reboot on the System

NOTE:
When scheduling the automatic reboot, it should be set to a time when the NX will not
be used, e.g. during the night.

IMPORTANT:
Be aware, that it might be impossible to schedule this automatic reboot in emergency
departments where the system needs to be running at any moment.

(1) Log on to the system using an administrator account (e.g. crservice).

(2) Go to Start  Program files  Accessories  System Tools
 Scheduled Tasks.
(3) Double click on <Add Scheduled Task>:

Figure 22

(4) Click <Next>:

Figure 23

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 54 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

(5) Click <Browse…> to open file browser dialog.

Figure 24

(6) Browse to C:\windows\system32\shutdown.exe.

This utility allows rebooting a PC.

(7) Give the task an appropriate name (e.g. “ShutdownNX”) and select the
frequency of the shutdown (Weekly).

Figure 25

(8) Click <Next>.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 55 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

(9) Select the start time (= time when the system is preferably not used or
rarely used).

Figure 26

(10) Finally, enter the user name and password under which this task may run.
Click <Next>:

Figure 27

NOTE:
• The task will run under this profile independent of the fact that
somebody is logged in or not. Preferably, use an administrator
account to run this task (e.g. crservice). Note that this does not
need to be a local account. In a domain setup, also a domain
account can be used. After the reboot, a user with log-in rights
must be present to log in.
• In case of password expiration, the task will cease to run.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 56 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

(11) Check Open advanced properties for this task when I click Finish and
click <Finish>.

Figure 28

(12) In the following window, enter the following ‘Run’ command:

C:\windows\system32\shutdown.exe –r –t 60 –f

Figure 29

(13) Click <OK>.

Result The weekly automatic reboot has been scheduled.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 57 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

3.6 Checking Version Information with “About NX”

(only available as of NX 2.0.6805)

The “About NX” utility creates a “snapshot” of the currently installed system and lists all
version related information:
• The installed NX version
• Dose Type
• NX Usage Information (Disk space)
• The installed Hotfix / Documentation CD version
• The installed languages
(which were installed using the language CDs)
• NX Component versions
• Installed licenses
• XRDi version information
This tool can be accessed using: Start  Agfa  NX  Service  About NX …

3.7 Check the ID Tablet Firmware Version Number

(1) Search the NXWorkstation log files for text FirmwareInfo. For a detailed
description refer to section “Fault Finding” sub section “View Logging”.
(2) Find out the version number by the text similar to the following example:
1007 ID-TABLET 1.12.07 06/17/05 00005054 1.11.13

Explanation:
• 1.12.07 represents the version of the firmware.
• 5054 is the serial number of the reader.
• 1.11.13 represents the version of the driver on the PC.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 58 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

3.8 Checking if an ALF matches a NX Workstation

(1) Start the Cx License Manager Tool.

(2) Click on the Security Info tab.
(3) Read out the Mac address of the machine and the Serial Number of the dongle:

Figure 30

(4) Open the ALF-file using Internet explorer.

IMPORTANT:
Do not change the content of the ALF and do not save any changes
that have been made unintentionally!
Any changes would invalidate the license file.

(5) Locate the Mac adress in the license file. Do this by searching for the string
HardwareKey (in the XML section ‘FingerprintFile’). The Mac address is the
Value attribute of this XML tag.

Figure 31

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 59 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

(6) Locate the dongle serial number in the license file. Do this by searching for the
string ‘Dongle’ (in the XML section ‘FingerprintFile’). The dongle serial number is
the Serial number attribute of this XML tag.
(7) Locate the installed software version in the license file. Do this by searching for
the string InstalledSwComponent. The version number consists of three
numbers: X, Y and Z-version
(8) Now the information has to match:
• The Mac address of the machine to the Mac address' in the license file.
• The dongle serial number to the dongle serial number in the license file.
• The installed software version to the installed software version in the
license file.

NOTE:
If a license file is loaded and the system goes into grace as a result of the loading,
the user is warned and can cancel the operation via the following warning dialog:

Figure 32

3.9 Forced Delete

In some situations sessions cannot be deleted using the Delete Examination function in
the Main Menu (cleanup date/time issues, exam cannot get into the 'closed'
status, etc).
Any Examination (open or closed) can be deleted by a Service user via the
Configuration Tool:

NOTE:
Make sure there are no jobs in the output queues for the session to be deleted.
These jobs will become faulty after the sessions is deleted.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 60 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

(1) Log in using the “crservice” account.

(2) Stop the NX Software.
(3) Start the Configuration Tool.
(4) Go to "Security and License Management".
(5) Click <Delete Examinations>.
(6) Click <Get Examinations>.

Figure 33
(7) Select an examination and click <Delete>.
(8) If the NX software is running, a confirmation is requested to stop the
NX software.
(9) The examination is deleted.
(10) Restart the system.

3.10 Configuring the Auto Log Off / Screen Saver

3.10.1 Lock the Screen by Password Protection of the current User

(default Configuration after Installation)

Repeat these steps for each configured user:

(1) Right-click anywhere on the desktop and select Properties.
(2) Select the tab Screen Saver.
(3) Select Bezier in the drop-down with the selection of the screen saver (or any
other screensaver).

NOTE:
Do not select Logoff Screen Saver!

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 61 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

(4) Set Wait time: Determines the time of non-activity before the screen saver
is activated.
(5) Set On resume, password protect: The user needs to enter his password to
unlock the screen saver.
(6) Click <OK>.

3.10.2 Configuring the Screensaver to log out the current User

Repeat these steps for each configured user:

(1) Right-click anywhere on the desktop and select Properties.
(2) Select the tab Screen Saver.
(3) Select Logoff Screen Saver in the drop-down with the selection of the
screen saver.
(4) Set Wait time: Determines the time of non-activity before the screen saver is
activated.

Execute these steps once:

(1) Log in using an account that has administrator rights.
(2) Right-click anywhere on the desktop and select Properties.
(3) Select the tab Screen Saver.
(4) Make sure that Logoff Screen Saver is selected in the drop-down and click
<Settings>.
(5) Make sure that the checkbox Force application termination is not checked!
(6) Set Countdown for ... seconds: The number of seconds a dialogue is displayed
before the AutoLogOff actually takes place (i.e. after a period of inactivity this
dialogue pops up and the user still has this number of seconds to prevent being
logged off).
(7) Set Logoff message: The message that is to be displayed within this
dialogue box.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 62 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

3.11 Enabling the Service Mode for Digitizers

The service mode allows the service engineer to preserve the data as it was acquired
from the digitizer (without any processing). This can be enabled and disabled per
digitizer.
This is a feature that can be used when there is doubt that the digitizer is sending the
correct information to the NX workstation (can be added as an attachment in the
problem tracking system for example).
When enabled, a DICOM file is generated in the folder:
• D:\Agfa\Healthcare\NX\DataFiles\DicomFiles in case it is a DICOM digitizer.
• An xml file with the demographic data and the raw pixel data are stored in the folder
D:\Agfa\Healthcare\NX\DataFiles\TwainProcessedFiles for Twain digitizers (e.g.
DX-S). In a DICOM file, both are available in one file. The names of the files match
the SOP instance UID (unique identifier) of the image in NX.
To enable or disable the service mode, use the following procedure:
(1) Go to:
Start  Agfa  NX  Service  Install tools  Set digitizer service mode
(2) All configured digitizers are listed.
(3) Select the digitizer for which the service mode needs to be changed.
Press 0 for cancelling this task.
Result The changes will be picked up when the NX backend service is restarted.

NOTE:
When the service mode is enabled for a digitizer, all pixel data will be stored twice on
the data harddisk. The service engineer is responsible to clean up the data when ready
with it. This cleanup happens automatically when disabling the service mode.

3.12 Enabling the Service Mode for Archiving

The service mode allows the service engineer to preserve the data as it was sent from
the NX Workstation to the Dicom archive. This can be enabled and disabled per
archive.
This is a feature that can be used when there is doubt that the NX is sending the
correct information to the Dicom archive (can be added as an attachment in the
problem tracking system for example). These Dicom objects can also be viewed using
any DICOM Viewer for further analysis or to compare them with what is visible on the
PACS.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 63 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

When enabled, one or two (in case that the GSPS option was enabled for the archive)
DICOM file are generated in the ArchiveEnhancedServiceModeStorage folder per
archive job. The names of the files match the SOP instance UID (unique identifier) of
the image in NX. To enable or disable the service mode, use the following procedure:
(1) Go to:
Start  Agfa  NX  Service  Install tools  Set archiving service mode.
(2) All configured archives are listed.
(3) Select the archive for which the service mode has to be changed. Press 0 for
cancelling this task.
Result The changes will be picked up when the NX backend service is restarted.

NOTE:
When the service mode is enabled for an archive, all pixel data will be stored twice on
the data harddisk. The service engineer is responsible to clean up the data when
he/she is ready with it. This cleanup happens automatically when disabling the
service mode.

3.13 Saving the Adjustments of Musica 1 Settings (via NX GUI) to the Backup
File

In the NX application (GUI), the Musica 1 settings can be adjusted and saved as
default. If these settings should be included into the backup configuration file, so that
they will not have to be repeated after a restore, follow these instructions:

(1) Close the Configuration Tool (if it is still running).

(2) Go to the NX application.
(3) Open a representative image of the regarded exposure type.
(4) Let the customer/key user edit the Musica1 settings.
(5) Click Set as default.
(6) Repeat steps 3 - 5 for as many exposure types as required.
(7) Stop NX.
(8) Open the Configuration Tool.
(9) Load the Active Configuration.
(10) Export the backup configuration file (xml), store it on a safe place (like a CD) and
name it with a time stamp.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 64 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

3.14 Recovering from Disk Failure on a RAID System

On NX systems with RAID functionality, the system remains operational if one of both
disks fails. The user receives a warning that the RAID volume is degraded and should
inform Service to replace the failing disk. After replacing the disk, the RAID must be
activated again.
(1) Change the BOOT ORDER after replacing the disk:
• On a DELL PC:
During booting press <F12> to enter the BIOS setup.
Select the RAID Volume (e.g. Intel Volume_000) as primary boot media.
• Or on an HP PC:
Press <F10> during booting to enter the BIOS setup.
Go to Storage and select Boot Order.
Set the RAID Volume (e.g. Intel Volume_000) as primary boot media.
Press <F10> to accept changes.
Select Save Changes and Exit and press <F10> to accept.

(2) Observe a message of degraded RAID is shown when the PC is booting.

Figure 34

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 65 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

(3) Wait until Windows is booted and log in using the “crservice” account.
For all PCs with RAID, except HP 8300 and HP rp5800:
Intel Matrix storage manager is informing about the fact that the RAID is
degraded an may be rebuild.

Figure 35

For HP 8300 and HP rp5800:

• Rebuilding starts automatically when the primary boot media is set correctly
in the BIOS.
• Wait until following message is displayed: Data on one or more
volumes is protected from a disk failure. The following steps
(4) to (7) are not required and can be skipped.

Figure 36

(4) Go to Start  All Programs > Intel Matrix Storage Manager  Intel Matrix
Storage Console to launch the Intel Storage Console.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 66 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

(5) Select Restore RAID 1 data protection and click

<Rebuild RAID volume now>:

Figure 37

(6) Click <Yes> to start migrating.

Figure 38

(7) The progress of migration is displayed:

Figure 39

IMPORTANT:
Do not perform a reboot of the system until the migration process has
finished completely.

NOTE:
The computer can be used normally during the migration process.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 67 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

3.15 Recovering from a corrupted Database after Power Failure

If there are symptoms for a corrupted database (See also section 1.7.1) proceed as
follows to recover from this error:

IMPORTANT:
This procedure can only be used at software NX 2.0.8700 / 3.0.8700 (and higher
versions if available).
For software versions < NX 2.0.8700 / 3.0.8700:
• Omit steps (2), (4) and (6): These functions are only available for
software ≥ NX 2.0.8700 / 3.0.8700.
• Step (5) is relevant only, if a Windows scheduled tasks exists to backup all data.

(1) A power failure may have caused corruption of the hard disk. Use the Windows
tooling (Windows7: http://www.w7forums.com/use-chkdsk-check-disk-t448.html ,
Windows XP: http://support.microsoft.com/kb/156571) to repair the disk.

(2) If the symptom for database corruption is the occurrence of error messages in
the NXWorkStation log file reporting database login failures of the user adcqs:
Repair the database by using the shortcut “ReSynchronize NX Configuration”.

Check startup of the NX: If it starts up normally, the database is recovered.

(3) Restore the configuration:

• Start the NX configuration tool.
• If it is not possible to start the NX Configuration Tool due to the database
being corrupt, then first use the shortcut “Reset NX Configuration Data to
Factory Settings”.
• Restore a previous configuration (by start up dialogue function "Restore NX
configuration" or by function "load a configuration from an external file").

Note, that in software versions < NX 2.0.8700 / 3.0.8700 using the function
"Restore NX configuration" always restores the configuration backup which was
made previously compared to the actual selection.

Check startup of the NX: If it starts up normally, the database is recovered.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 68 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

(4) Use the “Agfa > NX > Service > Backup Restore > Database Repair Utility”
shortcut. This utility provides some basic repair functions at SQL level:
• Check the database consistency
• Repair the database consistency without data loss
• Repair the database consistency allowing data loss

Check startup of the NX: If it starts up normally, the database is recovered.

(5) Use the “Agfa > NX > Service > Backup Restore > Restore All Data” shortcut.
Note, that all changes since the latest backup will be lost.
As for NX 2.0.8700 / 3.0.8700 a backup in hourly rate is automatically created,
the maximum of data loss will be the data added the last hour.

Check startup of the NX: If it starts up normally, the database is recovered.

(6) Use the “Agfa > NX > Service > Backup Restore > Recreate Database and
Restore All Data” shortcut to recreate the database and restore its content using
the latest backup.
Note, that all changes since the latest backup will be lost.
As for NX 2.0.8700 / 3.0.8700 a backup in hourly rate is automatically created,
the maximum of data loss will be the data added the last hour.

Check startup of the NX: If it starts up normally, the database is recovered.

(7) Use the “Agfa > NX > Service > Install Tools > Reset NX Completely to Factory
Settings” shortcut to re-initialize the database.
Using this script results in a loss of all configuration, image and dose data.

After this, restore the configuration.

3.16 Handling Issues occurring during automated Data Import/Export

The feature automated data import/export allows automatically maintaining the

following data when performing an upgrade from NX version 2.0.8000 / 3.0.8000
(except NX 2.0.8100 / 3.0.8100) or higher:

• Configuration Data
• Image Data
• Dose Statistic Data

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 69 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

3.16.1 Best Practices

Be aware of the following best practices using the automated data import/export:

IMPORTANT:
Do not interrupt the upgrade installation.
If the amount of image data that needs to be preserved is very limited compared to the
total set on the system, it is not advised to use the automated export/import. Use the
manual export/import procedures instead.
The procedures are described in the NX 3.0.9000 Service Manual, chapter 05 Clean
Installation.
• Make sure all sessions are closed prior to starting the upgrade.
• Make sure there are no pending jobs prior to starting the upgrade.

3.16.2 One of the Exports fails

If one of the exports fails a dialogue is shown reporting the outcome of each of the
exports and offering the possibility to cancel the upgrade process. In this case:

(1) Cancel the upgrade procedure.

(2) Use the manual export/import procedures as described in
NX 3.0.9000 Service Manual, chapter 05 Clean Installation.

3.16.3 Import of the Configuration Data fails due to Verification Errors in the Data

If one the import of the configuration data fails due to verification errors in the data:

(1) Load the exported configuration file in the NX Configuration Tool.

(2) Repair the verification errors.
(3) Activate the configuration.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 70 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Useful Service Activities

3.16.4 Interrupted Import

If after the upgrade one or more imports of image data have been interrupted, e.g.
because the system was switched off during import:

(1) Manually move (not copy and paste) the existing preprocessed pixel files
from the folder:
D:\Agfa\Healthcare\NX\DataFiles\PreprocessedPixelFiles
To the folder:
D:\Agfa\Healthcare\NX\DataFiles\UpgradeData\PreprocessedPixelFiles

(2) Run the NX Activation Utility to reset the system to factory defaults:
Start  Agfa  NX  Service  Install Tools  NX  NX Activation Utility
(3) Browse to the folder: C:\Agfa\Healthcare\NX\Bin
(4) Double click the file:
NX.Application.Visual.CommonTools.ImportAfterUpgrade.exe
An application opens.
(5) Use this application to restart the import of the data.

3.16.5 Images show red Crosses after Upgrade

If after the upgrade, the images appear as red crosses in the NX Viewer (and reporting
about missing pixel files), it can be that the associated pixel files have not been moved
back to their original folder.
To repair this situation, use the Windows Explorer to manually move the pixel files from
the folder:
D:\Agfa\Healthcare\NX\DataFiles\UpgradeData\PreprocessedPixelFiles
To the folder:
D:\Agfa\Healthcare\NX\DataFiles\PreprocessedPixelFiles

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 71 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

4 Fault Finding

Overview: See section:

1. NX System Snapshot 4.1

2. System snapshot tool for the user (CTRL-ALT-I) 4.2

3. Attention Keys 4.3

4. View Logging 4.4

5. Log Viewer Configuration 4.5

6. Logging Namespaces 4.6

7. Configure Logging 4.7

8. Exporting and Importing Images 4.8

9. DICOM Validation 4.9

10. Operational Statistics 4.10

11. Finding Configuration Information on the ELMS 4.11

12. Database Icon 4.12

13. NX Health Icon 4.13

14. Check installed Certificates 4.14

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 72 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

4.1 NX System Snapshot

The NX System Snapshot

• Is a collection of all relevant files for troubleshooting of the system.
• Is intended to be attached to each problem record when escalating a problem with
the NX or the CR / DR system.

(1) Select START > All programs > Agfa > NX > Service > NX System
Snapshot
(2) Recommendation: Leave everything on default. For details to the different
settings refer to table next page.
Click <Make Snapshot>
(3) Wait until the snapshot is created. This takes a few minutes.
(4) Copy the snapshot from C:\Agfa\HealthCare\NX\SystemSnapshot to a
USB flash drive and forward it to the next support level.

NOTE:
If the NX System Snapshot is too large for sending via email, create a temporary FTP
account for file transfer. Refer to following document on the Agfa HealthCare Library:
How to get a temporary AGFA FTP account for uploading files,
Document ID 34721327.

NOTE:
The NX System Snapshot GUI shown in Figure 42 was introduced together with
software version NX 2.0.8900 / 3.0.8900. For more information to the NX System
Snapshot see also the Application Note - Functional Changes in NX 2.0.8900 -
3.0.8900, Document ID 47340162.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 73 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

Figure 40

Details to the NX System Snapshot Settings

1 Deselect the options in the “snapshot actions” pane only, if instructed by the
support center.

2 Three types of files compression are available: Uncompressed (“Zip the

various snapshot files” deselected), normal and ultra. Recommendation: Leave
it on default = normal compression.

3 To create the snapshot select the <Make Snapshot> button. Creating a

snaphot including zipping takes several minutes and depends on the amount
of logfiles and the NX hardware.

4 If it is clear, that the fault appeared in a certain time frame, it is possible to

select a time frame for included logfiles. As the root cause of a problem may
happen hours or days before the actual problem, it is recommended to leave
the time frame on default. This way all available log files are included.

5 By selecting button <Preview copy of Agfa/HealthCare/logfiles>

the file names and locations of the log files are shown. At the end the amount
of the (unzipped) data is shown in MB.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 74 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

4.2 System snapshot tool for the user (CTRL-ALT-I)

The system snapshot tool for the user (CTRL-ALT-I) facilitate the user to export native
images and a limited system snapshot at the time of an incident.
This can be picked up later by the FSE.

At any time with started NX, the user can

press the key combination CTRL + ALT + I
to start a wizard. This wizard performs
following main steps:
• Stops NX
• Starts the NX image export tool (if the
user selects to include images).
• Starts the snapshot tool.
• Saves images and snapshot in
directory
C:\Agfa\HealthCare\NX\InformationS
napshot\<Date_Time>\
• Starts NX.
The complete wizard takes a maximum of
5 minutes.

Figure 41

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 75 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

4.3 Attention Keys

“Attention keys” are introduced with NX

2.0.8800 / 3.0.8800, to facilitate the
analysis of field issues in case an issue can
be reproduced in the field but not by R&D.
Example: A certain error appears in the
field during operation. Press “CTRL-ALT-
SHIFT-A” to add following line to the NX log
file: Warning #ATTENTION: User has
pressed attention key
combination CTRL-ALT-SHIFT-A”.
If the same or a different error appears
some times later, press e.g. “CTRL-ALT-
SHIFT-B” to indicate the 2nd error.

Figure 42

When passing the NX logfiles to the RSN or GSN, inform about which attention key you
pressed with which event. Following attention keys are possible:
• Return key
• Figures 0 to 9. Do not use the numerical keypad to enter digits. Entering digits are
logged with a “D” in front of the digit. Example: CTRL-ALT-SHIFT-1 results in entry
“Warning #ATTENTION: User has pressed attention key
combination CTRL-ALT-SHIFT-D1”
• Characters A to Z
• F1 to F12 key

4.4 View Logging

CAUTION:
Violation of patient privacy possible!
Since the patient privacy information is human readable, it must be treated as
confidential information and protected from unauthorized access.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 76 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

IMPORTANT:
Do not alter the security settings of the logfiles, since the application needs to be able
to write to them.
For using the AGFA Healthcare Log Viewer read the CX.Logging.Viewer manual.
Access the AGFA Healthcare log viewer’s documentation by selecting Help  User
manual in the Log viewer’s menu.
Logging is available on a per-process basis. For NX, logging is available for the
following processes:
• NX Workstation Windows service (NX backend, where most of the business logic is
running): NX.Application.NonVisual.NXWorkstation.exe.log
• Configuration Tool: NX.Application.Visual.Configuration.ConfigTool.exe.log
• QC/ID Viewer (NX viewer): NX.Application.Visual.QCID.exe.log

(1) Start up the logging viewer by clicking on Logging viewer item in the start
menu: Start  Agfa  NX  Service  Logging
(2) Select File  new  log4net reader. Browse to the location where the log
files are located (C:\agfa\healthcare\log\NX\xml).
(3) Select a file (see list of files above).

4.5 Log Viewer Configuration

The logging components always log timestamps in GMT (Greenwich Mean Time)
format. Upon displaying log entries, the logging viewer will use the time zone of the PC.
This is not a problem in case the log file was created on a PC which is configured in the
same time zone.
When viewing a log file of another time zone the local time of the log entries might be
interesting. E.g. a log file entry created in the UK at 9 AM would be displayed on a
system located in Paris (GMT+1 time zone) as 10 AM.
To override this behavior follow this procedure:

(1) Go to: Menu  Edit  PReference  PReference

(2) In the ‘Display log entries in specific time zone’ option, select the time zone that
matches the location of the originator of the log file.
(3) Verify that the log entries will all be shown in the local time zone of the originator.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 77 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

4.6 Logging Namespaces

In order to understand the logging information, the meaning of the namespaces need to
be known. The table below lists some of the most important namespaces.

Namespace Description
General
Agfa.Healthcare.NX.Business.CompositeInsta Fast Preview communication (high level,
nce.FastPreview.Facade abstracting from the protocol used =>
Common to Compact –family digitizers and
Stratus-family digitizers (e.g. DX-S).
com.agfa.med.DICOM.facility.DTFLogger When set to DEBUG, a very detailed
DICOM log is being produced, both for
MPPS, Dicom RIS communication and
archiving.
Agfa.Healthcare.NX.Data All database related actions and actions
pertaining structured data transfer.
Agfa.Healthcare.NX.Business.ImageAcquisitio Core of the system, including state
n.SessionManagement.QCIDSessionFacade management.
Specific to printing
Agfa.Healthcare.NX.Business.Printing Printing
Specific to Compact – family digitizers
Agfa.Healthcare.NX.Business.CompositeInsta Image acquisition for Compact-family
nce.Dicom.DicomStorageSCPGateway digitizers
Agfa.Healthcare.NX.Business.CompositeInsta Fast ID communication with DICOM
nce.DirectIDGateway digitizers (Compact family)
Agfa.Healthcare.NX.Business.CompositeInsta Fast preview communication for DICOM
nce.Dicom.DicomFastPreviewSCPGateway digitizers (Compact family) – low level
Specific to Stratus – family digitizers
Agfa.Healthcare.NX.Business.CompositeInsta Image acquisition using a DX-S, including
nce.Twain.Gateway low-level fast preview communication.
Specific to ID Tablet
Agfa.Healthcare.NX.Business.CompositeInsta ID Tablet communication
nce.IDTabletGateway
Specific to archiving
Agfa.Healthcare.NX.Business.CompositeInsta DICOM communication for archiving
nce.Dicom.DicomStorageSCUGateway
Agfa.Healthcare.NX.Business.Archiving High-level archiving communication

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 78 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

4.7 Configure Logging

The Cx Logging component is delivered with logging configuration functionality.

Through this interface the service engineer is able to adapt the settings for logging.
At installation time the following defaults apply:
• Information of severity levels warning, info, error and fatal are logged.
• Information of severity level debug is not logged.
Note that this includes the ‘Extended service logging’.
• The logging information is stored in files of 20 MB (with a maximum of 5 files) using
a roll-over mechanism. Roll-over mechanism means that when the maximum size
limit is reached, the oldest messages will be overwritten. A log file only contains the
data that was configured to be logged (in other words: What comes into the log file
is dependent on the logging configuration file).

Every process has a logging configuration file

(e.g. NX.Application.NonVisual.NXWorkstation.exe.Logging.config), located in the
C:\agfa\healthcare\NX\bin folder. For the list of processes, see the list in the previous
section.
In order to make things easy, different logging configuration files are foreseen.
Switch between configurations using one of the shortcuts in the Start Menu:
Agfa  NX  Service  Logging  program group
Examples are:
• Activate Standard logging
• Activate ID tablet logging
• Activate Archive logging

NOTE:
Apart from ‘Activate Standard logging’, all logging batch files that are available will
activate DEBUG-level logging for certain components.

IMPORTANT:
When debug logging is enabled, this can have a serious impact on the performance of
the NX application.
It is the intention that it is only used for a limited amount of time during the fault finding
process. When finished with troubleshooting switch back to the standard log
configuration.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 79 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

4.8 Exporting and Importing Images

Images can be exported and imported on another (local) NX workstation for further
problem analysis.

NOTE:
Not all information related to the image is exported. Some data on session-level will be
missing and rejected images will be visible as normal images after export and import.

This is the procedure to export images:

(1) Close the session the images will be exported from.
(2) Click Export images in the Main Menu overview list.
The Export image Workspace area appears.
(3) Select a session and the images to export.
(4) Select the file format NATIVE and choose to include or not include the patients
demographics by checking or unchecking the checkbox Include Patient
Demographics.
CAUTION:
Violation of patient privacy possible!
The patients demographics contain patient privacy information.
They must be treated as confidential information and protected from
unauthorized access.

(5) Click <Export>.

(6) Select destination folder and click <OK>.
(7) The files can now be found in the destination folder.

To import the images on an NX Workstation (from a CD):

(1) Click Import images in the Main Menu overview list
A Windows Import-dialog box appears.
(2) Select the CD-drive and click <OK>.
(3) The images are imported in the NX system.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 80 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

4.9 DICOM Validation

In order to validate and test DICOM interfaces the DICOM Validation Tool (DVT) will be
used. This tool provides extensive logging information. DVT is programmed using a
simple scripting language and can be instructed to play either SCU or SCP.
Besides it can be used as a Storage SCP emulator, Print SCP emulator or to validate
Media Stored Files.

4.10 Operational Statistics

The service engineer can consult the operational statistics or infocounters. A total and
a relative counter have to be kept which is incremented each time the specified event
occurs.

4.10.1 Viewing operational Statistics

(1) Start up the Infocounter viewer:

Start  Agfa  NX  Service  Infocounter viewer
(2) Browse through the Infocounter viewer to see the current value of a certain
counter.

Figure 43

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 81 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

4.10.2 Resetting a relative Counter

The relative counter value can be reset to zero by the service engineer, normally after
a service intervention. The absolute counter value cannot be reset.
(1) To reset a counter, select the counter and right-click to select the Reset counter
option from the context menu. Enter the user name and the reason for the
intervention.

Figure 44

(2) Click <Reset>.

(3) Alternatively, it is possible to reset all counters in one go by clicking Tools in the
menu bar and choose Reset all.

Figure 45

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 82 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

4.11 Finding Configuration Information on the ELMS

The ELMS contains system configuration information on hardware, licenses, software

versions and hospital contact Reference.
(1) Log in to the ELMS.
(2) Find the configuration.

The ELMS also allows downloading the most recently generated license key file or
fingerprint file of each system that can be viewed using the License Manager Tool.

(1) Log in to the ELMS.

(2) Find the configuration.
(3) Download the files.
(4) Start up the license manager tool: Start  Agfa  Service  License manager
(5) Load the files in the viewer.

4.12 Database Icon

The database icon in the task bar indicates the state of the SQL Server database
service. Green indicates that it is properly working.
Note that when logged in as a normal user, the database icon in the taskbar may be
white. This does not mean the database is not running.

4.13 NX Health Icon

The NX health monitor icon in the task bar indicates the health of the NX backend
application.

Green means that the NX backend application is up and running and properly
initialized.
When it stays red, starting the NX Viewer will end up with an error. In order to find out
the details of the error state look at the log files.

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 83 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

4.14 Check installed Certificates

The following procedure allows checking the presence and content of the installed
certificates. Note that this is only relevant in case SSL has been configured.

(1) Log in with a Windows account with administrator privileges (If possible, with the
same account that used to install the certificates, e.g. CRService).
(2) Start the certificate management tool:
Start Agfa  NX  Service  Install Tools  Manage Cerificates
(3) Open up the ‘Personal’ and ‘Trusted Root Authorities’ folders in the Certificate
management tool and check the presence of the required certificates.
(4) Double-click on the certificate to check the content of a certificate
(e.g. expiration date).

Figure 46

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 84 of 85

12-2016 Type 4406/303 Agfa Company Confidential
 Troubleshooting
Fault Finding

(5) Double-click on the certificate in the ‘Personal’ folder, select the ‘Details’ tab and
select the ‘Subject’ item to check the common name of the NX certificate (which
needs to be configured in the NX Configuration tool as well).
The text next to ‘CN = ‘ is the common name of the certificate and needs to match
the common name in the NX Configuration tool / Security section.

Figure 47

DOCUMENT CONTROL NOTE:

The controlled version of this document is available from the Agfa HealthCare Library. Any printed copy of this document is uncontrolled.

Edition 1, Revision 0 NX 3.0.9000 Chapter 9 / Page 85 of 85

12-2016 Type 4406/303 Agfa Company Confidential