MPPSSCU: Error " Cannot write SOP instance to database"

Questions regarding other OFFIS DICOM tools

Moderator: Moderator Team

Post Reply
Message
Author
Arunodaya S
Posts: 18
Joined: Mon, 2016-09-26, 14:08

MPPSSCU: Error " Cannot write SOP instance to database"

#1 Post by Arunodaya S » Mon, 2016-09-26, 14:26

I tried sending an N-CREATE message to the scp using mppsscu , but receiving this error message:

"E: Cannot write SOP instance to database
E: Unable to store current SOP instance: Illegal call, perhaps wrong parameters"


I am unable to send N-SET due to this error. Can anyone please help on this.

Here is the complete log :
------------------------------------------------
I: --MPPSSCU: $dcmtk: mppsscu_e v3.6.0 2011-01-27 $
I: --Copyright (C)2008-2011, OFFIS e.V.
I: --Licensed to:
I:
D: $dcmtk: mppsscu_e v3.6.0 2011-01-27 $
D:
I: Initializing network ...
D: DcmItem::checkTransferSyntax() TransferSyntax="Little Endian Explicit"
D: Configured a total of 2 presentation contexts for SCU
I: Negotiating network association ...
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: STPL-5014100595
D: Called Application Name: MAKHAON
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: =ModalityPerformedProcedureStepSOPClass
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
D: =LittleEndianExplicit
D: Context ID: 3 (Proposed)
D: Abstract Syntax: =ModalityPerformedProcedureStepSOPClass
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
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: 223 + 6 bytes PDU header
D: 02 00 00 00 00 df 00 01 00 00 4d 41 4b 48 41 4f
D: 4e 20 20 20 20 20 20 20 20 20 53 54 50 4c 2d 35
D: 30 31 34 31 30 30 35 39 35 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 1b 01 00 00 00 40 00 00 13 31
D: 2e 32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32
D: 2e 31 21 00 00 19 03 00 00 00 40 00 00 11 31 2e
D: 32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32 50
D: 00 00 42 51 00 00 04 00 00 40 00 52 00 00 22 31
D: 2e 32 2e 38 32 36 2e 30 2e 31 2e 33 36 38 30 30
D: 34 33 2e 32 2e 37 30 36 2e 31 2e 34 2e 32 30 30
D: 34 55 00 00 10 4d 41 4b 48 41 4f 4e 20 4e 65 74
D: 77 6f 72 6b 73
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.706.1.4.2004
D: Their Implementation Version Name: MAKHAON Networks
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: STPL-5014100595
D: Called Application Name: MAKHAON
D: Responding Application Name: MAKHAON
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: =ModalityPerformedProcedureStepSOPClass
D: Proposed SCP/SCU Role: Default
D: Accepted SCP/SCU Role: Default
D: Accepted Transfer Syntax: =LittleEndianExplicit
D: Context ID: 3 (Accepted)
D: Abstract Syntax: =ModalityPerformedProcedureStepSOPClass
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 MPPS request ...
D: --------
D: Issuing N-CREATE request
D: Request dataset:
D:
D: # Dicom-Data-Set
D: # Used TransferSyntax: Little Endian Explicit
D: (0000,1000) UI [1.2.840.10008.3.1.2.3.3.4.2951669361.21] # 40, 1 AffectedSOPInstanceUID
D: (0008,0050) SH [00001] # 6, 1 AccessionNumber
D: (0008,0060) CS [RF] # 2, 1 Modality
D: (0008,1032) SQ (Sequence with explicit length #=1) # 8, 1 ProcedureCodeSequence
D: (fffe,e000) na (Item with explicit length #=0) # 0, 1 Item
D: (fffe,e00d) na (ItemDelimitationItem for re-encoding) # 0, 0 ItemDelimitationItem
D: (fffe,e0dd) na (SequenceDelimitationItem for re-encod.) # 0, 0 SequenceDelimitationItem
D: (0008,1120) SQ (Sequence with explicit length #=1) # 8, 1 ReferencedPatientSequence
D: (fffe,e000) na (Item with explicit length #=0) # 0, 1 Item
D: (fffe,e00d) na (ItemDelimitationItem for re-encoding) # 0, 0 ItemDelimitationItem
D: (fffe,e0dd) na (SequenceDelimitationItem for re-encod.) # 0, 0 SequenceDelimitationItem
D: (0010,0010) PN [qwerty] # 4, 1 PatientName
D: (0010,0020) LO [PID-546] # 8, 1 PatientID
D: (0010,0030) DA [19920217] # 8, 1 PatientBirthDate
D: (0010,0040) CS [Male] # 4, 1 PatientSex
D: (0020,000d) UI [1.2.276.0.7230010.3.2.106] # 26, 1 StudyInstanceUID
D: (0020,0010) SH (no value available) # 0, 0 StudyID
D: (0040,0241) AE [qwqweqwee] # 6, 1 PerformedStationAETitle
D: (0040,0242) SH [qweqwewqeqwe] # 4, 1 PerformedStationName
D: (0040,0243) SH [OT-1] # 4, 1 PerformedLocation
D: (0040,0244) DA [20160926] # 8, 1 PerformedProcedureStepStartDate
D: (0040,0245) TM [170000] # 6, 1 PerformedProcedureStepStartTime
D: (0040,0252) CS [IN PROGRESS] # 12, 1 PerformedProcedureStepStatus
D: (0040,0253) SH [0000018706] # 10, 1 PerformedProcedureStepID
D: (0040,0254) LO [Ortho] # 6, 1 PerformedProcedureStepDescription
D: (0040,0255) LO [Ortho] # 6, 1 PerformedProcedureTypeDescription
D: (0040,0270) SQ (Sequence with explicit length #=1) # 8, 1 ScheduledStepAttributesSequence
D: (fffe,e000) na (Item with explicit length #=0) # 0, 1 Item
D: (fffe,e00d) na (ItemDelimitationItem for re-encoding) # 0, 0 ItemDelimitationItem
D: (fffe,e0dd) na (SequenceDelimitationItem for re-encod.) # 0, 0 SequenceDelimitationItem
D: (0040,0280) ST [None] # 4, 1 CommentsOnThePerformedProcedureStep
D:
D: --------
D: N-CREATE request successfully sent, waiting for response
D: Received N-CREATE response
D: Response Status: Success
E: Cannot write SOP instance to database
E: Unable to store current SOP instance: Illegal call, perhaps wrong parameters
I: Response received with status: Success
I: Releasing Association

------------------------------------------------

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

Re: MPPSSCU: Error " Cannot write SOP instance to database"

#2 Post by Marco Eichelberg » Wed, 2016-10-12, 17:39

The MPPS SCU stores the incoming message in a file and for this purpose needs the ability to create files in the current directory.
It seems like you are running the command in a directory where the tool cannot write to.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest