Internal error pop-up when importing DICOM data


Internal Error

I am currently trying to import a DICOM file into the program through “Import DICOM files from directory”. Once I have located the file and clicked “Import” the above image appears. This is my first time using the software. Any help is appreciated.


Here are couple of possible common issues:

  • Can you check the folder chosen as location for your DICOM database is writeable?
  • Can you import some public DICOM dataset that is known to work? (for example, you can try importing the files from this directory and see if you still have the crash)
  • Can you try applying DICOMPatcher to your DICOM dataset before trying to import it?

A post was split to a new topic: DICOM import can be attempted before creating database

Please try with latest Slicer Preview Release and let us know if you still encounter any issues.

Hi Andras,

Thank you for your reply and suggestion. I downloaded the Preview Release and dragged the folder in, but nothing appears. It also says no valid DICOM database found in folder.

Go to DICOM module and click “Create new database” before attempting to import anything.

I think this will come up more and more as that message is really quite obscure. I still propose to disable out the import tab until database initialized (or auto create the database first time DICOM module is run).

1 Like

I’ve clicked “Create new database” but nothing else happens when I try to import.

You can find messages about why file s are not imported in the application log (menu: Help / Report a bug). Could you upload it somewhere and post the link here?

I’ve implemented automatic creation now: if no valid database is available when user drag-and-drops a folder or clicks the import button then a new database is created with default settings. If it fails (e.g., because Slicer cannot find a writeable folder) then an error message is displayed and the user is instructed to resolve the error using options shown in DICOM browser. This will be available in Slicer Preview Releases from tomorrow.


Hi All,

Thank you for your replies and suggestions. I do have another one:

So I downloaded 3D Slicer onto two other workstations to see if it was going to be a recurring problem. When I drag-and-drop the files in, the images load fine (the DICOM browser window displays the correct BodyPartExamined - which for me is Abd; unlike previously where it would say HeadNeck for the same data set). Are there any suggestions as to why this is and how it can be fixed? (I can post this separately if need be)

Thank you and your help is much appreciated.

From this much information we cannot even guess what behavior you see on your computers and why.

If you find that on any computer the latest Slicer Preview Release does not load any DICOM data correctly then send us anonymized/animal/phantom sample data (preferred) or at least send the application log of DICOM import and loading (menu: Help / Report a bug).

[DEBUG][Qt] 05.03.2020 16:27:55 [] (unknown:0) - Session start time …: 2020-03-05 16:27:55
[DEBUG][Qt] 05.03.2020 16:27:55 [] (unknown:0) - Slicer version …: 4.11.0-2020-03-01 (revision 28798) win-amd64 - installed release
[DEBUG][Qt] 05.03.2020 16:27:55 [] (unknown:0) - Operating system …: Windows / 7 / (Build 7601, Code Page 1252) - 64-bit
[DEBUG][Qt] 05.03.2020 16:27:55 [] (unknown:0) - Memory …: 8103 MB physical, 16205 MB virtual
[DEBUG][Qt] 05.03.2020 16:27:55 [] (unknown:0) - CPU …: GenuineIntel , 4 cores, 4 logical processors
[DEBUG][Qt] 05.03.2020 16:27:55 [] (unknown:0) - VTK configuration …: OpenGL2 rendering, TBB threading
[DEBUG][Qt] 05.03.2020 16:27:55 [] (unknown:0) - Qt configuration …: version 5.10.1, with SSL, requested OpenGL 3.2 (compatibility profile)
[DEBUG][Qt] 05.03.2020 16:27:55 [] (unknown:0) - Developer mode enabled …: no
[DEBUG][Qt] 05.03.2020 16:27:55 [] (unknown:0) - Prefer executable CLI …: yes
[DEBUG][Qt] 05.03.2020 16:27:55 [] (unknown:0) - Application path …: C:/Users/z3461313/AppData/Local/NA-MIC/Slicer 4.11.0-2020-03-01/bin
[DEBUG][Qt] 05.03.2020 16:27:55 [] (unknown:0) - Additional module paths …: (none)
[DEBUG][Python] 05.03.2020 16:28:00 [Python] (C:\Users\z3461313\AppData\Local\NA-MIC\Slicer 4.11.0-2020-03-01\lib\Slicer-4.11\qt-scripted-modules\SubjectHierarchyPlugins\ - Scripted subject hierarchy plugin registered: Annotations
[DEBUG][Python] 05.03.2020 16:28:01 [Python] (C:\Users\z3461313\AppData\Local\NA-MIC\Slicer 4.11.0-2020-03-01\lib\Slicer-4.11\qt-scripted-modules\SubjectHierarchyPlugins\ - Scripted subject hierarchy plugin registered: SegmentEditor
[DEBUG][Python] 05.03.2020 16:28:01 [Python] (C:\Users\z3461313\AppData\Local\NA-MIC\Slicer 4.11.0-2020-03-01\lib\Slicer-4.11\qt-scripted-modules\SubjectHierarchyPlugins\ - Scripted subject hierarchy plugin registered: SegmentStatistics
[DEBUG][Qt] 05.03.2020 16:28:01 [] (unknown:0) - Switch to module: “Welcome”
[DEBUG][Qt] 05.03.2020 16:28:24 [] (unknown:0) - Switch to module: “DICOM”
[CRITICAL][Stream] 05.03.2020 16:28:24 [] (unknown:0) - Database folder does not contain ctkDICOM.sql file: //$/z3461313/SlicerDICOMDatabase_8
[WARNING][Qt] 05.03.2020 16:28:25 [] (unknown:0) - QSqlQuery::prepare: database not open
[DEBUG][Qt] 05.03.2020 16:28:25 [] (unknown:0) - SQL failed
Bad SQL:
[DEBUG][Qt] 05.03.2020 16:28:25 [] (unknown:0) - Error text: No query Unable to fetch row

It seems that the database could not be created at the default location, because it was a virtual/network drive. Change the database location to a local folder that your user has write access to. It can even be a folder used for temporary files.

If you download today’s Slicer Preview Release then you should get an informative error popup about what is wrong and what you should do to fix it.