IMPORTANT: Any XVHost push greater than 50K images must have their database isolated before the push starts. To request an Apteryx site to be isolated, please post in the Ask Apteryx Developers channel. If you do not have access to this channel, please ping a Supervisor or Senior Tech, and they can request an isolation for you.
Download:
When deploying this, make sure to unzip the folder. Make sure you transfer the entire folder, not just the EasyPush.exe, it needs the Resources folder as well to function.
After deploying the folder to the client’s workstation or server, navigate to the Resources folder and install VC_Redist.x64. This is necessary for this version of XVHost to function correctly.
After using this program, please remove it from the computer. This program must not be distributed to customers.
Directory of images - Points to the folder containing the DICOM files (typically C:\Apteryx\XVCapture\Databases\Images)
PFX Certificate Path - Points to the .pfx file (typically in XVCapture folder)
Site Name - Should autofill, but will be the domain name https://planetdds.atlassian.net/wiki/spaces/DIKB/pages/3464724555/Domains#What-are-domains%3F
Move Uploaded Images To - Optional. Allows you to move successfully pushed images out of the /Databases/Images folder to a separate folder. Recommended for large scale (50K+) pushes.
Date From and Date To - Optional. Allows you to specify a date range for XVHost to push.
noteXVHost EasyPush accepts paths with quotes on either end e.g. “C:\Apteryx”
XVHost EasyPush accepts paths with quotes on either end e.g. “C:\Apteryx”
Error regarding missing files
Occurs when Resources folder is missing. Make sure you transfer the entire EasyPush folder, not just the EXE.
“UNC Paths are not supported” error when initiating push
This occurs when the EasyPush tool/XVHost was placed on a networked path and is being invoked over a UNC path. XVHost cannot function when run over the network, it must be invoked locally.
To resolve, place the entire EasyPush tool somewhere local on the workstation or server you are accessing, and launch EasyPush.exe from there instead.
XVHost pausing/crashing during push
Typically occurs when handling a large push, causing the push to have to be restarted.
If you find XVHost pauses or crashes after a few thousand images, it is recommended to use the Move Uploaded Images To option moving forward. The pauses/crashes will likely still persists every few thousand images, but utilizing this option will allow you to easily restart the push from the point it had stopped.
Without Move Uploaded Images To in use, its impossible to restart the push from where it had left off, as XVHost attempts to push all images contained in the folder specified in Directory of images regardless of if they have successfully pushed or not. Using this option forces successfully pushed images to move to another folder, allowing the push tool to only see data it has not yet pushed.
Pause/crash occurs every 0-20 images
Typically occurs when handling a large push when many STAMP files are left over from successfully pushed and moved images. Removing left over STAMP files should resolve this.
If you find XVHost pauses or crashes every 0-20 images after otherwise working normally, and restarting it a couple of times doesn’t allow it to proceed normally anymore:
Open the folder Directory of images is pointed at
Sort by Date Modified
Scroll down to the bottom, you should see a lot of STAMP files left behind from already successfully pushed and moved images
-
Click the bottom STAMP file, then scroll up until you start to see DIC files - once you see DIC files, hold SHIFT and select the last STAMP file before DIC files start to be found.
This doesn’t need to be perfect, we’re essentially selecting most/all left over STAMP files from already forwarded images and missing a few isn’t a problem, as they do not contain actual image/patient data
Hit CTRL + X (Or right-click > cut), then paste into a separate folder, such as the folder where successful pushes are being moved
Open the folder Directory of images is pointed at again, and allow Windows to “index” the folder (shown by a green progress bar where the filepath displays)
Once done, restart the push. It should proceed normally