Posts by Joelg316

Hi Marcel,

Thanks for the reply. I went into our old server (UBER2) and tried the same thing, and it works.

[UBER2] UPACS THREAD 1148: STARTED AT: Sat Apr 30 11:48:06 2016
[UBER2] Calling Application Title : "UBER2 "
[UBER2] Called Application Title : "UBER2 "
[UBER2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 16384
[UBER2] Presentation Context 0 "1.2.840.10008.5.1.4.1.2.1.2" 1
[UBER2] Presentation Context 1 "1.2.840.10008.5.1.4.1.2.2.2" 1
[UBER2] Presentation Context 2 "1.2.840.10008.5.1.4.1.2.3.2" 1
[UBER2] C-Move Destination: "novapacs "
[UBER2] Number of images to send: 1
[UBER2] Sending file : P:\dicom\conquest\images\W146782\1.2.840.113619.2.134.1762903205.1706.1461934864.30_0001_000003_14619556228e50.dcm
[UBER2] C-Move (PatientRoot)
[UBER2] UPACS THREAD 1148: ENDED AT: Sat Apr 30 11:48:09 2016
[UBER2] UPACS THREAD 1148: TOTAL RUNNING TIME: 3 SECONDS

novapacs is configured to be promiscuous, but maybe they don't allow all incoming c-moves. I'll double check that there isn't an issue on their side. Outside of an issue with novapacs, do you have any other ideas why our old server can c-move, but not the new one? Thanks for your help.

Joel

Hello all,

I am experiencing problems when I try to send images to a remote PACs system. We recently installed Conquest on a new server and copied all the configuration files exactly, except for changing the name of the old server to the new server, which is called CROWN1.

When I try to send an image from Conquest to our PACs system, in the server status, I see that the Calling Application Title is correct, CROWN1, but the Called Application Title is also CROWN1, which is incorrect. I'm not sure why the Called Application Title is CROWN1. I downloaded TestSCU and for some reason that software uses the correct Called Application Title, but when I send directly from Conquest, it uses CROWN1, as you can see below:

Succesful transmit (using TestSCU):

CROWN1] UPACS THREAD 8: STARTED AT: Fri Apr 29 18:47:50 2016
[CROWN1] Calling Application Title : "CROWN1 "
[CROWN1] Called Application Title : "SynapseDicomSCP "
[CROWN1] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 16384
[CROWN1] Presentation Context 0 "1.2.840.10008.5.1.4.1.1.4" 1
[CROWN1] Rewritten file: E:\dicom\images\1234\1.2.840.113619.2.134.1762903205.1717.1461328941.834_0001_000008_14613602330007.dcm
[CROWN1] UPACS THREAD 8: ENDED AT: Fri Apr 29 18:47:50 2016
[CROWN1] UPACS THREAD 8: TOTAL RUNNING TIME: 0 SECONDS
[CROWN1] ExportConverter0.0: forward E:\dicom\images\1234\1.2.840.113619.2.134.1762903205.1717.1461328941.834_0001_000008_14613602330007.dcm to iPACS

Unsuccessful:

[CROWN1]
[CROWN1] UPACS THREAD 3: STARTED AT: Fri Apr 29 18:43:39 2016
[CROWN1] Calling Application Title : "CROWN1 "
[CROWN1] Called Application Title : "CROWN1 "
[CROWN1] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 16384
[CROWN1] Presentation Context 0 "1.2.840.10008.5.1.4.1.2.1.2" 1
[CROWN1] Presentation Context 1 "1.2.840.10008.5.1.4.1.2.2.2" 1
[CROWN1] Presentation Context 2 "1.2.840.10008.5.1.4.1.2.3.2" 1
[CROWN1] C-Move Destination: "novapacs "
[CROWN1] Number of images to send: 21
[CROWN1] Host 'novapacs ' did not accept the connection
[CROWN1] C-Move (PatientRoot)
[CROWN1] UPACS THREAD 3: ENDED AT: Fri Apr 29 18:44:00 2016
[CROWN1] UPACS THREAD 3: TOTAL RUNNING TIME: 21 SECONDS

And you may notice that in the first example I was sending to SynapseDicomSCP and in the second one I was sending to novapacs, but the problem persists no matter which PACs system I send to. I've tested it with both of them using TestSCP and it works for both, and it gives me the same error sending to both from Conquest. Any advice is appreciated! Thanks!