DICOM NoCompatibleTransferSyntaxFound
Good morning,
We would need help, thanks in advance for your help. 🙂
We have been trying to debug the following error, when sending a DICOM from a "EnsLib.DICOM.Operation.TCP" to a PACs:
| ERROR <EnsDICOM>NoCompatibleTransferSyntaxFound: No negotiated transfer syntax for SOP class '1.2.840.10008.5.1.4.1.1.4' is compatible with document transfer syntax '1.2.840.10008.1.2.4.70' |
.png)
We use the following AET titles at the Operation:
LocalAET: ESBSSCC-DCM
RemoteAET: HUNSCESBGWT
.png)
We have observed that we do have the transfer syntax "1.2.840.10008.5.1.4.1.1.4" with the document syntax "1.2.840.10008.1.2.4.70", configured in both associations:
ESBSSCC-DCM to HUNSCESBGWT:
.png)
.png)
And HUNSCESBGWT to ESBSSCC-DCM:
.png)
.png)
However, when the source provider sends the DICOM, or when we resent it from the Message Viewer, the error still happens:
| ERROR <EnsDICOM>NoCompatibleTransferSyntaxFound: No negotiated transfer syntax for SOP class '1.2.840.10008.5.1.4.1.1.4' is compatible with document transfer syntax '1.2.840.10008.1.2.4.70' |
How could we handle this issue?
Is there any way we could debug it further?
Thank you for your help. 🙂🙂🙂
In addition, we have read:
https://docs.intersystems.com/irisforhealthlatest/csp/documatic/%25CSP…
https://community.intersystems.com/post/sending-dicom-files-between-iri…
https://community.intersystems.com/post/receiving-dicom-messages-pacs-i…
Could you help us?
Thanks so much.
Comments
Hi @Yone Moreno ! Could you paste the metadata from your DICOM message, something like this:
.png)
Maybe you CommandField value isn't a C-STORE operation.
Hello @Luis Angel Pérez Ramos 🙂🙂🙂, yes it is the Command Set:
Command Set
| Tag | Name | Contents |
|---|---|---|
| (0000,0002) | AffectedSOPClassUID | 1.2.840.10008.5.1.4.1.1.4 |
| (0000,0100) | CommandField | 1 |
| (0000,1000) | AffectedSOPInstanceUID | 1.3.46.670589.11.34110.5.0.8212.2025052007473768693 |
It said:
| ERROR <EnsDICOM>NoCompatibleTransferSyntaxFound: No negotiated transfer syntax for SOP class '1.2.840.10008.5.1.4.1.1.4' is compatible with document transfer syntax '1.2.840.10008.1.2.4.70' |
...
...
But on date: "2025-06-05 12:32:05.765", we received a similar DICOM, with a more complete Command Set, and it also failed saying the same exception error (we configured the syntaxes before they sent this DICOM):
Command Set
| Tag | Name | Contents |
|---|---|---|
| (0000,0000) | CommandGroupLength | 124 |
| (0000,0002) | AffectedSOPClassUID | 1.2.840.10008.5.1.4.1.1.4 |
| (0000,0100) | CommandField | 1 |
| (0000,0110) | MessageID | 1 |
| (0000,0800) | CommandDataSetType | 65278 |
| (0000,1000) | AffectedSOPInstanceUID | 1.3.46.670589.11.34110.5.0.8212.2025052007473768693 |
It said:
| ERROR <EnsDICOM>NoCompatibleTransferSyntaxFound: No negotiated transfer syntax for SOP class '1.2.840.10008.5.1.4.1.1.4' is compatible with document transfer syntax '1.2.840.10008.1.2.4.70' |
...
Please, could you help us? Thank you so much. 🙂🙏🙂
Can I see the Association Context?
.png)
.png)
(1).png)
(1).png)
(1).png)
(1).png)
Please, does anybody have any ideas that could help us solve this issue?
Thank you so much!
I suppose DICOM is not the most used feature in HealthShare, right? ^^!!
Hello Yone
I have exactly the same error. Did you found a solution/workaround?
Thanksss
It's looks like when you are just setting :
It works
But when you try to set it genreally:
It fails:
Pretty sure it's something that I'm not getting conceptually from DICOM. But if someone, can explain it, it would be wonderful.
Sometimes IRIS doesn't work very well when there are too many abstract syntax defined for a DICOM configuration, I suggest to you to create a new DICOM configuration with a new name for IRIS and add the abstract syntax configuration that is failing.
Thanks Luis
You are totaly right .Reading this post, I understood that I had to filter Abstract Syntax, instead of setting it generaly.