Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Faied to send MPPS Command #80

Open
yadavvirus opened this issue Mar 8, 2022 · 2 comments
Open

Faied to send MPPS Command #80

yadavvirus opened this issue Mar 8, 2022 · 2 comments

Comments

@yadavvirus
Copy link

yadavvirus commented Mar 8, 2022

While using Worklist SCP finding patient is success. But after fetcing info getting this error.
image

Error on Modality
image

Log in Modality is
Started logging into new stream
Logging into file: C:\Users\BPYADAV\Documents\MODALIZERPLUS\LOGS\LastMPPSCreate.log
2022-03-0813:57:07.196000 15868 INFO Association Request Parameteres:
Our Implementation Class UID: 2.16.124.113543.6021.1
Our Implementation Version Name: RZDCX_3_1_0_11
Their Implementation Class UID:
Their Implementation Version Name:
Application Context Name: 1.2.840.10008.3.1.1.1
Calling Application Name: ModalitySCU
Called Application Name: QRSCP
Responding Application Name: resp AP Title
Our Max PDU Receive Size: 32768
Their Max PDU Receive Size: 0
Presentation Contexts:
Context ID: 1 (Proposed)
Abstract Syntax: =VerificationSOPClass
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=LittleEndianExplicit
=BigEndianExplicit
=LittleEndianImplicit
Context ID: 3 (Proposed)
Abstract Syntax: =ModalityPerformedProcedureStepSOPClass
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=LittleEndianImplicit
Requested Extended Negotiation: none
Accepted Extended Negotiation: none

2022-03-0813:57:07.206000 15868 INFO Association Request Result: Normal
Association Response Parameteres:
Our Implementation Class UID: 2.16.124.113543.6021.1
Our Implementation Version Name: RZDCX_3_1_0_11
Their Implementation Class UID: 1.3.6.1.4.1.30071.8
Their Implementation Version Name: fo-dicom 5.0.2
Application Context Name: 1.2.840.10008.3.1.1.1
Calling Application Name: ModalitySCU
Called Application Name: QRSCP
Responding Application Name: QRSCP
Our Max PDU Receive Size: 32768
Their Max PDU Receive Size: 262144
Presentation Contexts:
Context ID: 1 (Accepted)
Abstract Syntax: =VerificationSOPClass
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Accepted Transfer Syntax: =LittleEndianExplicit
Context ID: 3 (Accepted)
Abstract Syntax: =ModalityPerformedProcedureStepSOPClass
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Accepted Transfer Syntax: =LittleEndianImplicit
Requested Extended Negotiation: none
Accepted Extended Negotiation: none

2022-03-0813:57:07.206000 15868 INFO DIMSE receiveCommand
2022-03-0813:57:17.207000 15868 ERROR In DCXREQ, Code: 519, Text: DIMSE No data available (timout in non-blocking mode)
Stopped Logging.

Please Help

@yadavvirus
Copy link
Author

Is there someone who can help me in above?

@gofal
Copy link
Contributor

gofal commented May 25, 2022

The code provided here are just samples. This is not production ready code!

The exception shows you exactly the stacktrace, so you can locate the error easily.

In WorklistService.OnNCreateRequestAsync the code accesses a Tag, that is not present:
var affectedSopInstanceUID = request.Command.GetSingleValue(DicomTag.AffectedSOPInstanceUID);
So you have to secure that method. E.g. first check if the Tag exists before accessing it. Debug, what kind of messages the modality sends so that you can answer correctly. Etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants