Make ODBC data Source grayed out

  • I am working to setup the DICOM 1.4.19b server software on a Windows PC to act as a storage device for dicom images. In going through the setup the "Make ODBC Connection" button is grayed out. I have installed the drivers for SQLLite since I just went with the default database for the installation. In addition when I select the "Verify Database Installation" button I get the following error "The server is not running properly: association rejected, Probable cause: database is not accessible

  • Just to add a little more context to the issue, what I am looking to do is use the DiCom Server as a routing mechanism. I have a robust PC that I have installed the DiCOM Server software on and I have a drive mapped to out enterprise storage. I would like to use the DiCOM Server as a routing device so we can send images from our imaging modalities directly to the mapped drive using the DiCOM as the send to device from our imaging modalities. Do I really even need a database setup in order to do this

  • I think I am close now, I have reached the point where I am trying to Query / Move from my imaging modality to the DiCom Server I just setup. I queried the modality and am able to see the studies however when I tried to copy to the destination I received the following error "Dicom move error, Remote DiCom error. Do I need to setup the modality to be some type of Send To location. I did get the modality to ping the server

  • Hi,


    any c-move only sends the name of the destination (itself as listed in acrnema.map) to the modality. That name needs to be known to the modality and refer back to the IP and port of conquest.


    Marcel

    Marcel van Herk is developer of the Conquest DICOM server together with Lambert Zijp.

  • Just so I am clear on the last post. I have entered the modality name, ip, and port (104) into the acrnema.map file and also the Dicom Server name, ip address and port (5678). The modality has been setup to query and retrieve.


    Are there any other settings I need to check. Also could the error we are receiving be due to a port being blocked (5678)?

  • When I click the browse database button, I receive the following error message " Access violation at address ..... in Module ConquestDicomServer.exe. I am running the application as an admin so not sure why I would see this message

  • Hi,


    indeed port 5678 could be blocked by a firewall. Note sure why you get an access violation, it is likely that the database is not setup properly. Can you start from scratch in another folder and see what happen?


    Marcel

    Marcel van Herk is developer of the Conquest DICOM server together with Lambert Zijp.

  • I deleted the dicom.ini file and went through the installation process again. It appears the database has been created correctly now since I can verify it, however when I try to retrieve from the modality to the DiCom Server I get a message still stating: DiCom move error, Remote Dicom error.


    If I attempt to push or transfer from the modality to the server at the modality I get a "Data Transfer error" listed at the modality.