Error starting conquest with large MAG device mapped drive with many dicom images

  • Hi, Marcel,


    When I start conquest with my magdevice point to S3 mapped drive('Z') I get the next error on start, and next, conquest seems work normally.

    # Configuration of disk(s) to store images

    MAGDeviceFullThreshHold = 100

    MAGDevices = 1

    MAGDevice0 = Z:\dicomortoc\ ---> very large bucket with 2.6TB

    Here I get the error showing in the picture attached below.


    If I use:

    # Configuration of disk(s) to store images

    MAGDeviceFullThreshHold = 100

    MAGDevices = 2

    MAGDevice0 = Z:\dicomimages\ ---> Here I have about 30MB of dicom images in the mapped drive

    MAGDevice1 = Z:\dicomortoc\ ---> very large bucket with 2.6TB dicom images in the mapped drive

    then, No error occur


    If I use:

    # Configuration of disk(s) to store images

    MAGDeviceFullThreshHold = 100

    MAGDevices = 2

    MAGDevice0 = D:\data0\ ---> local drive not mapped

    MAGDevice1 = Z:\dicomortoc\ ---> very large bucket with 2.6TB dicom images

    No error occur


    Only to you know, aws S3 storage has no size limit to save images.


    I´m not running conquest as NT service. I am running as normal app in admin account.

    Can you help to find the error?







Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!