Posts by rickmill98

    I was able to get nightly move option to work now. It's just taking a really long time to move stuff given the size, so I end up having to stop it the next morning before it finishes the move operation. If I don't stop it, the system performs too poorly for users accessing it.


    Is there any way to start the nightly move before 2aM other than command line? I would like to start it at 7pm, after users have gone home for the day.


    Thanks!

    I got the following error last night when trying to start the Nightly Move process. This was on the Maintenance tab in the GUI:


    All functions of this page are optional.
    Making space at night by moving LRU patients to: MAG1
    Amount of MB to move: 431242
    [CONQUESTSRV1] ---------- Start archival operation -----------
    failed selecting patients for nightly moving
    [CONQUESTSRV1] ---------- Start archival operation -----------
    [CONQUESTSRV1] MoveDataToDevice: Nothing to do
    failed nightly moving



    Any ideas on how to fix this? Thanks!

    The bottom of my dicom.ini file now looks like this:


    # Configuration of disk(s) to store images
    MAGDeviceThreshhold = 0
    MAGDeviceFullThreshHold = 30
    IgnoreMAGDeviceThreshold = 0
    MAGDevices = 2
    MAGDevice0 = \\192.168.16.171\ostcxray\conquest\ostc xray\
    MAGDevice1 = \\Ostcnasbackups\XRay Archive\
    NightlyCleanThreshhold = 0
    LRUSort = StudyDate


    How do I input the date into the GUI to start the move? The only field I see in GUI is Cleanup Nightly below (MB): _____ and the input appears to be only for MB ie 500000 is 5MB. Can I put a date in this field instead? There is also Cleanup Disk below (MB): _______ and it appears to want the same input ie MB.


    Thanks!

    Thanks Marcel. When I put the command LRUSort = StudyDate, do I put an actual date in like LRUSort=09/01/2014? Or do I put LRUSort = StudyDate in the ini file and then put the date in the GUI field?


    We are running version 1.4.17alpha, so let me know if I need to upgrade to latest release before doing this. Thanks!

    Is there a way to auto archive all studies over 2 years old? We have a current db that is getting large and slow, so I plan to split it into 2 separate databases so the current images are loaded faster. I'm looking for tips to automate or speed up that process. Current db is ConquestSRV1 and running on mysql. Thanks in advance.

    Ok, found the solution in another post in this forum. Root cause is corrupt image in the db. I upgraded to 1.14 beta and added


    IgnoreOutOfMemoryErrors = 1 to dicom.ini file. Did full regen and it worked this time.


    Keep up the good work on Conquest!


    Regards
    Rick Miller

    Hi Marcel. I did a full regen of the db. It gets about half way thru and then shows this error message.


    [CONQUESTSRV1] [Regen] X:\conquest\OSTC XRAY\MRI\1.2.840.113564.1921681684.20080627112503234530_0001_000001_12145878920872.v2 -SUCCESS
    [CONQUESTSRV1] ***VR:ReAlloc out of memory allocating 1681985024 bytes
    [CONQUESTSRV1] ***A fatal error occurred (out of memory) - closing server



    Any ideas on this?

    Hi, We initially deployed Conquest server with Images stored as DCM. Then about 2 months in, the configuration was changed to V2 (Under configuration, Images are stored on disk as ... setting). Now we are having an issue when we query Conquest that the older DCM images won't show up in the query. We can manually find them in the xray folders by Patient ID, so we know the images are still there, just not showing up in Conquest. Is there an easy way to fix this?


    Many thanks in advance.


    Regards
    Rick Miller

    Ok, finally got this working. I had to change the RAD Server in KPACS to the internal VPN network (10.0.xx). I originally had this setup on the internal NIC of the Conquest Server (192.xx network), which worked fine for queries after VPN was established. On the Conquest side, I had to remove duplicate Known Dicom Provider entries that had same AET, but pointing to different IP addresses (ie AET of Rick for 192.1. xxx IP and 10.xxx VPN addresss). It worked before when I was pushing images from Conquest because I could select the destination (and correct corresponding IP). But when I tried to pull the image using KPACS, it would use the first AET entry in the Conquest Known Providers List (which was internal 192.xx IP). Once I fixed the config and entries, it all started working correctly.


    Thanks again for your help (and for making a really cool dicom server/client setup that is cost effective).


    Regards
    Rick Miller

    Here is Conquest log from a move I tried to do just a few minutes ago. Same issue as before.


    [CONQUESTSRV1] Query On Image
    [CONQUESTSRV1] Issue Query on Columns: DICOMImages.SOPClassUI, DICOMImages.SOPInstanc, DICOMSeries.SeriesDate, DICOMSeries.SeriesTime, DICOMSeries.Modality, DICOMSeries.SeriesDesc, DICOMSeries.BodyPartEx, DICOMSeries.ProtocolNa, DICOMSeries.PatientPos, DICOMSeries.SeriesInst, DICOMSeries.SeriesNumb, DICOMStudies.StudyInsta,DICOMImages.ObjectFile,DICOMImages.DeviceName
    [CONQUESTSRV1] Values: DICOMSeries.SeriesInst = '1.2.840.113564.1921681684.200806030915555465' and DICOMStudies.StudyInsta = '1.2.840.113564.1921681684.200806030915304534' and DICOMSeries.StudyInsta = DICOMStudies.StudyInsta and DICOMImages.SeriesInst = DICOMSeries.SeriesInst
    [CONQUESTSRV1] Tables: DICOMImages, DICOMSeries, DICOMStudies
    [CONQUESTSRV1] Records = 1
    [CONQUESTSRV1] Number of Images to send: 1
    [CONQUESTSRV1] Host 'Rick' did not accept the connection
    [CONQUESTSRV1] C-Move (StudyRoot)
    [CONQUESTSRV1] UPACS THREAD 478: ENDED AT: Tue Jun 03 10:08:41 2008
    [CONQUESTSRV1] UPACS THREAD 478: TOTAL RUNNING TIME: 23 SECONDS
    [CONQUESTSRV1]
    [CONQUESTSRV1] UPACS THREAD 479: STARTED AT: Tue Jun 03 10:08:41 2008
    [CONQUESTSRV1] A-ASSOCIATE-RQ Packet Dump
    [CONQUESTSRV1] Calling Application Title : "Rick"
    [CONQUESTSRV1] Called Application Title : "CONQUESTSRV1 "
    [CONQUESTSRV1] Application Context : "1.2.840.10008.3.1.1.1"
    [CONQUESTSRV1] Number of Proposed Presentation Contexts: 1
    [CONQUESTSRV1] Presentation Context 0 "1.2.840.10008.5.1.4.1.2.2.2"
    [CONQUESTSRV1] Server Command := 0021
    [CONQUESTSRV1] Message ID := 0003
    [CONQUESTSRV1] C-Move Destination: "Rick"
    [CONQUESTSRV1] 0000,0002 28 UI AffectedSOPClassUID "1.2.840.10008.5.1.4.1.2.2.2"
    [CONQUESTSRV1] 0000,0100 2 US CommandField 33
    [CONQUESTSRV1] 0000,0110 2 US MessageID 3
    [CONQUESTSRV1] 0000,0600 4 AE MoveDestination "Rick"
    [CONQUESTSRV1] 0000,0700 2 US Priority 0
    [CONQUESTSRV1] 0000,0800 2 US DataSetType 258
    [CONQUESTSRV1] (QualifyOn) (mapped) IP:10.0.1.7, PORT:104
    [CONQUESTSRV1] MyStudyRootRetrieveGeneric :: SearchOn
    [CONQUESTSRV1] 0008,0021 0 DA SeriesDate (empty)
    [CONQUESTSRV1] 0008,0031 0 TM SeriesTime (empty)
    [CONQUESTSRV1] 0008,0052 6 CS QueryRetrieveLevel "SERIES"
    [CONQUESTSRV1] 0008,0060 0 CS Modality (empty)
    [CONQUESTSRV1] 0008,103e 0 LO SeriesDescription (empty)
    [CONQUESTSRV1] 0018,0015 0 CS BodyPartExamined (empty)
    [CONQUESTSRV1] 0018,1030 0 LO ProtocolName (empty)
    [CONQUESTSRV1] 0018,5100 0 CS PatientPosition (empty)
    [CONQUESTSRV1] 0020,000d 44 UI StudyInstanceUID "1.2.840.113564.1921681684.200806030915304534"
    [CONQUESTSRV1] 0020,000e 44 UI SeriesInstanceUID "1.2.840.113564.1921681684.200806030915557817"
    [CONQUESTSRV1] 0020,0011 0 IS SeriesNumber (empty)
    [CONQUESTSRV1] Query On Image
    [CONQUESTSRV1] Issue Query on Columns: DICOMImages.SOPClassUI, DICOMImages.SOPInstanc, DICOMSeries.SeriesDate, DICOMSeries.SeriesTime, DICOMSeries.Modality, DICOMSeries.SeriesDesc, DICOMSeries.BodyPartEx, DICOMSeries.ProtocolNa, DICOMSeries.PatientPos, DICOMSeries.SeriesInst, DICOMSeries.SeriesNumb, DICOMStudies.StudyInsta,DICOMImages.ObjectFile,DICOMImages.DeviceName
    [CONQUESTSRV1] Values: DICOMSeries.SeriesInst = '1.2.840.113564.1921681684.200806030915557817' and DICOMStudies.StudyInsta = '1.2.840.113564.1921681684.200806030915304534' and DICOMSeries.StudyInsta = DICOMStudies.StudyInsta and DICOMImages.SeriesInst = DICOMSeries.SeriesInst
    [CONQUESTSRV1] Tables: DICOMImages, DICOMSeries, DICOMStudies
    [CONQUESTSRV1] Records = 1
    [CONQUESTSRV1] Number of Images to send: 1
    [CONQUESTSRV1] 0000,0002 18 UI AffectedSOPClassUID "1.2.840.10008.1.1"
    [CONQUESTSRV1] 0000,0100 2 US CommandField 48
    [CONQUESTSRV1] 0000,0110 2 US MessageID 7
    [CONQUESTSRV1] 0000,0800 2 US DataSetType 257
    [CONQUESTSRV1] 9999,0400 6 UN "silent"
    [CONQUESTSRV1] 0000,0002 18 UI AffectedSOPClassUID "1.2.840.10008.1.1"
    [CONQUESTSRV1] 0000,0100 2 US CommandField 48
    [CONQUESTSRV1] 0000,0110 2 US MessageID 7
    [CONQUESTSRV1] 0000,0800 2 US DataSetType 257
    [CONQUESTSRV1] 9999,0400 6 UN "silent"
    [CONQUESTSRV1] Host 'Rick' did not accept the connection
    [CONQUESTSRV1] C-Move (StudyRoot)
    [CONQUESTSRV1] UPACS THREAD 479: ENDED AT: Tue Jun 03 10:09:05 2008
    [CONQUESTSRV1] UPACS THREAD 479: TOTAL RUNNING TIME: 24 SECONDS


    Regards
    Rick Miller

    I verified AET is exactly the same in Conquest as in Kpacs. Still having same issue. Can push an image, but can't retrieve one.


    AET on KPACS is Rick. Here is the detailed log file of an unsuccessful attempt.


    \par \cf1 5/29/2008 8:40:56 PM ThreadID[224] : Retrieving images from CONQUESTSRV1 started
    \par \cf2 *******************************************************
    \par [224] >> : c-move request for SeriesInstanceUID: 1.2.840.113564.1921681684.20080529113943359420 initated
    \par \cf4 [DICOM SCU] >> : Connected to: 192.168.16.2:5678
    \par [DICOM SCU] >> : Item Type: 2
    \par [DICOM SCU] >> : Association Accept::ReadDynamic
    \par [DICOM SCU] >> : Presentation Context Accept, Transfer Syntax: 1.2.840.10008.1.2
    \par [DICOM SCU] >> : rick >> CONQUESTSRV1
    \par [DICOM SCU] >> : (0000,0000), 4,\tab UL, "88" - Group Length
    \par [DICOM SCU] >> : (0000,0002), 28,\tab UI, "1.2.840.10008.5.1.4.1.2.2.2" - Affected SOP Class UID
    \par [DICOM SCU] >> : (0000,0100), 2,\tab US, "33" - Command Field
    \par [DICOM SCU] >> : (0000,0110), 2,\tab US, "3" - Message ID
    \par [DICOM SCU] >> : (0000,0600), 4,\tab AE, "rick" - Move Destination
    \par [DICOM SCU] >> : (0000,0700), 2,\tab US, "0" - Priority
    \par [DICOM SCU] >> : (0000,0800), 2,\tab US, "258" - Data Set Type
    \par [DICOM SCU] >> :
    \par [DICOM SCU] >> : rick >> CONQUESTSRV1
    \par [DICOM SCU] >> : (0008,0021), 0,\tab DA, "" - Series Date
    \par [DICOM SCU] >> : (0008,0031), 0,\tab TM, "" - Series Time
    \par [DICOM SCU] >> : (0008,0052), 6,\tab CS, "SERIES" - Query/Retrieve Level
    \par [DICOM SCU] >> : (0008,0060), 0,\tab CS, "" - Modality
    \par [DICOM SCU] >> : (0008,103E), 0,\tab LO, "" - Series Description
    \par [DICOM SCU] >> : (0018,0015), 0,\tab CS, "" - Body Part Examined
    \par [DICOM SCU] >> : (0018,1030), 0,\tab LO, "" - Protocol Name
    \par [DICOM SCU] >> : (0018,5100), 0,\tab CS, "" - Patient Position
    \par [DICOM SCU] >> : (0020,000D), 46,\tab UI, "1.2.840.113564.1921681684.20080529113921765390" - Study Instance UID
    \par [DICOM SCU] >> : (0020,000E), 46,\tab UI, "1.2.840.113564.1921681684.20080529113943359420" - Series Instance UID
    \par [DICOM SCU] >> : (0020,0011), 0,\tab IS, "" - Series Number
    \par [DICOM SCU] >> :
    \par [DICOM SCU] >> : rick << CONQUESTSRV1
    \par [DICOM SCU] >> : (0000,0000), 4,\tab UL, "116" - Group Length
    \par [DICOM SCU] >> : (0000,0002), 28,\tab UI, "1.2.840.10008.5.1.4.1.2.2.2" - Affected SOP Class UID
    \par [DICOM SCU] >> : (0000,0100), 2,\tab US, "32801" - Command Field
    \par [DICOM SCU] >> : (0000,0120), 2,\tab US, "3" - Message ID Being Responded To
    \par [DICOM SCU] >> : (0000,0800), 2,\tab US, "257" - Data Set Type
    \par [DICOM SCU] >> : (0000,0900), 2,\tab US, "49157" - Status
    \par [DICOM SCU] >> : (0000,1020), 2,\tab US, "0" - Number of Remaining Sub-Operations
    \par [DICOM SCU] >> : (0000,1021), 2,\tab US, "0" - Number of Completed Sub-Operations
    \par [DICOM SCU] >> : (0000,1022), 2,\tab US, "0" - Number of Failed Sub-Operations
    \par [DICOM SCU] >> : (0000,1023), 2,\tab US, "0" - Number of Warning Sub-Operations
    \par [DICOM SCU] >> :
    \par \cf3 [224] >> : Error: move failed for JAMES, DANNY , Study: , Sequence: 1
    \par \cf2 *******************************************************
    \par \cf3 5/29/2008 8:41:24 PM ThreadID[224] : Closed.
    \par Task processed with errors
    \par \cf2 *******************************************************
    \par \cf3 [TdView Class] >> : EXCEPTION caught in OnFilename method
    \par [TdView Class] >> : Class name: EInvalidOperation message: Scrollbar property out of range
    \par \cf0
    \par }

    Ok, I verified that I get the error trying to push an image from Conquest out to Kpacs client. I was able to push an image from conquest to Kpacs by adding a connection to Conquest under "known dicom providers" for the VPN address. But I still have the same problem on the kpacs side trying to view the images. Can I force kpacs to use a specific path?


    Or is there a specific VPN application I can use to easily solve this issue? I'm using Microsoft VPN that comes with Windows 2000 Server currently. I downloaded Himachi and I'm trying it out, but not having any luck so far. Anything else I can try to get this working?


    Thanks again.
    Regards
    Rick Miller

    Hi. I'm using Conquest as a DICOM server and KPacs on the client side. It works great in local network, but trying to setup remote access for Dr's to view images. I installed Kpacs on remote client and established VPN. I'm able to queary the Conquest db and select patients. However, when I try to view the images, its a solid black screen. Any ideas on how to view the images locally?


    Thanks in advance for your help.


    Regards
    Rick Miller