0xa900: Error: Refused - Data Set does not match SOP Class

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
martinrame
Posts: 347
Joined: Mon, 2009-02-23, 19:57

0xa900: Error: Refused - Data Set does not match SOP Class

#1 Post by martinrame »

Hi, in dcmqrscp I'm getting the error "0xa900: Error: Refused - Data Set does not match SOP Class" when sending some MPR images generated by a Toshiba CT scanner.

Firstly the images were sent to K-PACS (it receives ok), then to dcmqrscp.

Here is the dicom header:

(Group,Element) TAG Description VR VM Length Value
(0002,0000) FileMetaInformationGroupLength UL 1 4 200
(0002,0001) FileMetaInformationVersion OB 1 2
(0002,0002) MediaStorageSOPClassUID UI 1 26 1.2.840.10008.5.1.4.1.1.7
(0002,0003) MediaStorageSOPInstanceUID UI 1 58 1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.426208
(0002,0010) TransferSyntaxUID UI 1 20 1.2.840.10008.1.2.1
(0002,0012) ImplementationClassUID UI 1 34 1.2.826.0.1.3680043.2.360.0.3.5.4
(0002,0013) ImplementationVersionName SH 1 8 IIS_354
(0008,0008) ImageType CS 3 22 DERIVED\SECONDARY\MPR
(0008,0016) SOPClassUID UI 1 26 1.2.840.10008.5.1.4.1.1.7
(0008,0018) SOPInstanceUID UI 1 58 1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.426208
(0008,0020) StudyDate DA 1 8 20230130
(0008,0021) SeriesDate DA 1 8 20230130
(0008,0022) AcquisitionDate DA 1 8 20230130
(0008,0023) ContentDate DA 1 8 20230130
(0008,0030) StudyTime TM 1 10 191701.000
(0008,0031) SeriesTime TM 1 10 193954.812
(0008,0032) AcquisitionTime TM 1 10 191903.900
(0008,0033) ContentTime TM 1 10 193954.796
(0008,0050) AccessionNumber SH 0 0
(0008,0060) Modality CS 1 2 CT
(0008,0064) ConversionType CS 1 4 WSD
(0008,0070) Manufacturer LO 1 8 TOSHIBA
(0008,0080) InstitutionName LO 1 20 SRIO.PRIVADO RIO IV
(0008,0090) ReferringPhysicianName PN 0 0
(0008,1010) StationName SH 1 10 ID_STATION
(0008,103E) SeriesDescription LO 1 20 Head 3.0 Axial.Ref
(0008,1040) InstitutionalDepartmentName LO 1 14 ID_DEPARTMENT
(0008,1090) ManufacturerModelName LO 1 8 Aquilion
(0010,0010) PatientName PN 1 24 LEONARDI JOSE SEBASTIAN
(0010,0020) PatientID LO 1 8 28802190
(0010,0030) PatientBirthDate DA 1 8 19810424
(0010,0040) PatientSex CS 1 2 M
(0010,1010) PatientAge AS 1 4 041Y
(0010,1030) PatientWeight DS 1 2 90
(0018,1130) TableHeight DS 1 6 +53.00
(0018,1210) ConvolutionKernel SH 1 4 FC23
(0020,000D) StudyInstanceUID UI 1 58 1.2.392.200036.9116.2.6.1.48.1211393409.1675064515.369645
(0020,000E) SeriesInstanceUID UI 1 58 1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.288084
(0020,0010) StudyID SH 1 2 0
(0020,0011) SeriesNumber IS 1 2 15
(0020,0013) InstanceNumber IS 1 2 1
(0020,4000) ImageComments LT 1 10 Axial.Ref
(0028,0002) SamplesPerPixel US 1 2 3
(0028,0004) PhotometricInterpretation CS 1 4 RGB
(0028,0006) PlanarConfiguration US 1 2 0
(0028,0010) Rows US 1 2 512
(0028,0011) Columns US 1 2 512
(0028,0100) BitsAllocated US 1 2 8
(0028,0101) BitsStored US 1 2 8
(0028,0102) HighBit US 1 2 7
(0028,0103) PixelRepresentation US 1 2 0
(0040,0002) ScheduledProcedureStepStartDate DA 1 8 20230130
(0040,0003) ScheduledProcedureStepStartTime TM 1 10 191700.000
(0040,0004) ScheduledProcedureStepEndDate DA 1 8 20230130
(0040,0005) ScheduledProcedureStepEndTime TM 1 10 193700.000
(0040,0244) PerformedProcedureStepStartDate DA 1 8 20230130
(0040,0245) PerformedProcedureStepStartTime TM 1 10 191701.000
(7005,0010) PrivateCreator LO 1 16 TOSHIBA_MEC_CT3
(7FE0,0010) PixelData OW 1 786432

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

Re: 0xa900: Error: Refused - Data Set does not match SOP Class

#2 Post by Michael Onken »

I think we also need association negotiation to answer your question.

The image is a Secondary Capture image. Maybe the something else than Secondary Capture Image Storage SOP Class has been negotiated but the Secondary Capture has then been sent?

Best regards,
Michael

martinrame
Posts: 347
Joined: Mon, 2009-02-23, 19:57

Re: 0xa900: Error: Refused - Data Set does not match SOP Class

#3 Post by martinrame »

Let me write here what the server is receiving:

Code: Select all

2023-02-02 13:18:59.629  INFO - dcmqrdb  - ===================== INCOMING DIMSE MESSAGE ====================
2023-02-02 13:18:59.629  INFO - dcmqrdb  - Message Type                  : C-STORE RQ
2023-02-02 13:18:59.629  INFO - dcmqrdb  - Message ID                    : 99
2023-02-02 13:18:59.629  INFO - dcmqrdb  - Affected SOP Class UID        : SecondaryCaptureImageStorage
2023-02-02 13:18:59.629  INFO - dcmqrdb  - Affected SOP Instance UID     : 1.2.392.200036.9116.2.6.1.48.1211005721.1675075204.76976
2023-02-02 13:18:59.629  INFO - dcmqrdb  - Data Set                      : present
2023-02-02 13:18:59.629  INFO - dcmqrdb  - Priority                      : medium
2023-02-02 13:18:59.629  INFO - dcmqrdb  - ======================= END DIMSE MESSAGE =======================
... here comes the data ...

Code: Select all

2023-02-02 13:19:00.293  WARN - dcmqrdb  - ===================== OUTGOING DIMSE MESSAGE ====================
2023-02-02 13:19:00.293  WARN - dcmqrdb  - Message Type                  : C-STORE RSP
2023-02-02 13:19:00.293  WARN - dcmqrdb  - Message ID Being Responded To : 99
2023-02-02 13:19:00.293  WARN - dcmqrdb  - Affected SOP Class UID        : SecondaryCaptureImageStorage
2023-02-02 13:19:00.293  WARN - dcmqrdb  - Affected SOP Instance UID     : 1.2.392.200036.9116.2.6.1.48.1211005721.1675075204.76976
2023-02-02 13:19:00.293  WARN - dcmqrdb  - Data Set                      : none
2023-02-02 13:19:00.293  WARN - dcmqrdb  - DIMSE Status                  : 0xa900: Error: Refused - Data Set does not match SOP Class
2023-02-02 13:19:00.293  WARN - dcmqrdb  - ======================= END DIMSE MESSAGE =======================
I'll have to modify my dcmqrscp to store the file, because now, when there's an error I delete that file.

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

Re: 0xa900: Error: Refused - Data Set does not match SOP Class

#4 Post by Michael Onken »

Hi,

thanks, what I would need to see is the association negotiation log, i.e. the SOP Class and transfer syntax negotiation that takes place at the beginning of the connection.

Best,
Michael

martinrame
Posts: 347
Joined: Mon, 2009-02-23, 19:57

Re: 0xa900: Error: Refused - Data Set does not match SOP Class

#5 Post by martinrame »

Ok, please take a look:

Code: Select all

2023-02-02 13:27:22.268 DEBUG - dcmnet   - setting network send timeout to 60 seconds
2023-02-02 13:27:22.268 DEBUG - dcmnet   - setting network receive timeout to 60 seconds
2023-02-02 13:27:22.270 DEBUG - dcmnet   - PDU Type: Associate Request, PDU Length: 262 + 6 bytes PDU header
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   01  00  00  00  01  06  00  01  00  00  53  50  52  49  4f  49
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   56  53  43  50  00  00  00  00  00  00  53  45  52  56  45  52
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   00  00  00  00  00  00  00  00  00  00  10  00  00  15  31  2e
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   32  2e  38  34  30  2e  31  30  30  30  38  2e  33  2e  31  2e
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   31  2e  31  20  00  00  67  01  00  00  00  30  00  00  19  31
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   2e  32  2e  38  34  30  2e  31  30  30  30  38  2e  35  2e  31
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   2e  34  2e  31  2e  31  2e  32  40  00  00  16  31  2e  32  2e
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   38  34  30  2e  31  30  30  30  38  2e  31  2e  32  2e  34  2e
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   37  30  40  00  00  13  31  2e  32  2e  38  34  30  2e  31  30
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   30  30  38  2e  31  2e  32  2e  31  40  00  00  11  31  2e  32
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   2e  38  34  30  2e  31  30  30  30  38  2e  31  2e  32  50  00
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   00  3a  51  00  00  04  00  00  40  00  52  00  00  1e  31  2e
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   32  2e  38  32  36  2e  30  2e  31  2e  33  36  38  30  30  34
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   33  2e  32  2e  31  33  39  36  2e  39  39  39  55  00  00  0c
2023-02-02 13:27:22.270 DEBUG - dcmnet   -   43  68  61  72  72  75  61  56  69  73  74  61
2023-02-02 13:27:22.271 DEBUG - dcmnet   - Parsing an A-ASSOCIATE PDU
2023-02-02 13:27:22.271  INFO - dcmqrdb  - Association Received (200.123.248.6:SERVER -> SPRIOIVSCP) Thu Feb  2 13:27:22 2023
2023-02-02 13:27:22.271  INFO - dcmqrdb  -
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Parameters:
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - ====================== BEGIN A-ASSOCIATE-RQ =====================
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Our Implementation Class UID:      1.2.276.0.7230010.3.0.3.6.2
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Our Implementation Version Name:   OFFIS_DCMTK_362
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Their Implementation Class UID:    1.2.826.0.1.3680043.2.1396.999
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Their Implementation Version Name: CharruaVista
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Application Context Name:    1.2.840.10008.3.1.1.1
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Calling Application Name:    SERVER
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Called Application Name:     SPRIOIVSCP
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Responding Application Name:
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Our Max PDU Receive Size:    16384
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Their Max PDU Receive Size:  16384
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Presentation Contexts:
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  -   Context ID:        1 (Proposed)
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  -     Abstract Syntax: =CTImageStorage
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  -     Proposed SCP/SCU Role: Default
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  -     Proposed Transfer Syntax(es):
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  -       =JPEGLossless:Non-hierarchical-1stOrderPrediction
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  -       =LittleEndianExplicit
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  -       =LittleEndianImplicit
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Requested Extended Negotiation: none
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Accepted Extended Negotiation:  none
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - Requested User Identity Negotiation: none
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - User Identity Negotiation Response:  none
2023-02-02 13:27:22.271 DEBUG - dcmqrdb  - ======================= END A-ASSOCIATE-RQ ======================
2023-02-02 13:27:22.271 DEBUG - dcmnet   - Constructing Associate AC PDU
2023-02-02 13:27:22.271  INFO - dcmqrdb  - Association Acknowledged (Max Send PDV: 16372)
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - ====================== BEGIN A-ASSOCIATE-AC =====================
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Our Implementation Class UID:      1.2.276.0.7230010.3.0.3.6.2
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Our Implementation Version Name:   OFFIS_DCMTK_362
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Their Implementation Class UID:    1.2.826.0.1.3680043.2.1396.999
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Their Implementation Version Name: CharruaVista
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Application Context Name:    1.2.840.10008.3.1.1.1
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Calling Application Name:    SERVER
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Called Application Name:     SPRIOIVSCP
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Responding Application Name:
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Our Max PDU Receive Size:    16384
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Their Max PDU Receive Size:  16384
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Presentation Contexts:
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  -   Context ID:        1 (Accepted)
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  -     Abstract Syntax: =CTImageStorage
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  -     Proposed SCP/SCU Role: Default
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  -     Accepted SCP/SCU Role: Default
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  -     Accepted Transfer Syntax: =JPEGLossless:Non-hierarchical-1stOrderPrediction
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Requested Extended Negotiation: none
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Accepted Extended Negotiation:  none
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - Requested User Identity Negotiation: none
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - User Identity Negotiation Response:  none
2023-02-02 13:27:22.272 DEBUG - dcmqrdb  - ======================= END A-ASSOCIATE-AC ======================
2023-02-02 13:27:22.461 DEBUG - dcmdata  - DcmDataset::read() TransferSyntax="Little Endian Implicit"
2023-02-02 13:27:22.462  INFO - dcmqrdb  - Received Store SCP:
2023-02-02 13:27:22.462  INFO - dcmqrdb  - ===================== INCOMING DIMSE MESSAGE ====================
2023-02-02 13:27:22.462  INFO - dcmqrdb  - Message Type                  : C-STORE RQ
2023-02-02 13:27:22.462  INFO - dcmqrdb  - Message ID                    : 3
2023-02-02 13:27:22.462  INFO - dcmqrdb  - Affected SOP Class UID        : CTImageStorage
2023-02-02 13:27:22.462  INFO - dcmqrdb  - Affected SOP Instance UID     : 1.2.392.200036.9116.2.6.1.48.1211393409.1675299857.297915
2023-02-02 13:27:22.462  INFO - dcmqrdb  - Data Set                      : present
2023-02-02 13:27:22.462  INFO - dcmqrdb  - Priority                      : medium
2023-02-02 13:27:22.462  INFO - dcmqrdb  - ======================= END DIMSE MESSAGE =======================

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

Re: 0xa900: Error: Refused - Data Set does not match SOP Class

#6 Post by Michael Onken »

Hey,

this seems to be unrelated to your original question. In the log you send last, a CT file is transferred:

Code: Select all

2023-02-02 13:27:22.462  INFO - dcmqrdb  - ===================== INCOMING DIMSE MESSAGE ====================
2023-02-02 13:27:22.462  INFO - dcmqrdb  - Message Type                  : C-STORE RQ
2023-02-02 13:27:22.462  INFO - dcmqrdb  - Message ID                    : 3
2023-02-02 13:27:22.462  INFO - dcmqrdb  - Affected SOP Class UID        : CTImageStorage
In your first original report it was a Secondary Capture. Please send the log from the error case. From the beginning (association negotiation as you send in the last log) up to the message with the DIMSE error ("0xa900: Error: Refused - Data Set does not match SOP Class").

BR Michael

martinrame
Posts: 347
Joined: Mon, 2009-02-23, 19:57

Re: 0xa900: Error: Refused - Data Set does not match SOP Class

#7 Post by martinrame »

Sorry, here is the complete frame, from 13:18:30 to 13:18:33.

It looks like the issue happens when more than one Secondary Capture image is sent in the same association. In this association there is a Message ID: 3 that's received ok, but Message ID: 5, 7 and 9 are wrong.

Code: Select all

2023-02-02 13:18:30.429 DEBUG - dcmnet   - PDU Type: Associate Request, PDU Length: 262 + 6 bytes PDU header
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   01  00  00  00  01  06  00  01  00  00  53  50  52  49  4f  49
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   56  53  43  50  00  00  00  00  00  00  53  45  52  56  45  52
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   00  00  00  00  00  00  00  00  00  00  00  00  00  00  00  00
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   00  00  00  00  00  00  00  00  00  00  10  00  00  15  31  2e
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   32  2e  38  34  30  2e  31  30  30  30  38  2e  33  2e  31  2e
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   31  2e  31  20  00  00  67  01  00  00  00  30  00  00  19  31
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   2e  32  2e  38  34  30  2e  31  30  30  30  38  2e  35  2e  31
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   2e  34  2e  31  2e  31  2e  37  40  00  00  16  31  2e  32  2e
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   38  34  30  2e  31  30  30  30  38  2e  31  2e  32  2e  34  2e
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   37  30  40  00  00  13  31  2e  32  2e  38  34  30  2e  31  30
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   30  30  38  2e  31  2e  32  2e  31  40  00  00  11  31  2e  32
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   2e  38  34  30  2e  31  30  30  30  38  2e  31  2e  32  50  00
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   00  3a  51  00  00  04  00  00  40  00  52  00  00  1e  31  2e
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   32  2e  38  32  36  2e  30  2e  31  2e  33  36  38  30  30  34
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   33  2e  32  2e  31  33  39  36  2e  39  39  39  55  00  00  0c
2023-02-02 13:18:30.429 DEBUG - dcmnet   -   43  68  61  72  72  75  61  56  69  73  74  61
2023-02-02 13:18:30.429 DEBUG - dcmnet   - Parsing an A-ASSOCIATE PDU
2023-02-02 13:18:30.429  INFO - dcmqrdb  - Association Received (200.123.248.6:SERVER -> SPRIOIVSCP) Thu Feb  2 13:18:30 2023
2023-02-02 13:18:30.429  INFO - dcmqrdb  - 
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Parameters:
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - ====================== BEGIN A-ASSOCIATE-RQ =====================
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Our Implementation Class UID:      1.2.276.0.7230010.3.0.3.6.2
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Our Implementation Version Name:   OFFIS_DCMTK_362
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Their Implementation Class UID:    1.2.826.0.1.3680043.2.1396.999
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Their Implementation Version Name: CharruaVista
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Application Context Name:    1.2.840.10008.3.1.1.1
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Calling Application Name:    SERVER
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Called Application Name:     SPRIOIVSCP
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Responding Application Name: 
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Our Max PDU Receive Size:    16384
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Their Max PDU Receive Size:  16384
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Presentation Contexts:
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  -   Context ID:        1 (Proposed)
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  -     Abstract Syntax: =SecondaryCaptureImageStorage
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  -     Proposed SCP/SCU Role: Default
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  -     Proposed Transfer Syntax(es):
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  -       =JPEGLossless:Non-hierarchical-1stOrderPrediction
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  -       =LittleEndianExplicit
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  -       =LittleEndianImplicit
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Requested Extended Negotiation: none
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Accepted Extended Negotiation:  none
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - Requested User Identity Negotiation: none
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - User Identity Negotiation Response:  none
2023-02-02 13:18:30.430 DEBUG - dcmqrdb  - ======================= END A-ASSOCIATE-RQ ======================
2023-02-02 13:18:30.433 DEBUG - dcmnet   - Constructing Associate AC PDU
2023-02-02 13:18:30.433  INFO - dcmqrdb  - Association Acknowledged (Max Send PDV: 16372)
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - ====================== BEGIN A-ASSOCIATE-AC =====================
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Our Implementation Class UID:      1.2.276.0.7230010.3.0.3.6.2
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Our Implementation Version Name:   OFFIS_DCMTK_362
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Their Implementation Class UID:    1.2.826.0.1.3680043.2.1396.999
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Their Implementation Version Name: CharruaVista
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Application Context Name:    1.2.840.10008.3.1.1.1
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Calling Application Name:    SERVER
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Called Application Name:     SPRIOIVSCP
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Responding Application Name: 
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Our Max PDU Receive Size:    16384
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Their Max PDU Receive Size:  16384
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Presentation Contexts:
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  -   Context ID:        1 (Accepted)
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  -     Abstract Syntax: =SecondaryCaptureImageStorage
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  -     Proposed SCP/SCU Role: Default
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  -     Accepted SCP/SCU Role: Default
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  -     Accepted Transfer Syntax: =JPEGLossless:Non-hierarchical-1stOrderPrediction
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Requested Extended Negotiation: none
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Accepted Extended Negotiation:  none
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - Requested User Identity Negotiation: none
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - User Identity Negotiation Response:  none
2023-02-02 13:18:30.435 DEBUG - dcmqrdb  - ======================= END A-ASSOCIATE-AC ======================
2023-02-02 13:18:30.640 DEBUG - dcmdata  - DcmDataset::read() TransferSyntax="Little Endian Implicit"
2023-02-02 13:18:30.641  INFO - dcmqrdb  - Received Store SCP:
2023-02-02 13:18:30.641  INFO - dcmqrdb  - ===================== INCOMING DIMSE MESSAGE ====================
2023-02-02 13:18:30.641  INFO - dcmqrdb  - Message Type                  : C-STORE RQ
2023-02-02 13:18:30.641  INFO - dcmqrdb  - Message ID                    : 3
2023-02-02 13:18:30.641  INFO - dcmqrdb  - Affected SOP Class UID        : SecondaryCaptureImageStorage
2023-02-02 13:18:30.641  INFO - dcmqrdb  - Affected SOP Instance UID     : 1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.426208
2023-02-02 13:18:30.641  INFO - dcmqrdb  - Data Set                      : present
2023-02-02 13:18:30.641  INFO - dcmqrdb  - Priority                      : medium
2023-02-02 13:18:30.641  INFO - dcmqrdb  - ======================= END DIMSE MESSAGE =======================
2023-02-02 13:18:30.641  INFO - dcmqrdb  - General dicom storage directory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage
2023-02-02 13:18:30.641  INFO - dcmqrdb  - Using callingAETitle as name for a new subdirectory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER
2023-02-02 13:18:30.641 DEBUG - dcmqrdb  - Checking for directory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER
2023-02-02 13:18:30.641  INFO - dcmqrdb  - New subdirectory to be created: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02
2023-02-02 13:18:30.641 DEBUG - dcmqrdb  - Checking for directory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02
2023-02-02 13:18:30.641  INFO - dcmqrdb  - Final subdirectory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02
2023-02-02 13:18:30.641  INFO - dcmqrdb  - [FE00001] File already exists. It will be replaced. 
2023-02-02 13:18:30.641  INFO - dcmqrdb  - Saving file: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02/SC_1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.426208.dcm
2023-02-02 13:18:30.641  INFO - dcmqrdb  - File saved.
2023-02-02 13:18:30.671 DEBUG - dcmdata  - DcmDataset::read() TransferSyntax="JPEG Lossless, Non-hierarchical, 1st Order Prediction"
2023-02-02 13:18:31.431  INFO - dcmqrdb  - --- Chequeando transfer syntax original ---
2023-02-02 13:18:31.431  INFO - dcmqrdb  - Transfer Syntax Original: JPEG Lossless, Non-hierarchical, 1st Order Prediction
2023-02-02 13:18:31.431  INFO - dcmqrdb  - DICOM file is already compressed, converting to uncompressed transfer syntax first
2023-02-02 13:18:31.432 DEBUG - dcmjpeg  - Start of Image
2023-02-02 13:18:31.432 DEBUG - dcmjpeg  - Adobe APP14 marker: version 100, flags 0x0000 0x0000, transform 0
2023-02-02 13:18:31.432 DEBUG - dcmjpeg  - Start Of Frame 0xc3: width=512, height=512, components=3
2023-02-02 13:18:31.432 DEBUG - dcmjpeg  -     Component 82: 1hx1v q=0
2023-02-02 13:18:31.432 DEBUG - dcmjpeg  -     Component 71: 1hx1v q=0
2023-02-02 13:18:31.432 DEBUG - dcmjpeg  -     Component 66: 1hx1v q=0
2023-02-02 13:18:31.432 DEBUG - dcmjpeg  - Define Huffman Table 0x00
2023-02-02 13:18:31.432 DEBUG - dcmjpeg  - Start Of Scan: 3 components
2023-02-02 13:18:31.432 DEBUG - dcmjpeg  -     Component 82: dc=0 ac=0
2023-02-02 13:18:31.432 DEBUG - dcmjpeg  -     Component 71: dc=0 ac=0
2023-02-02 13:18:31.432 DEBUG - dcmjpeg  -     Component 66: dc=0 ac=0
2023-02-02 13:18:31.432 DEBUG - dcmjpeg  -   Ss=1, Se=0, Ah=0, Al=0
2023-02-02 13:18:31.438 DEBUG - dcmjpeg  - End Of Image
2023-02-02 13:18:31.438  INFO - dcmqrdb  - Transfer Syntax Configurado: JPEG Lossless, Non-hierarchical, 1st Order Prediction
2023-02-02 13:18:31.438  INFO - dcmqrdb  - Linea 148 - dcmqrcbs.cc
2023-02-02 13:18:31.450 DEBUG - dcmdata  - DcmPixelItem: creating offset table with 1 entries
2023-02-02 13:18:31.450  INFO - dcmqrdb  - Output transfer syntax JPEG Lossless, Non-hierarchical, 1st Order Prediction can be written
2023-02-02 13:18:31.450  INFO - dcmqrdb  - creating output file /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02/SC_1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.426208.dcm
2023-02-02 13:18:31.450 DEBUG - dcmdata  - DcmFileFormat::checkMetaHeaderValue() Version of MetaHeader is ok: 0x0001
2023-02-02 13:18:31.450 DEBUG - dcmdata  - DcmFileFormat::checkMetaHeaderValue() use SOPClassUID [1.2.840.10008.5.1.4.1.1.7] from Dataset
2023-02-02 13:18:31.450 DEBUG - dcmdata  - DcmFileFormat::checkMetaHeaderValue() use SOPInstanceUID [1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.426208] from Dataset
2023-02-02 13:18:31.450 DEBUG - dcmdata  - DcmFileFormat::checkMetaHeaderValue() use new TransferSyntaxUID [JPEG Lossless, Non-hierarchical, 1st Order Prediction] on writing following Dataset
2023-02-02 13:18:31.451 DEBUG - dcmdata  - DcmFileFormat::validateMetaInfo() found 8 Elements in DcmMetaInfo 'metinf'
2023-02-02 13:18:31.451 DEBUG - dcmdata  - DcmItem::computeGroupLengthAndPadding() Length of Group 0x0008 len=604
2023-02-02 13:18:31.451 DEBUG - dcmdata  - DcmItem::computeGroupLengthAndPadding() Length of Group 0x0010 len=96
2023-02-02 13:18:31.451 DEBUG - dcmdata  - DcmItem::computeGroupLengthAndPadding() Length of Group 0x0018 len=26
2023-02-02 13:18:31.451 DEBUG - dcmdata  - DcmItem::computeGroupLengthAndPadding() Length of Group 0x0020 len=180
2023-02-02 13:18:31.451 DEBUG - dcmdata  - DcmItem::computeGroupLengthAndPadding() Length of Group 0x0028 len=92
2023-02-02 13:18:31.451  WARN - dcmdata  - DcmItem: Group Length with VR other than UL found, corrected
2023-02-02 13:18:31.451 DEBUG - dcmdata  - DcmItem::computeGroupLengthAndPadding() Length of Group 0x0040 len=102
2023-02-02 13:18:31.451 DEBUG - dcmdata  - DcmItem::computeGroupLengthAndPadding() Length of Group 0x7005 len=544
2023-02-02 13:18:31.454 DEBUG - dcmdata  - DcmMetaInfo::checkAndReadPreamble() TransferSyntax="Little Endian Explicit"
2023-02-02 13:18:31.454 DEBUG - dcmdata  - DcmDataset::read() TransferSyntax="JPEG Lossless, Non-hierarchical, 1st Order Prediction"
2023-02-02 13:18:31.494  INFO - dcmqrdb  - Sending:
2023-02-02 13:18:31.494  INFO - dcmqrdb  - ===================== OUTGOING DIMSE MESSAGE ====================
2023-02-02 13:18:31.494  INFO - dcmqrdb  - Message Type                  : C-STORE RSP
2023-02-02 13:18:31.494  INFO - dcmqrdb  - Message ID Being Responded To : 3
2023-02-02 13:18:31.494  INFO - dcmqrdb  - Affected SOP Class UID        : SecondaryCaptureImageStorage
2023-02-02 13:18:31.494  INFO - dcmqrdb  - Affected SOP Instance UID     : 1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.426208
2023-02-02 13:18:31.494  INFO - dcmqrdb  - Data Set                      : none
2023-02-02 13:18:31.494  INFO - dcmqrdb  - DIMSE Status                  : 0x0000: Success
2023-02-02 13:18:31.494  INFO - dcmqrdb  - ======================= END DIMSE MESSAGE =======================
2023-02-02 13:18:31.873 DEBUG - dcmdata  - DcmDataset::read() TransferSyntax="Little Endian Implicit"
2023-02-02 13:18:31.873  INFO - dcmqrdb  - Received Store SCP:
2023-02-02 13:18:31.873  INFO - dcmqrdb  - ===================== INCOMING DIMSE MESSAGE ====================
2023-02-02 13:18:31.873  INFO - dcmqrdb  - Message Type                  : C-STORE RQ
2023-02-02 13:18:31.873  INFO - dcmqrdb  - Message ID                    : 5
2023-02-02 13:18:31.873  INFO - dcmqrdb  - Affected SOP Class UID        : SecondaryCaptureImageStorage
2023-02-02 13:18:31.873  INFO - dcmqrdb  - Affected SOP Instance UID     : 1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.667504
2023-02-02 13:18:31.873  INFO - dcmqrdb  - Data Set                      : present
2023-02-02 13:18:31.873  INFO - dcmqrdb  - Priority                      : medium
2023-02-02 13:18:31.873  INFO - dcmqrdb  - ======================= END DIMSE MESSAGE =======================
2023-02-02 13:18:31.873  INFO - dcmqrdb  - General dicom storage directory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage
2023-02-02 13:18:31.873  INFO - dcmqrdb  - Using callingAETitle as name for a new subdirectory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER
2023-02-02 13:18:31.873 DEBUG - dcmqrdb  - Checking for directory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER
2023-02-02 13:18:31.873  INFO - dcmqrdb  - New subdirectory to be created: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02
2023-02-02 13:18:31.873 DEBUG - dcmqrdb  - Checking for directory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02
2023-02-02 13:18:31.874  INFO - dcmqrdb  - Final subdirectory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02
2023-02-02 13:18:31.874  INFO - dcmqrdb  - Saving file: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02/SC_1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.667504.dcm
2023-02-02 13:18:31.874  INFO - dcmqrdb  - File saved.
2023-02-02 13:18:31.912 DEBUG - dcmdata  - DcmDataset::read() TransferSyntax="JPEG Lossless, Non-hierarchical, 1st Order Prediction"
2023-02-02 13:18:32.068  WARN - dcmqrdb  - NOTICE: StoreSCP:
2023-02-02 13:18:32.068  WARN - dcmqrdb  - ===================== OUTGOING DIMSE MESSAGE ====================
2023-02-02 13:18:32.068  WARN - dcmqrdb  - Message Type                  : C-STORE RSP
2023-02-02 13:18:32.068  WARN - dcmqrdb  - Message ID Being Responded To : 5
2023-02-02 13:18:32.068  WARN - dcmqrdb  - Affected SOP Class UID        : SecondaryCaptureImageStorage
2023-02-02 13:18:32.068  WARN - dcmqrdb  - Affected SOP Instance UID     : 1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.667504
2023-02-02 13:18:32.068  WARN - dcmqrdb  - Data Set                      : none
2023-02-02 13:18:32.068  WARN - dcmqrdb  - DIMSE Status                  : 0xa900: Error: Refused - Data Set does not match SOP Class
2023-02-02 13:18:32.068  WARN - dcmqrdb  - ======================= END DIMSE MESSAGE =======================
2023-02-02 13:18:32.068  INFO - dcmqrdb  - Store SCP: Deleting Image File: %s/mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02/SC_1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.667504.dcm
2023-02-02 13:18:32.438 DEBUG - dcmdata  - DcmDataset::read() TransferSyntax="Little Endian Implicit"
2023-02-02 13:18:32.438  INFO - dcmqrdb  - Received Store SCP:
2023-02-02 13:18:32.438  INFO - dcmqrdb  - ===================== INCOMING DIMSE MESSAGE ====================
2023-02-02 13:18:32.438  INFO - dcmqrdb  - Message Type                  : C-STORE RQ
2023-02-02 13:18:32.438  INFO - dcmqrdb  - Message ID                    : 7
2023-02-02 13:18:32.438  INFO - dcmqrdb  - Affected SOP Class UID        : SecondaryCaptureImageStorage
2023-02-02 13:18:32.438  INFO - dcmqrdb  - Affected SOP Instance UID     : 1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.846693
2023-02-02 13:18:32.438  INFO - dcmqrdb  - Data Set                      : present
2023-02-02 13:18:32.438  INFO - dcmqrdb  - Priority                      : medium
2023-02-02 13:18:32.438  INFO - dcmqrdb  - ======================= END DIMSE MESSAGE =======================
2023-02-02 13:18:32.438  INFO - dcmqrdb  - General dicom storage directory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage
2023-02-02 13:18:32.438  INFO - dcmqrdb  - Using callingAETitle as name for a new subdirectory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER
2023-02-02 13:18:32.438 DEBUG - dcmqrdb  - Checking for directory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER
2023-02-02 13:18:32.438  INFO - dcmqrdb  - New subdirectory to be created: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02
2023-02-02 13:18:32.438 DEBUG - dcmqrdb  - Checking for directory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02
2023-02-02 13:18:32.439  INFO - dcmqrdb  - Final subdirectory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02
2023-02-02 13:18:32.439  INFO - dcmqrdb  - Saving file: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02/SC_1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.846693.dcm
2023-02-02 13:18:32.439  INFO - dcmqrdb  - File saved.
2023-02-02 13:18:32.489 DEBUG - dcmdata  - DcmDataset::read() TransferSyntax="JPEG Lossless, Non-hierarchical, 1st Order Prediction"
2023-02-02 13:18:32.643  WARN - dcmqrdb  - NOTICE: StoreSCP:
2023-02-02 13:18:32.643  WARN - dcmqrdb  - ===================== OUTGOING DIMSE MESSAGE ====================
2023-02-02 13:18:32.643  WARN - dcmqrdb  - Message Type                  : C-STORE RSP
2023-02-02 13:18:32.643  WARN - dcmqrdb  - Message ID Being Responded To : 7
2023-02-02 13:18:32.643  WARN - dcmqrdb  - Affected SOP Class UID        : SecondaryCaptureImageStorage
2023-02-02 13:18:32.643  WARN - dcmqrdb  - Affected SOP Instance UID     : 1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.846693
2023-02-02 13:18:32.643  WARN - dcmqrdb  - Data Set                      : none
2023-02-02 13:18:32.643  WARN - dcmqrdb  - DIMSE Status                  : 0xa900: Error: Refused - Data Set does not match SOP Class
2023-02-02 13:18:32.643  WARN - dcmqrdb  - ======================= END DIMSE MESSAGE =======================
2023-02-02 13:18:32.643  INFO - dcmqrdb  - Store SCP: Deleting Image File: %s/mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02/SC_1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.846693.dcm
2023-02-02 13:18:33.014 DEBUG - dcmdata  - DcmDataset::read() TransferSyntax="Little Endian Implicit"
2023-02-02 13:18:33.014  INFO - dcmqrdb  - Received Store SCP:
2023-02-02 13:18:33.014  INFO - dcmqrdb  - ===================== INCOMING DIMSE MESSAGE ====================
2023-02-02 13:18:33.014  INFO - dcmqrdb  - Message Type                  : C-STORE RQ
2023-02-02 13:18:33.014  INFO - dcmqrdb  - Message ID                    : 9
2023-02-02 13:18:33.014  INFO - dcmqrdb  - Affected SOP Class UID        : SecondaryCaptureImageStorage
2023-02-02 13:18:33.014  INFO - dcmqrdb  - Affected SOP Instance UID     : 1.2.392.200036.9116.2.6.1.48.1211005721.1675075196.215835
2023-02-02 13:18:33.014  INFO - dcmqrdb  - Data Set                      : present
2023-02-02 13:18:33.014  INFO - dcmqrdb  - Priority                      : medium
2023-02-02 13:18:33.014  INFO - dcmqrdb  - ======================= END DIMSE MESSAGE =======================
2023-02-02 13:18:33.014  INFO - dcmqrdb  - General dicom storage directory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage
2023-02-02 13:18:33.014  INFO - dcmqrdb  - Using callingAETitle as name for a new subdirectory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER
2023-02-02 13:18:33.014 DEBUG - dcmqrdb  - Checking for directory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER
2023-02-02 13:18:33.015  INFO - dcmqrdb  - New subdirectory to be created: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02
2023-02-02 13:18:33.015 DEBUG - dcmqrdb  - Checking for directory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02
2023-02-02 13:18:33.015  INFO - dcmqrdb  - Final subdirectory: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02
2023-02-02 13:18:33.015  INFO - dcmqrdb  - Saving file: /mnt/disk2/sitios/sprioiv/scp/dicomstorage/SERVER/2023-02-02/SC_1.2.392.200036.9116.2.6.1.48.1211005721.1675075196.215835.dcm
2023-02-02 13:18:33.015  INFO - dcmqrdb  - File saved.
2023-02-02 13:18:33.054 DEBUG - dcmdata  - DcmDataset::read() TransferSyntax="JPEG Lossless, Non-hierarchical, 1st Order Prediction"
2023-02-02 13:18:33.208  WARN - dcmqrdb  - NOTICE: StoreSCP:
2023-02-02 13:18:33.208  WARN - dcmqrdb  - ===================== OUTGOING DIMSE MESSAGE ====================
2023-02-02 13:18:33.208  WARN - dcmqrdb  - Message Type                  : C-STORE RSP
2023-02-02 13:18:33.208  WARN - dcmqrdb  - Message ID Being Responded To : 9
2023-02-02 13:18:33.208  WARN - dcmqrdb  - Affected SOP Class UID        : SecondaryCaptureImageStorage
2023-02-02 13:18:33.208  WARN - dcmqrdb  - Affected SOP Instance UID     : 1.2.392.200036.9116.2.6.1.48.1211005721.1675075196.215835
2023-02-02 13:18:33.208  WARN - dcmqrdb  - Data Set                      : none
2023-02-02 13:18:33.208  WARN - dcmqrdb  - DIMSE Status                  : 0xa900: Error: Refused - Data Set does not match SOP Class
2023-02-02 13:18:33.208  WARN - dcmqrdb  - ======================= END DIMSE MESSAGE =======================

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

Re: 0xa900: Error: Refused - Data Set does not match SOP Class

#8 Post by Michael Onken »

Thank you. The network log looks OK from what I can say, i.e. there is nothing obviously wrong.

However, note that in the log you have the error with the image with SOP Instance UID 1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.667504 while in the dump you sent in your first post the image has the UID 58 1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.426208.

Can you provide the dump for image 1.2.392.200036.9116.2.6.1.48.1211005721.1675075195.667504 instead? Then all pieces actually belong together : ) You could also send me the file under forum at open-connections dot de.

Best regards,
Michael

martinrame
Posts: 347
Joined: Mon, 2009-02-23, 19:57

Re: 0xa900: Error: Refused - Data Set does not match SOP Class

#9 Post by martinrame »

I think I found the solution.

K-PACS has two C-STORE modes, one using the internal method (the default) and one using DCMTKś

In file k-pacs.ini, there's this parameter:

UseDCMTKStore=0

If you change it to this:

UseDCMTKStore=1

The C-STORE uses dcmtk instead of the internal, and everything starts to work ok.

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

Re: 0xa900: Error: Refused - Data Set does not match SOP Class

#10 Post by Michael Onken »

Ok, whatever the problem with the other "store mode" was...

Marco Eichelberg
OFFIS DICOM Team
OFFIS DICOM Team
Posts: 1437
Joined: Tue, 2004-11-02, 17:22
Location: Oldenburg, Germany
Contact:

Re: 0xa900: Error: Refused - Data Set does not match SOP Class

#11 Post by Marco Eichelberg »

My guess would be an incorrect presentation context ID used in the C-STORE-RQ message. Unfortunately, the dump output of our tools does not print this ID - perhaps something we should change.

J. Riesmeier
DCMTK Developer
Posts: 2501
Joined: Tue, 2011-05-03, 14:38
Location: Oldenburg, Germany
Contact:

Re: 0xa900: Error: Refused - Data Set does not match SOP Class

#12 Post by J. Riesmeier »

Actually, some DCMTK tools do print this information, e.g. dcmsend and dcmrecv, so the underlying dcmnet functions already support it. This feature just has to be enabled in other DCMTK networking tools.

Code: Select all

D: ===================== INCOMING DIMSE MESSAGE ====================
D: Message Type                  : C-STORE RQ
D: Presentation Context ID       : 1
D: Message ID                    : 1
D: Affected SOP Class UID        : ComprehensiveSRStorage
D: Affected SOP Instance UID     : 1.2.276.0.7230010.3.1.4.1787205428.26111.1248711438.4
D: Data Set                      : present
D: Priority                      : medium
D: ======================= END DIMSE MESSAGE =======================
D: received dataset is not stored since the storage mode is set to 'ignore'
I: Sending C-STORE Response
D: ===================== OUTGOING DIMSE MESSAGE ====================
D: Message Type                  : C-STORE RSP
D: Presentation Context ID       : 1
D: Message ID Being Responded To : 1
D: Affected SOP Class UID        : ComprehensiveSRStorage
D: Affected SOP Instance UID     : 1.2.276.0.7230010.3.1.4.1787205428.26111.1248711438.4
D: Data Set                      : none
D: DIMSE Status                  : 0x0000: Success
D: ======================= END DIMSE MESSAGE =======================

Post Reply

Who is online

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