0006:0208 DIMSE No valid Presentation Context ID

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
mentaanilkumar
Posts: 15
Joined: Thu, 2017-09-07, 09:34

0006:0208 DIMSE No valid Presentation Context ID

#1 Post by mentaanilkumar »

No Acceptable Presentation Contexts
0006:0208 DIMSE No valid Presentation Context ID

I am getting above errors for findscu and movescu using dcmtk but its working for storescu and echoscu.I am unable to find the solution.Please help.

Michael Onken
DCMTK Developer
Posts: 2048
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: 0006:0208 DIMSE No valid Presentation Context ID

#2 Post by Michael Onken »

Hi,

What kind of DICOM service do you like to use? Do you want to query a PACS? If so, try findscu with option -S to select one of the query SOP Classes

Best,
Michael

mentaanilkumar
Posts: 15
Joined: Thu, 2017-09-07, 09:34

Re: 0006:0208 DIMSE No valid Presentation Context ID

#3 Post by mentaanilkumar »

I am querying against PACS and I queried using findscu (-S).

Michael Onken
DCMTK Developer
Posts: 2048
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: 0006:0208 DIMSE No valid Presentation Context ID

#4 Post by Michael Onken »

Then add option -d and post the output.

Best,
Michael

mentaanilkumar
Posts: 15
Joined: Thu, 2017-09-07, 09:34

Re: 0006:0208 DIMSE No valid Presentation Context ID

#5 Post by mentaanilkumar »

D: $dcmtk: findscu v3.6.0 2011-01-06 $
D:
D: Request Parameters:
D: ====================== BEGIN A-ASSOCIATE-RQ =====================
D: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.0
D: Our Implementation Version Name: OFFIS_DCMTK_360
D: Their Implementation Class UID:
D: Their Implementation Version Name:
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: KPServer
D: Called Application Name: DicomListener
D: Responding Application Name: resp. AP Title
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 0
D: Presentation Contexts:
D: Context ID: 1 (Proposed)
D: Abstract Syntax: =FINDStudyRootQueryRetrieveInformationModel
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
D: =LittleEndianExplicit
D: =BigEndianExplicit
D: =LittleEndianImplicit
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-RQ ======================
I: Requesting Association
D: Constructing Associate RQ PDU
D: PDU Type: Associate Accept, PDU Length: 182 + 6 bytes PDU header
D: 02 00 00 00 00 b6 00 01 00 00 44 69 63 6f 6d 4c
D: 69 73 74 65 6e 65 72 20 20 20 4b 50 53 65 72 76
D: 65 72 20 20 20 20 20 20 20 20 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 10 00 00 15 31 2e
D: 32 2e 38 34 30 2e 31 30 30 30 38 2e 33 2e 31 2e
D: 31 2e 31 21 00 00 19 01 00 03 00 40 00 00 11 31
D: 2e 32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32
D: 50 00 00 38 51 00 00 04 00 00 40 00 52 00 00 21
D: 31 2e 32 2e 38 32 36 2e 30 2e 31 2e 33 36 38 30
D: 30 34 33 2e 32 2e 33 36 30 2e 30 2e 33 2e 35 2e
D: 34 55 00 00 07 49 49 53 5f 33 35 34
D: Parsing an A-ASSOCIATE PDU
D: Association Parameters Negotiated:
D: ====================== BEGIN A-ASSOCIATE-AC =====================
D: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.0
D: Our Implementation Version Name: OFFIS_DCMTK_360
D: Their Implementation Class UID: 1.2.826.0.1.3680043.2.360.0.3.5.4
D: Their Implementation Version Name: IIS_354
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: KPServer
D: Called Application Name: DicomListener
D: Responding Application Name: DicomListener
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 16384
D: Presentation Contexts:
D: Context ID: 1 (Abstract Syntax Not Supported)
D: Abstract Syntax: =FINDStudyRootQueryRetrieveInformationModel
D: Proposed SCP/SCU Role: Default
D: Accepted SCP/SCU Role: Default
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-AC ======================
E: No Acceptable Presentation Contexts
E: 0006:0208 DIMSE No valid Presentation Context ID

Michael Onken
DCMTK Developer
Posts: 2048
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: 0006:0208 DIMSE No valid Presentation Context ID

#6 Post by Michael Onken »

The PACS just does not support the most common Query SOP Class. You could try another one, Patient Root, by using -P instead of -S.

Best,
Michael

mentaanilkumar
Posts: 15
Joined: Thu, 2017-09-07, 09:34

Re: 0006:0208 DIMSE No valid Presentation Context ID

#7 Post by mentaanilkumar »

D: $dcmtk: findscu v3.6.0 2011-01-06 $
D:
D: Request Parameters:
D: ====================== BEGIN A-ASSOCIATE-RQ ====
D: Our Implementation Class UID: 1.2.276.0.723
D: Our Implementation Version Name: OFFIS_DCMTK_3
D: Their Implementation Class UID:
D: Their Implementation Version Name:
D: Application Context Name: 1.2.840.10008.3.1.1
D: Calling Application Name: KPServer
D: Called Application Name: DicomListener
D: Responding Application Name: resp. AP Title
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 0
D: Presentation Contexts:
D: Context ID: 1 (Proposed)
D: Abstract Syntax: =FINDPatientRootQueryRetrie
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
D: =LittleEndianExplicit
D: =BigEndianExplicit
D: =LittleEndianImplicit
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-RQ =====
I: Requesting Association
D: Constructing Associate RQ PDU
D: PDU Type: Associate Accept, PDU Length: 182 + 6
D: 02 00 00 00 00 b6 00 01 00 00 44 69
D: 69 73 74 65 6e 65 72 20 20 20 4b 50
D: 65 72 20 20 20 20 20 20 20 20 00 00
D: 00 00 00 00 00 00 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 10 00
D: 32 2e 38 34 30 2e 31 30 30 30 38 2e
D: 31 2e 31 21 00 00 19 01 00 03 00 40
D: 2e 32 2e 38 34 30 2e 31 30 30 30 38
D: 50 00 00 38 51 00 00 04 00 00 40 00
D: 31 2e 32 2e 38 32 36 2e 30 2e 31 2e
D: 30 34 33 2e 32 2e 33 36 30 2e 30 2e
D: 34 55 00 00 07 49 49 53 5f 33 35 34
D: Parsing an A-ASSOCIATE PDU
D: Association Parameters Negotiated:
D: ====================== BEGIN A-ASSOCIATE-AC ====
D: Our Implementation Class UID: 1.2.276.0.723
D: Our Implementation Version Name: OFFIS_DCMTK_3
D: Their Implementation Class UID: 1.2.826.0.1.3
D: Their Implementation Version Name: IIS_354
D: Application Context Name: 1.2.840.10008.3.1.1
D: Calling Application Name: KPServer
D: Called Application Name: DicomListener
D: Responding Application Name: DicomListener
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 16384
D: Presentation Contexts:
D: Context ID: 1 (Abstract Syntax Not Supp
D: Abstract Syntax: =FINDPatientRootQueryRetrie
D: Proposed SCP/SCU Role: Default
D: Accepted SCP/SCU Role: Default
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-AC =====
E: No Acceptable Presentation Contexts
E: 0006:0208 DIMSE No valid Presentation Context ID

Michael Onken
DCMTK Developer
Posts: 2048
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: 0006:0208 DIMSE No valid Presentation Context ID

#8 Post by Michael Onken »

Hi,

then your PACS does understand Query at all. Maybe the server uses another port for Query Services?

Best,
Michael

P.S: This is overall not a DCMTK question...

mentaanilkumar
Posts: 15
Joined: Thu, 2017-09-07, 09:34

Re: 0006:0208 DIMSE No valid Presentation Context ID

#9 Post by mentaanilkumar »

But the thing is it is working for storescu and echoscu.


D: $dcmtk: echoscu v3.6.0 2011-01-06 $
D:
D: Request Parameters:
D: ====================== BEGIN A-ASSOCIATE-RQ =====================
D: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.0
D: Our Implementation Version Name: OFFIS_DCMTK_360
D: Their Implementation Class UID:
D: Their Implementation Version Name:
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: KPServer
D: Called Application Name: DicomListener
D: Responding Application Name: resp. AP Title
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 0
D: Presentation Contexts:
D: Context ID: 1 (Proposed)
D: Abstract Syntax: =VerificationSOPClass
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
D: =LittleEndianImplicit
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-RQ ======================
I: Requesting Association
D: Constructing Associate RQ PDU
D: PDU Type: Associate Accept, PDU Length: 182 + 6 bytes PDU header
D: 02 00 00 00 00 b6 00 01 00 00 44 69 63 6f 6d 4c
D: 69 73 74 65 6e 65 72 20 20 20 4b 50 53 65 72 76
D: 65 72 20 20 20 20 20 20 20 20 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 10 00 00 15 31 2e
D: 32 2e 38 34 30 2e 31 30 30 30 38 2e 33 2e 31 2e
D: 31 2e 31 21 00 00 19 01 00 00 00 40 00 00 11 31
D: 2e 32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32
D: 50 00 00 38 51 00 00 04 00 00 40 00 52 00 00 21
D: 31 2e 32 2e 38 32 36 2e 30 2e 31 2e 33 36 38 30
D: 30 34 33 2e 32 2e 33 36 30 2e 30 2e 33 2e 35 2e
D: 34 55 00 00 07 49 49 53 5f 33 35 34
D: Parsing an A-ASSOCIATE PDU
D: Association Parameters Negotiated:
D: ====================== BEGIN A-ASSOCIATE-AC =====================
D: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.0
D: Our Implementation Version Name: OFFIS_DCMTK_360
D: Their Implementation Class UID: 1.2.826.0.1.3680043.2.360.0.3.5.4
D: Their Implementation Version Name: IIS_354
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: KPServer
D: Called Application Name: DicomListener
D: Responding Application Name: DicomListener
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 16384
D: Presentation Contexts:
D: Context ID: 1 (Accepted)
D: Abstract Syntax: =VerificationSOPClass
D: Proposed SCP/SCU Role: Default
D: Accepted SCP/SCU Role: Default
D: Accepted Transfer Syntax: =LittleEndianImplicit
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-AC ======================
I: Association Accepted (Max Send PDV: 16372)
I: Sending Echo Request: MsgID 1
I: Received Echo Response (Status: Success)
I: Releasing Association

Michael Onken
DCMTK Developer
Posts: 2048
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: 0006:0208 DIMSE No valid Presentation Context ID

#10 Post by Michael Onken »

Yes, but echoscu does Verification SOP Class, and storescu one or many Storage SOP Classes. findscu does one or more Query SOP Classes. Those are different services, that your target server does not support (at least not under that AE Title and/or port)

Best,
Michael

mentaanilkumar
Posts: 15
Joined: Thu, 2017-09-07, 09:34

Re: 0006:0208 DIMSE No valid Presentation Context ID

#11 Post by mentaanilkumar »

Is there any public server to test whether findscu working or not?

Michael Onken
DCMTK Developer
Posts: 2048
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: 0006:0208 DIMSE No valid Presentation Context ID

#12 Post by Michael Onken »

I can promise findscu is working, it's not the tool... :)

Use dicomserver.co.uk port 104 for testing, e.g.

Code: Select all

findscu -S dicomserver.co.uk 104 -k QueryRetrieveLevel=STUDY -k PatientName

Best,
Michael

Post Reply

Who is online

Users browsing this forum: Ahrefs [Bot], Google [Bot] and 1 guest