Hi I am using the Dicom Networking, Query and Retrieve option to access a Visbion PACS system. I am able to retrieve the DICOM using the ID and it says Retrieve Process finished, however it then does not appear in my show dicom database, nor does it appear in the destination database location. Can anyone help with this, I have checked my firewall and re-downloaded Slicer. A colleague has no issues on her system which is set up the same. Many thanks Sandie
Thanks for the report. Can you also confirm that the same version of Slicer is used in both cases ?
Hi Jean Christophe, my colleague downloaded the latest 5.8.1 release on her Mac, and it worked fine. I’m using Windows 11 and it initially worked with version 5.6.2. to which I initially managed to download one DICOM from the PACS system using DICOM networking, but all subsequent attempts with DICOM IDs reached the point shown in the screenshot and then failed to appear in the DICOM database. I also tried version 5.8.1, but the same issue persists. This is urgent for my PhD project as the PACS system will be replaced by Petcloud next week. I’ve been desperately trying to download all the DICOMs I need before then, but it keeps failing. I’m with Cambridge University.
my colleague downloaded the latest 5.8.1 release on her Mac, and it worked fine […] This is urgent for my PhD project as the PACS system will be replaced by Petcloud next week
Waiting this is sorted out, you may consider copying the local database directory already available on your colleague workstation onto your own workstation and locally importing the DICOM series from it.
In the interim, would that be a workable solution ?
My colleague is in a different part of the country and the dicoms are currently being transferred to the new cloud platform, however, I think I may have resolved the issue, although it takes along time to download and quite often crashes, before reaching to the dicom database. I will keep trying. Are there any others with issues, do you have a any debugging methods. 
Note that DICOM DIMSE, the standard way of communicating with PACS is meant to be a local area network protocol, so using it to access a remote cloud server can lead to slow performance or timeouts. If possible you should try to use the newer DICOMweb standard, which is designed for this use case.
Note that under the hood Slicer uses DCMTK, which offers some useful command line options that can probably set longer timeouts that could improve the robustness of the transfer.
The new DICOM browser (that you can actuvate using the dropdown menu of the “Show DICOM database” button has much more advanced and more robust DICOM query/retrieve implementation.
Is your computer and the PACS on the same local network? What protocol does the server support for retrieve: C-GET or C-MOVE? Is your computer registered as known host in the PACS?