SAXParseException in pre archive.

12 views
Skip to first unread message

Brad Jones

unread,
Oct 21, 2025, 2:21:23 PM (7 days ago) Oct 21
to xnat_discussion

Hello, I'm new to DICOM/ XNAT.  I'm using a third party to de-identify the metadata in the DCM files.  1.5% (out of about 5000) of my files are returning the error below when imported into Xnat.  I'm guessing there is something missing in the headers, but I do not know what.

is there any documentation that can tell me what the required DICOM headers are?  or a log file to give me a more detail as to what might be missing?


XNAT has encountered an error with your request:

Exception: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Premature end of file.

If this error continues to occur, please contact your system administrator with information about how to recreate the problem.

Brad Jones

unread,
Oct 23, 2025, 2:51:23 PM (5 days ago) Oct 23
to xnat_discussion

I was able to go into the /data/xnat/prearchive and see that when the xml is built it is 0kb in size.

I deleted it and rebuilt it using the button in the prearchival, and it came back as 0kb again.

I can use the  Download DCMTK Tools - dicom.offis.de  dcm2xml it gives me an xml and I see the headers

I have all of these in the file: 

  • StudyInstanceUID
  • SeriesInstanceUID
  • Modality
  • PatientID
  • StudyDate

    I also the project subject and session in the composite string on 0010,21b0 

    the stack trace I am seeing in the prearchive log is:

    must contain exactly one session
    org.nrg.session.SessionBuilder$NoUniqueSessionException: No session found

    and 

    ust contain exactly one session
    org.nrg.session.SessionBuilder$NoUniqueSessionException: Multiple sessions found: [no session type identified]
Reply all
Reply to author
Forward
0 new messages