[TEST] ***No valid presentation contexts/transfer syntax found in 2 candidates
[TEST] ***In 2 presentation contexts
[TEST] ***#Possible transfer syntaxes: 1
[TEST] *** multiplex: connection terminated
How can I deal with this problem?
[TEST] ***No valid presentation contexts/transfer syntax found in 2 candidates
[TEST] ***In 2 presentation contexts
[TEST] ***#Possible transfer syntaxes: 1
[TEST] *** multiplex: connection terminated
How can I deal with this problem?
Hi,
try to enable jpeg support? This gives conquest more transfer syntaxes.
Marcel
Hi all!
I'm having the same issue with adding some dicom files to the incoming folder. Some files pass through, but for the vast majority I end up with
Tue Aug 25 11:30:56 2020 ***No valid presentation contexts/transfer syntax found in 0 candidates Tue Aug 25 11:30:56 2020 ***In 0 presentation contexts Tue Aug 25 11:30:56 2020 ***#Possible transfer syntaxes: 13 Tue Aug 25 11:30:56 2020 *** multiplex: connection terminated
Is it commected with jpeg support aswell? How do I enable that?
part of the dicom.ini which might be related is
# Configure server
ImportExportDragAndDrop = 1
ZipTime = 05:
UIDPrefix = 99999.99999
EnableComputedFields = 1
FileNameSyntax = 4
# Configuration of compression for incoming images and archival
DroppedFileCompression = un
IncomingCompression = un
ArchiveCompression = as
Best regards,
Niko
Hi,
I believe these error messages are not associated with processing of the incoming folder which does not utilise DICOM transfer at all. What do you exactly do?
Marcel
Hi,
I'm uploading new dicom files to the Conquest server (with anonymization) by adding them to the 'Incoming" folder. The files were previously anonymized on another server aswell.
Best regards,
Nikolay
Oh, I'm sorry, maybe I'm asking in the wrong thread? I was just googling for the same errors and ended up here...
No thread is OK.
But the error messages you shared cannot come from the processing of the incoming folder. Can you show a more complete excerpt from the log?
Marcel
Well, actually I was trying to add a ton of dcm files packed in the large (around 20 GB each) archives on my server. After copying them as-is in the 'incomng' folder, most of them didn't make it to the server and stayed there after a long time (days). I unzipped the archives and added them on the server by small portions, and everything seems to be OK, i got nothing new in DicomTrouble.log besides this
Thu Aug 27 19:35:50 2020 Inconsistent StudyTime in DICOMStudies: PatientID = '4195368894.0' StudyInsta = '99999.99999.7.1598531727.6573', Old='165316.000', New='171642.000'
Thu Aug 27 19:36:16 2020 Inconsistent StudyTime in DICOMStudies: PatientID = '4195368894.0' StudyInsta = '99999.99999.7.1598531727.6573', Old='171642.000', New='165316.000'
Thu Aug 27 19:40:31 2020 SaveToDisk: *** warning: cannot write NKI compressed in dcm format, decompressing: /storage1/conquest_storage/data/567779206_0/99999.99999.7.1598531628.6512_9000_000001_15985320319d14.dcm
and the same kind of errors I mentioned above. Maybe the files just stayed in the queue for too long. Sorry for bothering you.
Best regards,
Niko
Hm, maybe that makes more sense.
The warnings seems normal, just small inconsistencies in the headers. The last warning suggests yoy try to use NKI compression which is maybe not a good idea, it is not standard dicom.
Marcel
Hello
I use DICOMSERVER150b and I have an image receiving error of a ultrasound.
[CONQUESTSRV1] A-ASSOCIATE-RQ Packet Dump
[CONQUESTSRV1] Calling Application Title : "Voluson "
[CONQUESTSRV1] Called Application Title : "CONQUESTSRV1 "
[CONQUESTSRV1] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 28672
[CONQUESTSRV1] Number of Proposed Presentation Contexts: 6
[CONQUESTSRV1] Presentation Context 0 "1.2.840.10008.5.1.4.1.1.6.1" 1
[CONQUESTSRV1] Presentation Context 1 "1.2.840.10008.5.1.4.1.1.3.1" 1
[CONQUESTSRV1] Presentation Context 2 "1.2.840.10008.1.1" 1
[CONQUESTSRV1] Presentation Context 3 "1.2.840.10008.5.1.4.1.1.6" 1
[CONQUESTSRV1] Presentation Context 4 "1.2.840.10008.5.1.4.1.1.7" 1
[CONQUESTSRV1] Presentation Context 5 "1.2.840.10008.5.1.4.1.1.6.2" 1
[CONQUESTSRV1] Server Command := 0001
[CONQUESTSRV1] Message ID := 003b
[CONQUESTSRV1] FreeStore Left 100731 on f:\
[CONQUESTSRV1] Written file: f:\voluson\dicom_server\data\8001198657\1.2.276.0.26.1.1.1.2.2021.260.31579.3402772_0001_000021_16287579590027.dcm
[CONQUESTSRV1] UPACS THREAD 146: ENDED AT: Thu Aug 12 10:45:59 2021
[CONQUESTSRV1] UPACS THREAD 146: TOTAL RUNNING TIME: 0 SECONDS
[CONQUESTSRV1] ***No valid presentation contexts/transfer syntax found in 3 candidates
[CONQUESTSRV1] ***In 3 presentation contexts
[CONQUESTSRV1] ***#Possible transfer syntaxes: 1
[CONQUESTSRV1] *** multiplex: connection terminated
The other ultrasounds work properly.
What can I do ?
thank you
Hi Alain,
the log up to *** seems complete and without error, but normally, I expect information "[CONQUESTSRV1] Presentation Context" information before an error. Can you try again?
Marcel
Don’t have an account yet? Register yourself now and be a part of our community!