Error codes

ERR001

This error code is displayed when Edison™ Datalogue™ Connect fails to retrieve case that was queued for download.

Both the site administrator and the patient/physician (logged in user) receive a message with the error code, case ID and instructions on how to resolve the issue.

To troubleshoot the ERR001 caused by unavailability of study in VNA, please follow the steps listed below:

If the issue is not resolved then please contact the GE Service team.

To troubleshoot the ERR001 caused by connectivity issue (EA with application), please follow the steps listed below:

1. Click and select Org Management.

2. Click to expand the row for the site.
   Note: The Site name is mentioned in an email you receive for ERR001.
3. Click Device Management.
4. Select the device and click .

5. Click the Test C-Echo button to test the connectivity.

   If C-Echo connection is successful then issue should be resolved. If the issue persists then please contact GE Service team.

   Note: If the connection is unsuccessful, then please contact the GE Service team.

ERR002

This error code is displayed when Edison™ Datalogue™ Connect fails to package (zip) case that was queued for download.

Both the site administrator and the patient/physician (logged in user) receive a message with the error code, case ID and instructions on how to resolve the issue.

Technical issue with the zipping software

To troubleshoot the ERR002, please follow the steps listed below:

ERR003

This error is displayed when searching patient from Edge device fails during case creation.

The site administrator receives a notification email about the queried data retrieval failure with the error code.

Edge Services are down or connectivity to Edge machine is unavailable.

To troubleshoot the error, please follow the steps listed below:

1. Contact the GE Service team to resolve the issue.

ERR004

This error is displayed when an Edge device fails to create a case from DICOM device or fails to send a case to DICOM device.

The site administrator receives an email about the failure with the error code and instructions on how to resolve the issue.

Edge Device is down or disconnected from the network.

To troubleshoot the error, please follow the steps listed below:

1. Restart Predix Core (Refer to Restarting Predix Core section from the Edge Device Service Configuration Guide)

If you are unable to restart the Predix Core, then please contact your GE Edison™ Datalogue™ Connect support team and log a support incident for this issue.

ERR005

This error is displayed when there is a checksum mismatch.

The site administrator or the affected user receives an email about the failure with the error code and instructions on how to resolve the issue.

This error occurs when the file transferred is corrupt.

Re-initiate the performed operation.

ERR006

This error is displayed when the sftp server is down. It is displayed to the Site Admin, Sender and to the GE service configured email ID.

The site administrator or the affected user receives an email about the failure with the error code and instructions on how to resolve the issue.

This error occurs when the sftp service responsible for file transfer which is running on Edge device is down.

Start the sftp service on Edge using the command:

service edge-sftp start

ERR007

This error is displayed when Edison™ Datalogue™ Connect is unable to retrieve the failure details.

The site administrator or the affected user receives an email about the failure with the error code and instructions on how to resolve the issue.

This error occurs when the file was transferred partially or it failed completely.

Ensure if the network between the Edge device and the cloud server is available and then re-initiate the performed operation.

-44444

This error code is displayed when a timeout is occurred while performing patient search or while searching patient studies.

When you perform a patient search from the DICOM, while creating a case from DICOM devices, you may be displayed with this error when timeout happens while retrieving patient details

When you perform a study search for the patient from the DICOM, while creating a case from DICOM devices, you may be displayed with this error when timeout happens while retrieving patient studies.

To troubleshoot the error, please follow the steps listed below:

• Check the Network connectivity by performing ping or telnet. If there is a network connectivity issue, then please contact your GE Edison™ Datalogue™ Connect support team and log a support incident for this issue

• Check the PACS service status. If it stopped, then restart it. If you are unable to restart the PACS, then please contact your GE Edison™ Datalogue™ Connect support team and log a support incident for this issue.
• Check the Predix Core status, if it is stopped, then restart it. If you are unable to restart the Predix Core, then please contact your GE Edison™ Datalogue™ Connect support team and log a support incident for this issue.

-99999

This error code is displayed when there is any PACS connectivity issue or any runtime exception occurs while patient search.

When you perform a patient search while creating a case from DICOM devices, you may be displayed with this error due to PACS connectivity issue or any runtime exception occurs.

• PACS connectivity issue.
• Runtime Exception

To troubleshoot the error, please follow the steps listed below:

• Check the Network connectivity by performing ping or telnet. If there is a network connectivity issue, then please contact your GE Edison™ Datalogue™ Connect

• Check the Predix Core status, if it is stopped, then restart it. If you are unable to restart the Predix Core, then please contact your GE Edison™ Datalogue™ Connect support team and log a support incident for this issue.

-77777

This error code is displayed when there is any PACS connectivity issue or any runtime exception occurs while patient search.

When you perform a patient search, while creating a case from DICOM devices, you may be displayed with this error due to PACS connectivity issue or any runtime exception occurs.

• PACS connectivity issue.
• Runtime Exception

To troubleshoot the error, please follow the steps listed below:

• Check the Network connectivity by performing ping or telnet. If there is a network connectivity issue, then please contact your GE Edison™ Datalogue™ Connect

• Check the Predix Core status, if it is stopped, then restart it. If you are unable to restart the Predix Core, then please contact your GE Edison™ Datalogue™ Connect support team and log a support incident for this issue.

ERR008

This error is received in email when the DICOM copy from Spring SFTP component to local file system fails.

The GE Administrator receives an email about the failure with the error code and instructions on how to resolve the issue.

Although there can be any reason for this failure, one possible cause can be that Predix core service is running under dsp-k-user. So it is unable to delete the zip file downloaded by the Spring SFTP component.

Check whether Predix core is running on the Edge device under the root user.

ERR009

This is a generic error code displayed in email to the user who performed the action, for all Case Exchange related errors.

If the upload of attachments fail during case creation, there is no error message that is displayed on the UI. The attachment is displayed in red in the case summary section and Upload Failed label is displayed.

If the download of attachments to local machine fails, a notification is sent to the user in the Notifications section with status 'Failed'.

• Edge service is down
• CloudEA service is down
• Error in checksum
• SFTP service is down

• Check the status of Edge service.
• Check the status of CloudEA service.
• Check for the back-end code on Edge.
• Check for the status of on SFTP.

ERR009

This is a generic error code displayed in email to the user who performed the action, for all Case Exchange related errors.

If the download of DICOM attachment to PACS device fails, the message 'An error occurred. Please try again' is displayed

Predix service for that Edge is down.

Check the status of Predix service.

ERR010

SCP Storage Failure

This failure happens when system fails to store SOP class.

SOP class needs to be supported in EA and XJT.

• Check with the EA manual if SOP is supported or not.
• Check with XJT if SOP is supported or not.

ERR011

HL7 Failure Deletion

The failure happens when study is not available in Archive.

HL7 scheduler tries to process the HL7 message till configurable time present in the application properties.

Once the time has lapsed, the HL7 message deletes the failure messages from the database.

ERR012

HL7 Failure

This failure happens when study is not available in Archive.

Study not yet reached Archive

Wait for the study to reach Archive for processing of HL7 message

ERR013

Transfer of DICOM files from Cloud FS to CloudEA retry failed.

The site administrator receives an email about the failure with the error code and instructions on how to resolve the issue.

• CloudEA service is down
• Network is unreachable

• Check the status of CloudEA.
• Verify if the network is reachable or not.
• Check the memory storage for CloudEA service.

ERR014

Transfer of DICOM files from local file system to local Predix machine FS failed on Edge.

The site administrator receives an email about the failure with the error code and instructions on how to resolve the issue.

Edge EA/PACS service is down or communication error between EDGE & PACS.

Check the status of EDGE EA/PACS.