Apteryx Online Capture’s Forwarding Database can be located under Username > Capture > Open Forwarding Database. The following can be found within the Forwarding Database:
Completed forwards
Failed forwards + errors explaining why the failure occurred
The locally stored files the Forward Database references are found in C:\PlanetDDS\Apteryx.Capture\AppCommonFiles\DICOM.
Completed forwards that have successfully stored will be purged from the Forwarding Database as well as C:\PlanetDDS\Apteryx.Capture\AppCommonFiles\DICOM after 24 hours regardless of what the current status of DICOM connectivity is.
Failed forwards and images that failed to store to Apteryx are not purged, and will remain in the Forwarding Database and C:\PlanetDDS\Apteryx.Capture\AppCommonFiles\DICOM.
Troubleshooting within the Forwarding Database
There are two main functions within the Forwarding Database:
Clear Completed: Removed completed forwards from the Forwarding Database.
Requeue: Resubmits the selected failed forwards to Apteryx. Functions similarly to the Fix Forwarding Errors function in XVCapture.
Include Patient Info: Toggles the ability to see Patient ID, Last Name, and First Name associated with the failed forwards.
UID: Displays the image UID belonging to the completed or failed store.
Attempts: How many times Capture has attempted to resubmit the failed forward automatically and/or manually.
Error: Displays why the image had failed to forward.
Completed: Will display what date and time the image successfully stored to Apteryx. If this field is blank, this indicates the file has not stored into Apteryx.
The first recommended step when handling a failed forward is to Requeue and see if the failure is able to resubmit on its own. If the failure is able to resubmit, the Completed status will populate.
More information regarding this process, and where to find forwarding logs if the failure continues to fail can be found here: Finding Missing Images in Apteryx Online Capture
The Forwarding Database shows an image had failed to forward, but you were able to verify the image is visible in Apteryx
If you come across an issue where the Forwarding Database contains failed forwards, but you were able to confirm the images did not fail to forward and are visible in Apteryx, but you’re unable to remove the “failed” forwards from the Forwarding Database, the Forwarding Database can be reset to a clean slate using the following steps:
Shut down the Ambassador (Right-click the Apteryx Ambassador from the System Tray and select “Quit”)
Navigate to C:\PlanetDDS\Apteryx.Capture\AppCommonFiles\DICOM and cut the DICOM files that had “failed” to forward to a separate folder
-
Navigate to C:\PlanetDDS\Apteryx.Capture\AppCommonFiles and rename the XVCapture Data Base File:
Restart the Ambassador - the “failed” forwards should now have disappeared.
The Data Base file acts similar to XVCapture’s ToStore and FailedStore files, where renaming the file will cause Apteryx Online Capture to generate a new file the next time the application is launched.
Since this file references what is contained within C:\PlanetDDS\Apteryx.Capture\AppCommonFiles\DICOM, manually removing the “failed” forwards from this folder then recreating the Data Base file will update the Forwarding Database, removing the “failed” entries.
Confirming if a DICOM file has failed to forward or successfully forwarded
Refer to the steps located in https://planetdds.atlassian.net/wiki/spaces/DIKB/pages/4156883039/Finding+Missing+Images+in+Apteryx+Capture#Confirming-if-a-DICOM-file-had-already-forwarded-to-the-web%2C-or-if-it-had-failed to search by Image UID in XVCapture.
“Certificate not found” error
This can occur if images that were taken on an old version of Apteryx Online Capture and continued to fail to forward after Apteryx Online Capture was updated. If this is seen, navigate to C:\PlanetDDS\Apteryx Online Capture\AppCommonFiles\Logs\Ambassador and review the most recent log - it will display what path Apteryx Online Capture is referencing for that file:
If you find it is referencing C:\Users\<username>\AppData\Roaming\Apteryx.Capture\, this means that image was taken on a version of Apteryx Online Capture that utilized the %AppData% folder.
This folder is no longer used by current iterations of Apteryx Online Capture, so the cert would no longer exist within this path, causing the DICOM file(s) to fail to forward.
To work around this, place the practice’s cert (.pfx file) into the path specified in the log, then requeue the failures in Apteryx Online Capture. The images should forward without issue.
This issue will not apply to newly captured images moving forward, as Apteryx Online Capture will be using the correct path where the cert already exists (C:\PlanetDDS\Apteryx Online Capture\AppCommonFiles\certs).
Viewing Apteryx Online Capture’s “ToStore”
XVCapture.db acts similar to XVCapture’s ToStore and FailedStore files, and is what tells Apteryx Online Capture what needs to store, what has stored, and what has failed to store.
This file can be opened in Notepad if you need to get a closer look for any reason. A lot of text within this file will not display correctly, however the following can still be seen:
DICOM file strings
Path to the client’s cert
Timestamps as to when something attempted to forward
Name of patient associated with the DICOM files