Canceled C-Move kill conquest Server

Tetraib · Aug 22nd 2017

Hi,
We just connected a carestream streaming server to our conquest PACS : it basicly querys conquest to retrieve the dicom as needed.

We face strange behavior/bug when a c-move operation is cancelled in the middle of file forwarding.
As soon as the operation is canceled, conquest service just stops. Everytime it is canceled. Otherwise it is working perfectly.
I updated from conquest 1417 to 1419 without improvement.

Here I join the log of the begining end the ending of the c-move :

Code

22/08/2017 19:48:00 [ISISPHINX] UPACS THREAD 7: STARTED AT: Tue Aug 22 19:48:00 2017
22/08/2017 19:48:00 [ISISPHINX] A-ASSOCIATE-RQ Packet Dump
22/08/2017 19:48:00 [ISISPHINX]  Calling Application Title : "stquewfmLDR     "
22/08/2017 19:48:00 [ISISPHINX]  Called Application Title : "ISISPHINX       "
22/08/2017 19:48:00 [ISISPHINX]  Application Context : "1.2.840.10008.3.1.1.1", PDU length: 32768
22/08/2017 19:48:00 [ISISPHINX]  Number of Proposed Presentation Contexts: 5
22/08/2017 19:48:00 [ISISPHINX]  Presentation Context 0 "1.2.840.10008.5.1.4.1.2.2.2" 1
22/08/2017 19:48:00 [ISISPHINX]  Presentation Context 1 "1.2.840.10008.5.1.4.1.2.1.2" 1
22/08/2017 19:48:00 [ISISPHINX]  Presentation Context 2 "1.2.840.10008.5.1.4.1.2.3.2" 1
22/08/2017 19:48:00 [ISISPHINX]  Presentation Context 3 "1.2.840.10008.1.1" 1
22/08/2017 19:48:00 [ISISPHINX]  Presentation Context 4 "1.2.840.113704.7.0.1.14" 0
22/08/2017 19:48:00 [ISISPHINX] Server Command   := 0021
22/08/2017 19:48:00 [ISISPHINX] Message ID       := 0129
22/08/2017 19:48:00 [ISISPHINX]  C-Move Destination: "stquewfmLDR "
22/08/2017 19:48:00 [ISISPHINX] (QualifyOn) (mapped) IP:192.168.2.200, PORT:2105
22/08/2017 19:48:00 [ISISPHINX] MyStudyRootRetrieveGeneric :: SearchOn
22/08/2017 19:48:00 [ISISPHINX] Query On Image
22/08/2017 19:48:00 [ISISPHINX] Issue Query on Columns: DICOMImages.SOPClassUI, DICOMImages.SOPInstanc, DICOMSeries.SeriesInst, DICOMStudies.StudyInsta,DICOMImages.ObjectFile,DICOMImages.DeviceName
22/08/2017 19:48:00 [ISISPHINX] Values: DICOMStudies.StudyInsta = '1.2.826.0.1.3680043.2.455.30.10.960000.3.1006297' and DICOMSeries.StudyInsta = DICOMStudies.StudyInsta and DICOMImages.SeriesInst = DICOMSeries.SeriesInst
22/08/2017 19:48:00 [ISISPHINX] Tables: DICOMImages, DICOMSeries, DICOMStudies
22/08/2017 19:48:00 [ISISPHINX] Records = 1573
22/08/2017 19:48:00 [ISISPHINX] Number of Images to send: 1573
22/08/2017 19:48:00 [ISISPHINX] MyStudyRootRetrieveGeneric :: RetrieveOn
/*  Skipped Lines
22/08/2017 19:48:08 [ISISPHINX] Sending file : e:\images\SIR138981\1.2.392.200036.9116.2.2047269698.1502859332.11.1270200007.1_0010_000039_1502884339d5e1.dcm
22/08/2017 19:48:08 [ISISPHINX] Image Loaded from Read Ahead Thread, returning TRUE
22/08/2017 19:48:08 [ISISPHINX] [recompress]: recompressed with mode = un (strip=1)
22/08/2017 19:48:08 [ISISPHINX] ReadAheadThread: readahead > 0200
22/08/2017 19:48:08 [ISISPHINX] Retrieve: remote connection dropped after 192 images, 1381 not sent
22/08/2017 19:48:08 [ISISPHINX] C-Move (StudyRoot)
22/08/2017 19:48:08 [ISISPHINX] Server Command   := 0fff
22/08/2017 19:48:08 [ISISPHINX] Message ID       := 0000
22/08/2017 19:48:08 [ISISPHINX] Cancel request
22/08/2017 19:48:08 [ISISPHINX] UPACS THREAD 7: ENDED AT: Tue Aug 22 19:48:08 2017
22/08/2017 19:48:08 [ISISPHINX] UPACS THREAD 7: TOTAL RUNNING TIME: 8 SECONDS
/* Thas is where conquest goes offline

Display More

Any ideas are welcomed ?

PS : I would like to use this first post to also thanks all the conquest team and community for the great work. Using conquest for many years now and can't count all the helps conquest brought to our clinics and by extension their patients.

Sincerely
Thibaut

marcelvanherk · Aug 25th 2017

Hi Thibaut,

is there any chance you can run conquest in a debugger? I assume it crashes and I would need to know the crash address.

Marcel

Tetraib · Aug 28th 2017

Hi Marcel,
Could you detail me the preferred method to run conquest in a debugger ?

marcelvanherk · Aug 28th 2017

Hi,

start a debugger e.g. visual studio express edition. Attach the debugger to dgate(64). exe and then send the c-cancel. The debugger should pop up and show the error location.

More info will be shown if I share the dgate.pdb file, but you can start without.

Marcel

Tetraib · Aug 30th 2017

Here is the debugger result (sorry it's french) :
Exception levée à 0x000000013F59AE7A dans dgate64.exe : 0xC0000005 : Violation d'accès lors de la lecture de l'emplacement 0x0000000001F5BD58.

marcelvanherk · Aug 30th 2017

Great. What is the exact version and OS?

Marcel

marcelvanherk · Sep 4th 2017

Hi,

during a move there are two connections to conquest, the client and the receiver. Do you know which one sends the cancel request. And can you please report the exact version on which you reported the crash? Otherwise I cannot locate the crash address.

Marcel

Tetraib · Sep 19th 2017

Sorry for the delay, I was on vacation and missed the notification,
The os is windows server 2008 R2.
ConQuest DICOM server version 1.4.19. Date of this release: 20170208.
I believe the one who cancel the request is the receiver.

marcelvanherk · Sep 19th 2017

Thanks!

I will have a look if I can locate the crash address and find a fix.

Marcel

marcelvanherk · Sep 19th 2017

Hi,

can you reproduce and send a screenshot what the debugger shows after clinking OK on the error message? That would be helpful.

Marcel

marcelvanherk · Sep 19th 2017

Hi,

here is 64 bits dgate.exe (replace dgate64.exe), do not change name, and its associated debug file. If you place both in the server folder the debugger should show a bit more detail at a crash.

Marcel

marcelvanherk · Sep 20th 2017

Hi,

And running conquest in a high level debug mode may give some more clues too.

Marcel

Tetraib · Oct 4th 2017

Here the screenshot of the debugging :
In Conquest :

In vs Studio :

Hope it helps

marcelvanherk · Oct 6th 2017

Thanks,

this make it much clearer.

Marcel

marcelvanherk · Oct 9th 2017

Hi,

I will give you an updated dgate.exe tonight to test.

regards,

Marcel

marcelvanherk · Oct 9th 2017

Hi Thibaut,

Here is a fix (32 bits dgate with debug information). Can you give it a try? Basically there were two paths where an assocation could be dropped without the read ahead thread being stopped. This code is quite old, but never encountered issues with it. Now it closes the thread and waits for it in both possible paths.

Please test it.

Marcel

marcelvanherk · Oct 13th 2017

Fix released in 1.4.19b

Marcel

Canceled C-Move kill conquest Server

Participate now!

Share