Additional Messages Print
Modified on: Tue, 11 May, 2021 at 2:22 AM
Disclaimer: The information herein is not intended to replace the product’s User Manual. Please consult the User Manual for comprehensive information and cautionary guidance about the product’s operation and use.
| User message | Remarks |
| User Rejection | The proposed presentation context is rejected by the Service Class Provider (SCP) (DICOM End Point). Contact Hospital IT team. |
| No Reason | Initiated DICOM transaction from Vscan Extend is rejected by the SCP. Contact Hospital IT team for more details. Device logs may help find the reason. |
| Abstract syntax not supported. | SCP does not support the DICOM Service (Abstract Syntax) initiated by the device. Contact Hospital IT team. |
| Transfer syntax not supported. | SCP does not support the DICOM Service (Transfer Syntax) initiated by the device. Contact Hospital IT team. |
| No type negotiated. | Contact GE Service for more details. |
| DUL Association Rejected: No Reason (Service User) | DICOM End Point rejects the association without giving any reason. |
| DUL Association Rejected: App Context Name Not Supported | Contact Hospital IT team. |
| DUL Association Rejected: No Reason (Service Provider) | |
| DUL Association Rejected: Calling AE Title Not Recognized | Calling AE Title mismatch. Contact Hospital IT team. |
| DUL Association Rejected: Protocol Version Not Supported | Association rejected because of protocol version mismatch. |
| Contact Hospital IT team. | |
| DUL Association Rejected: Temporary Congestion | Failure due to network congestion. Contact Hospital IT team. |
| DUL Association Rejected: Local Limit Exceeded | Number of clients accessing the DICOM SCP exceeded. |
| Contact Hospital IT team. | |
| Refused: Duplicate Invocation | Indicates that the Message ID (0000,0110) specified is allocated to another notification or operation. |
| DICOM transaction need to be repeated. Contact GE Service. | |
| Refused: Mistyped argument | Indicates one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users. |
| Contact GE Service. | |
| Refused: SOP Class Not Supported | SOP Class mismatch. Contact GE Service. |
| Refused: Unrecognized Operation | Contact GE Service. |
| Association request failed (or never connected). | Request to connect to DICOM Server failed. Contact Hospital IT team. |
| Network timeout error | Check network connection. Contact Hospital IT team. |
| Peer aborted association | Repeat the DICOM transaction. If it consistently fails, contact GE Service. |
| No network connection | Check network connection. Contact Hospital IT team. |
| Refused - Server out of resources | The DICOM endpoint server is out of resources to accept exported DICOM file. |
| Contact Hospital IT team. | |
| Identifier does not match SOP class | DICOM file's data set does not match with the SOP Class. |
| Contact GE Service. | |
| Failure - Processing failure | Interoperability issue. Contact GE Service. |
| Failure - Invalid object instance | Contact GE Service. |
| Internal application error | Contact GE Service. |
DICOM messages
Did you find it helpful? Yes No
Send feedbackSorry we couldn't be helpful. Help us improve this article with your feedback.