Troubleshooting
Image conversions to Apteryx require an XVHost Push in order to upload the converted images from the client's machine to their Apteryx site. This upload should typically be done concurrently with the conversion, except for cases of high resource usage, and 3D images.
** If you are converting 3D images, DO NOT start XVHost Push until following steps in the 3D Images section of this OneNote.
-
Obtaining Apteryx Site Certs
Confirm client's Apteryx URL (they should be logged in to their Apteryx site on the server). The URL should be the same as found in the conversion Zendesk ticket.
Search for the URL in the Apteryx Sites Dashboard. Office name should match office name in ticket. If so, click URL.
Click Site Locations and compare Name, Phone, Address fields to same fields in Zendesk ticket. These should all be very similar if not the same.
-
Go back to the site's landing page and click Download Cetificates. Input URL then click confirm. Certs should download to your default directory.
Move certificates to a different location on your PC if needed for easier access.
-
Setting up Push Loop
In LogMeIn File Manager, transfer cert zip from your PC to the \converter\XVHost folder
Unzip certs to \converter\xvhost folder
Copy the path of the .pfx file (hold shift key when right-clicking .pfx file, choose copy as path)
In the XVHost folder, right click the push-delloop.bat > edit
Paste .pfx file path after cert (retain quotes around path)
Paste subdomain of Apteryx site after dicom.Apteryx.net:2762/
Save file
-
Running Push Loop
Search bar (windows key + Q) > cmd > run as Administrator
Navigate to the \converter\xvhost folder
Run push-delloop.bat
Momentarily, images should begin pushing. Message in command prompt window will say something like "1 of ### - success"
Window will say "No DICOM Images Found" if there are no images in the Apteryx-Images folder
Once the conversion has completed and there are no images left in the Apteryx-Images folder, the push is complete.
Troubleshooting
XVHost Taking Up Space
Association Rejected
Sequence Contains No Elements
System.Exception
Files Stuck in Images Folder
32-bit Windows Error
Slow Connections/Time-outs
Conversion Percentage
XVHost Taking Up Space
If XVHost crashes continuously, it will create a bunch of .dmp files in the XVHost folder which can take up a lot of space and cause the command to delete the Apteryx-stored contents to not work.
You can remove the .dmp files from the XVHost folder and run the following command line arguments manually to empty the Apteryx-stored folder:
dir /b ..\Apteryx-stored >> ..\stored-UID-list.txt
NOTE: Confirm the Stored-UID-list.txt file was actually written to and contains some of the UIDs in the Apteryx-stored folder before proceeding to the next command.
del /q ..\Apteryx-stored\*
Association Rejected
DICOM files that fail to upload with error "Failed: Association Rejected" or "Missing SOP Class UID"
Open some of these files in DicomViewer, and see if the SOP Class UID tag is present.
If SOP Class UID is missing for these files, this tag will need to be added:
Install Sante DICOM Editor
Launch Sante DICOM Editor
Go to File > Batch > Modify DICOM Files
Enter the path to the Apteryx-Images folder where the files that failed to upload are stored.
Check the Modify box, and check Insert tag if not exists
-
Click Create New Template
Click Insert Tag…
-
Enter the DICOM tag info for SOP Class UID, or click From List… to select it manually:
-
Enter the new value for the SOP Class UID to be assigned to all files. The correct SOP Class UID may not be the same for all files. Here are some example:
Intraoral X-ray (IO modality): 1.2.840.10008.5.1.4.1.1.1.3
-
3D/CT file (CT modality): 1.2.840.10008.5.1.4.1.1.2
These are typically large files over 30MB, and would need to be updated separately from the smaller files.
Generic CR modality: 1.2.840.10008.5.1.4.1.1.1
-
In this example, all files will be set to Intraoral X-ray SOP Class UID:
Click OK on both windows, and you will be prompted to save these settings to a "Template.sdt" file. Save this file.
Back in the Batch Modify window, under Modify, click Select Template . Select the path to the template sdt file that was saved above.
-
Click the Process button.
-
The tool will create a new set of DICOM files in the same directory, with _mod added to the filename.
Move all the old DICOM files to a backup folder, leaving only the _mod files in the directory to be uploaded.
Run xvhost push command to upload the _mod DICOM files.
Sequence Contains No Elements
Most likely a DICOM tag is empty, or a DICOM sequence is missing some tags.
Example:
The sample DICOM file on the left defines an "Anatomic Region Sequence", but then it is missing the Code Value, Coding Scheme Designator, Code Meaning tags.
Resolution: These tags would either need to be manually added (if the correct value is known), or the customer would need to be notified that these files could not be imported due to missing anatomic information.
System.Exception
Error: Exception of type 'System.Exception' was thrown.
Try opening these files in DicomViewer, and go to View Image to confirm that the image displays successfully.
Most likely the image format is not supported. It may be possible to use the Image Importer in XVCapture to import these files instead.
Files Stuck in Images Folder
Issue: Files push with result "Success", but they do not get moved from the Images folder to the Stored folder.
Cause 1: Windows permissions prevent the file from being moved to the Stored folder.
Fix: Take ownership of all files and subfolders within the converter directory and subfolders. Then change permission on all files and subfolders in the converter directory to Full Control for Everyone.
Fix 2: Alternatively, run the push completely at least 3 times to make sure all files have pushed successfully.
Cause 2: files with the same name already exist in the Stored folder, so the move fails. In this case nothing needs to be done.
Missing SOP Class UID
See instructions under related error: Association Rejected
32-bit Windows Error
Error: Xvhost.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher.
Cause: XVHost needs to be run from a 64-bit version of Windows, not 32-bit.
Resolution: Contact the customer and request to connect to a newer PC in the office (Windows 10) which will most likely be 64-bit. Run the xvhost upload from that PC, while still running the conversion from the server.
Slow Connections/Time-outs
For customers with slow internet connections, or issues with timeouts, while running the normal xvhost push command, add this parameter at the end:
one-at-a-time
Original command example:
xvhost push "D:\converter\Apteryx-Conversion\Images" to dicoms://dicom.Apteryx.net:2762/testing cert "D:\converter\Apteryx_net_testing.pfx" move-to "D:\converter\Apteryx-Conversion\Stored"New command example:
xvhost push "D:\converter\Apteryx-Conversion\Images" to dicoms://dicom.Apteryx.net:2762/testing cert "D:\converter\Apteryx_net_testing.pfx" move-to "D:\converter\Apteryx-Conversion\Stored" one-at-a-timeConversion Percentage
First you need to obtain the most upto date Imagecache and logs folder images sheet.
Open the imagecache in Notepad and scroll to bottom to copy this string.
Next, using Notepad++ search the file with the thread you copied.
Inside Notepad++ the thread was on 644,026 of total 1,358,451. Divide 644,026 / 1,358,451 = 47%
Alternatively, place this executable in the converter directory, open a command-line prompt, and run the exe.
NOTE: This does NOT work for Apteryx / XV4 / Dentrix Ascend conversions.
Can’t insert EXE because IT blocked the file from download in OneNote
Sample output: