Thanks Marcel. We use PostgreSQL. We will test PostgreSQL mirroring and let you know.
Our use case actually requires same filename as databases will grow differently. One with all online MAG0 other will have both online MAG0 and MAG1 (as remote node)
Best Regards,
Haluk
Hello,
2 Conquests are fed with same identical images but they create different object file names for same image in different DB (looks like adding access time integer plus a count). Is there a way to control and tell Conquest to use same object file name for the same image when run two different instances with different databases.
Our use case will be like that. We want to change an image location from MAG0 to MAG1 in one Conquest and delete image at a certain time and map MAG1 to other Conquest to retrieve the images.
As 2 Conquests create deferent object file name we were not successful. Any help appreciated.
Best Regards,
Haluk Celikel
Hi Marcel,
Sorry for late reply. Actually we have identical viewer configuration with another PACS and don't have the time out problem. We have seen new 64 PDU exe in another post and tested with the new exe below.
"http://ingenium.home.xs4all.nl/dicomser ... u32768.exe
it has a hardcoded pdu size of 32768 instead of 16384. Curious what it will bring."
This time we get the error below;
BETA] UPACS THREAD 89: STARTED AT: Wed Aug 3 11:50:50 2016
[BETA] Records = 1
[BETA] Number of Images to send: 1
[BETA] MyStudyRootRetrieveGeneric :: RetrieveOn
[BETA] ReadAheadThread: readahead > 0000
[BETA] RetrieveOn: givenout < 0000
[BETA] Sending file : C:\imageRAD\BETA\Data\31181097336\1.3.12.2.1107.5.5.2.203411.30000016022606545865600000020_0001_000025_14702138280000.dcm
[BETA] Image Loaded from Read Ahead Thread, returning TRUE
[BETA] Protocol error 0 in PDU:Read
[BETA] Retrieve: remote connection dropped after 0 images, 1 not sent
[BETA] C-Move (StudyRoot)
[BETA] UPACS THREAD 89: ENDED AT: Wed Aug 3 11:50:56 2016
[BETA] UPACS THREAD 89: TOTAL RUNNING TIME: 6 SECONDS
Any thoughts on "Protocol error 0 in PDU:Read"
Best regards,
Haluk Celikel
Hi,
This is what the (BB4DC2) Conquest log shows when accessing a MultiFrame US image with our viewer (RESMD).
We are able to view anything else with this configuration.
When we use a different PACS with the same viewer, we can display MF images.
Any help appreciated.
Haluk
[BB4DC2] UPACS THREAD 632: STARTED AT: Tue Jun 14 16:21:19 2016
[BB4DC2] A-ASSOCIATE-RQ Packet Dump
[BB4DC2] Calling Application Title : "RESMD "
[BB4DC2] Called Application Title : "BB4DC2 "
[BB4DC2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 102400
[BB4DC2] Number of Proposed Presentation Contexts: 128
[BB4DC2] Presentation Context 0 "1.2.840.10008.5.1.4.1.2.1.1" 1
[BB4DC2] Queried item 0008 0005 is not in the database
[BB4DC2] Queried item 0008 1060 is not in the database
[BB4DC2] Queried item 0010 0021 is not in the database
[BB4DC2] Issue Query on Columns: DICOMStudies.StudyDate, DICOMStudies.StudyTime, DICOMStudies.AccessionN, DICOMStudies.StudyModal, DICOMStudies.ReferPhysi, DICOMStudies.StudyDescr, DICOMStudies.PatientNam, DICOMStudies.PatientID, DICOMStudies.PatientBir, DICOMStudies.PatientSex, DICOMStudies.StudyInsta, DICOMStudies.StudyID
[BB4DC2] Values: DICOMStudies.StudyInsta = E'1.2.792.0.35000001.41418'
[BB4DC2] Issue Query on Columns: COUNT(1)
... (cleared patient info)
[BB4DC2] Query On Image
[BB4DC2] Issue Query on Columns: COUNT(1)
... (cleared patient info)
[BB4DC2] ReadAheadThread: readahead > 0000
[BB4DC2] RetrieveOn: givenout < 0000
[BB4DC2] Sending file : E:\conquest2\data\22136131526\1.3.12.2.1107.5.5.2.203411.30000016061411272281200000000_0002_000001_14659102660585.dcm
[BB4DC2] Image Loaded from Read Ahead Thread, returning TRUE
[BB4DC2] Retrieve: remote connection dropped after 0 images, 1 not sent
[BB4DC2] C-Move (StudyRoot)
[BB4DC2] UPACS THREAD 634: ENDED AT: Tue Jun 14 16:21:22 2016
[BB4DC2] UPACS THREAD 634: TOTAL RUNNING TIME: 3 SECONDS
