PacsOne Server

Wed Nov 25 15:48:33 2020 INFO - <3> Sending P-DATA-TF PDU Wed Nov 25 15:48:33 2020 ERROR - CPixelData: Failed allocate 1051034400 bytes This error means PacsOne could not allocated the required amount of physical memory during the Dicom transfer syntax conversion to JPEG-LS compression when forward...

You can search by Modality in the "Search->Search By Study/Series->Search by Modality" menu. For example, if you are looking for MG studies, you can click on the "Search->Search By Study" menu and enter "MG" as the Modality type then click on the <Search By Modality> button.

You can try downloading that single study for Patient B into a zip file, then import from the content of the extracted zip file from another Dicom application, e.g., a workstation or another instance of PacsOne Server, etc., change the Patient ID from there then send that study back to PacsOne Serve...

For newer versions of PacsOne Server such as 6.7.2, PacsOne is registered as a SYSTEMD service so you should use the following command to start PacsOne Server service:

# systemctl start pacsone

You should definitely NOT delete those Dicom image files externally without involving PacsOne Server, because doing so would result in discrepancies in the PacsOne Server database as the meta-records stored in the database would be linked to some non-existant files. The correct way to make room for ...

If the conflicts in Patient Name for the duplicate Patient ID are of no concern, and you are Ok with overwriting existing patient records with newly received Patient Name (regardless of what the new names are), then we can create and send you a PHP script to remove all the duplicate Patient IDs and ...

This is confirmed to be a bug in version 6.6.2 of PacsOne Server, and we'll fix it in the next release (6.6.3) to be released soon.

In the meanwhile, you can download the patched "php/wado.php" script from our website below:

http://www.pacsone.net/Patch662.zip

This is confirmed to be a bug in PacsOne Server and it's traced to the " Preferred Transfer Syntax " setting for the destination AE, if it's ever configured then reset to " None ", the setting stored in the " Dicom AE " table will become empty ("") but not NULL. So when the Dicom server component of...

Can you try the same test with the latest version 6.5.3 of PacsOne Server? There are some recent changes in this area (Dicom transfer syntax negotiation) which may have addressed the issue you just reported.

So to summerize your description of the problem, the original transfer syntax of a Dicom image is "1.2.840.10008.1.2.4.51", but when version 6.5.2 of PacsOne Server sends this image to a destination AE, it proposes the default transfer syntax (Implicit VR Little-Endian) "1.2.840.10008.1.2" first on ...

It'd much easier for you to apply for a new trial license without the default limit by sending your current trial license (" license.dat ") under the directory where PacsOne is installed, along with the output text of the following command run from a local shell on your server to: mailto:pacsone@pac...

Your existing PacsOne Server license will NOT work on the new server with different hardware configurations, and that's why you'll need a replacment license for your new server if there're more than 1,000,000 images in the existing PacsOne Server database, since that's the maximum number of images s...

We have less than 30K images to import. The problem appears after database import, as is there were a control between licence.dat file and something stored inside the database. Before importing database, we are able to modify the local storage folder and make an import of some images without errors...

1. Can you run the following command from a local shell on the new CentOS server to see which User/Group context PacsOne Server is currently running as? # ps -ef|grep PacsOne 2. Can you send us your current configuration file for PacsOne Server? It's the " ${AeTitle}.ini " file under the directory w...

How is the radiologist's workstation connected with the host where PacsOne Server is running? e.g., via LAN, WAN, or VPN etc? If they are connected via a LAN, then the timeouts were most likely caused by network congestions within your LAN and increasing the timeout values will not help. If this is ...