I am trying to set up a local PACS server in my lab to access the data from the MRI/PET scanner. I have 2 questions and I am hoping that somebody can guide me to solve this problem.
Problem 1: I am able to run Query and see the subject that I want to retrieve the data of from MRI scanner. But, when I click retrieve, the log on the screen is
E: Failed receiveing DIMSE command: 0006:031 Peer aborted Association (or never connected)
GET responses report for study: 1.2.840.113696.376376.500.38586294.20170505170859
0 images transferred, and
0 images transferred with warning, and
2728 images transfers failed
I: Releasing Association
E: Association Release Failed: 0006:0303 DUL Finite State Machine Error: No action defined, state 1 event 10
I: Aborting Association
E: Association Abort Failed: 0006:0303 DUL Finite State Machine Error: No action defined, state 1 event 14
Can anybody guide me as to what is the problem here?
Problem 2: How do I retrieve the data only using command line and not opening GUI everytime?
Thank you for your reply, Andras. But I have the same error with 4.7.0-2017-05-23
On the scanner, I set the port 4054 , AE TILE: LOCALPACS, IP:xx.xx.xx.xx for the local PACS server on which Slicer is running
On Slicer DICOM window, should my storage Port be 4054 or 11112 (default)? Also, Storage AETitle be LOCALPACS or the default (CTKSTORE) is fine? I believe just change the Calling AE TITLE to LOCALPACS should suffice?
Also, where is the .cfg file for the DICOM window GUI called as FORM saved on my computer? I checked Slicer --settings-path but doesn’t have the exact dcmqrscp.cfg that is eventually being used by Slicer?
check if CGET is supported on your scanner. If not, you need to be running the Listener on the Slicer side and your scanner needs to be configured to be able to send to it.
the Slicer listener runs as an independent process (storescp) so you can use our OS tools to look at that process to see what the command line arguments are and use the DCMTK documentation to understand how those map to what your scanner expects.
Often debugging is easiest by using the command line tools independent of Slicer to confirm all the settings and then copy them to Slicer.
Here are some notes about using dcmtk command line tools for storage, query: