Reference guide for troubleshooting Denticon Bridge Service connections to third-party dental imaging software, including registry paths, default install locations, and launch parameters for each supported system.
General Troubleshooting Steps
- Make sure the latest Bridge Service is installed (Help > Download Links in Denticon).
- Ensure the Bridge Service is up to date (right-click the tray icon > Check for Updates).
- Check the registry keys for the specific imaging software (see reference tables below).
- Grab logs from C:\Users\<username>\AppData\Roaming\DenticonBridgeService\Logs. Tip: open File Explorer, type %appdata% in the address bar, and press Enter — this avoids having to hunt for the logged-in Windows user folder. From there, open the DenticonBridgeService folder.
- Screenshot the Developer Tools console after launching the bridge from Denticon.
X-Ray Imaging Software Reference
Each entry below lists the registry location, default executable path, launch command, and any data-path or configuration notes needed to bridge Denticon with that imaging system.
Apteryx
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Apteryx\ApplicationLocations — SubKey: XVa3 |
| Default EXE File | \\server\Apteryx\XVAssistant.exe |
| Launch Program Command | /p"Lastname,FirstName::SSN::PatID::DOB::Sex" |
| Comments | DDSWorks.exe, CliniView.exe, ProfSuni.exe, or DentiMax.exe should be renamed to XVAssistant.exe. |
Apteryx DrSuni
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Apteryx\ApplicationLocations — SubKey: XVa3 |
| Default EXE File | C:\Program Files\Apteryx\Apteryx Imaging\DrSuniNL.exe |
| Launch Program Command | /p"Lastname,FirstName::SSN::PatID::DOB::Sex" |
Apteryx XVCapture
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Apteryx\ApplicationLocations — SubKey: XrayVision DCV |
| Default EXE File | XrayVisionDCV.exe |
| Launch Program Command | /p"Lastname,FirstName::SSN::PatID::DOB::Sex" |
| Comments | If XrayVisionDCV.exe does not exist in XVCapture's install directory, copy the existing XVCapture.exe and rename the copy to XrayVisionDCV.exe. |
Apteryx DataGrabber
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Apteryx\ApplicationLocations — SubKey: XrayVision DCV |
| Default EXE File | C:\Program Files\Apteryx\Apteryx Imaging\Datagrabber.exe |
| Launch Program Command | /p"Lastname,FirstName::SSN::PatID::DOB::Sex" |
Apteryx XVLite
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Apteryx\ApplicationLocations — SubKey: XVa3 |
| Default EXE File | C:\Program Files\Apteryx\Apteryx Imaging\XVLite.exe |
| Launch Program Command | /p"Lastname,FirstName::SSN::PatID::DOB::Sex" |
Carestream V8
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Trophy\TW\Path — String Value: BDDPath |
| Comments |
For Chrome/Edge — 64-bit machines: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Trophy\TW\Path. 32-bit machines: HKEY_LOCAL_MACHINE\SOFTWARE\Trophy\TW\Path. If the server name doesn't work, use the IP address instead. For IE: HKEY_CURRENT_USER\Software\Trophy\TW\Path\BDDPath. Client must be on version 8.0.17+ to bridge with SSN; on 8.0.16 and under, use the Kodak/Trophy bridge setup instead. |
DentiMax Imaging
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Apteryx\ApplicationLocations — SubKey: XVa3 |
| Default EXE File | C:\Program Files\Apteryx\Apteryx Imaging\DMADVI.exe |
| Launch Program Command | /p"Lastname,FirstName::SSN::PatID::DOB::Sex" |
| Comments | DMADVI.exe or DMI.exe should be renamed to XVAssistant.exe. |
Dexis — Direct
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Dexis — SubKey: ApplicationPath |
| Default EXE File | C:\Program Files\Dexis\Dexis.exe |
| Comments | Before launching, we pre-fill Denticon patient data to the local machine, e.g. C:\Program Files\Dexis\Denticon.txt. |
Dexis — Integrator
| Default EXE File | C:\Dexis\Integra.exe |
| Comments | Launch Integra.exe. Before launching, we pre-fill Denticon patient data to the local machine, e.g. C:\Dexis\Denticon.txt, and update C:\Dexis\INTEGRA.INI with PMS=Denticon. |
Dexis Imaging Suite 10
| Default EXE File | C:\Dexis\Dexis.exe |
| Comments | Confirm this reg key is present: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Dexis\DEXIS Imaging Suite 10 (see DEXIS.reg). Cannot bridge to version 10.7.1 — known working version is 10.0.4. |
Downloads DEXIS.reg
DTX Studio
| Comments | Have office confirm that Dexis has installed DTX Studio Integrator. Without this portion we cannot bridge to it. Once integrator is installed completely you can confirm by verifying that this directory exists C:\Dexis\Dexis.exe. Once everything is in place follow the steps for Dexis - Direct |
Download
Dolphin Imaging
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Dolphin Imaging Systems — SubKey: Path → C:\Dolphin |
| Default EXE File | C:\DOLPHIN\DOLCTRL.EXE and C:\DOLPHIN\DOLDB.EXE |
| Launch Program Command | [path] Find –I PATIENTID |
| Comments |
We create a DENTICON.INI file with Denticon patient information, then launch DOLDB.exe with the patient ID as a parameter — it returns the patient ID if found, else blank. We open the existing patient or create a new one accordingly, then launch DOLCTRL.exe with the patient ID. |
EasyDent
| Default EXE File | C:\EasyDent4\EdpV4\EasyDent4.exe |
| Comments | Before launching, we pre-fill Denticon patient data to the local machine, e.g. C:\EasyDent4\EdpV4\linkage.xml. |
EzDenti-i (Chrome only)
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\EWOOSOFT\E2 |
| Comments |
Create a String Value named “ExecutableName” with data \\VTEzDenti-i32.exe grant full permission to the Vatech folder. Default exe key launches as “VTEDenti-i32.exe,” which is incorrect (no such file exists) — work around this with the registry key above. Give full read/write permission to C:\Program Files (x86)\VATECH\EzDent-i (the \Bin subfolder does not need to be in the reg key, even though the exe lives there. Reg key name: ExecutableName; Value: VTEzDenti-i32.exe. Reference: EzDenti64.reg. |
Download EzDenti64.reg
Gendex Imaging
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\vixwin\ApplicationLocations — SubKey: vixwin |
| Default EXE File | c:\vixwin\vixwin.exe |
| Launch Program Command | -I <PatientID> -N <FirstName>^<LastName> |
Genoray — Triana
| Default EXE File | C:\Program Files (x86)\genoray\GDP-1\Triana.exe |
| Comments | Before launching, we pre-fill Denticon patient data to the local machine, e.g. C:\Denticon\Denticon.ini (the C:\Denticon folder must exist). |
Kodak OMS Imaging
| Registry EXE File Path | HKEY_LOCAL_MACHINE\Software\PWInc\Kodak OMS Imaging\ — Subkey: LocalExeDir |
| Default EXE File | C:\PWInc\Image\PWImage.exe |
| Launch Program Command | –I<Path and file name> -E<Export Path and file name> |
| Registry DATA Path | HKEY_CURRENT_USER\Software\Trophy\TW\Path\BDDPath |
| Default Data Path | C:\PWInc\Image\ |
Kodak/Trophy
| Registry EXE File Path | HKEY_LOCAL_MACHINE\Software\PWInc\TrophyWindows — Subkey: LocalExeDir |
| Default EXE File | C:\TW\TW.exe |
| Launch Program Command | -P<DATAPATH>\<PATIENTID> -N<LASTNAME>,<FIRSTNAME> |
| Registry DATA Path | For Chrome/Edge — 64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Trophy\TW\Path; 32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Trophy\TW\Path (use IP address if server name fails). For IE: HKEY_CURRENT_USER\Software\Trophy\TW\Path\BDDPath. |
| Default Data Path | C:\TW\ |
| Comments |
MiPACS / Medicor Imaging (Lead Tools)
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Medicor Imaging\MiPACS Dental Enterprise Viewer 3 — Sub Key: MiDentViewPath |
| Default EXE File | C:\Program Files\Midentview\cmdlink.exe |
| Launch Program Command | /ID=PATIENT_ID, /FN=FIRST_NAME, /LN=LAST_NAME, /BD=06/25/1984, /Sex=M |
| Comments | Tested against MiPACS Dental Enterprise Viewer 3.1.1235. The registry value is stored like C:\Program Files (x86)\midentview\midentview.exe — truncate the “midentview.exe” part; cmdlink.exe always lives in that same folder. Reference: DentalEye.reg. |
Download DentalEye.reg
OrthoTrac Imaging
| Registry EXE File Path | HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\PWIMAGE.exe — Subkey: Path |
| Default EXE File | C:\PWInc\Images\PWIMAGE.exe |
| Launch Program Command | -I<Full path of INI file with file name> -E<Full path of Export data file with file name> |
| Registry DATA Path | HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\PWIMAGE.exe — Subkey: Path |
| Default Data Path | C:\PWInc\Images\Denticon.ini |
Patient Gallery
| Default EXE File | X:\PatientGallery.exe |
| Launch Program Command | -PatientID;PatFName;PatLName;;PatDOB |
Patterson Imaging / Eaglesoft
| Registry EXE File Path | HKEY_LOCAL_MACHINE\Software\EagleSoft\Paths — SubKey: Shared Files |
| Default EXE File | C:\Eaglesoft\Shared Files\Imaging.exe |
| Comments | We can only bridge to the standalone version of Eaglesoft — if Imaging.exe is not present in C:\Eaglesoft\Shared Files\, we cannot bridge to it. We create and use a Denticon.ini file as a parameter, placed alongside Imaging.exe (e.g. C:\Eaglesoft\Shared Files\Denticon.ini). Since the exe now installs under C:\Patterson Imaging, copy that folder into C:\Eaglesoft\Shared Files. |
Planmeca Romexis
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Dimaxis.exe |
| Default EXE File | C:\Program files\Planmeca\Romexis\PmBridge\Program\DxStart.exe |
| Launch Program Command | "PatientID" "FamilyName" "FirstName" "BirthDate" <"Doctor"> |
| Comments |
Their DxStart.exe is sometimes incompatible with our bridge — if so, replace it with this one DxStart.exe
|
Download romexis.reg
Prof. Suni
| Comments | Same install process as Apteryx XVa3. |
QuickVision
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Julie\QuickVision — SubKey: QuickVisionApp |
| Default EXE File | C:\Juliew\mj32.exe |
| Launch Program Command | /PA:<PatientID>,LASTNAME,FIRSTNAME |
| Comments | Exe should launch as: <Exepath> C /ALINK, where C is the drive letter. |
QuickVision 2.0
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Julie\QuickVision — SubKey: QuickVisionApp |
| Default EXE File | C:\Juliew\mj32.exe |
| Launch Program Command | /PA:<PatientID>,LASTNAME,FIRSTNAME |
| Comments | Exe should launch as: <Exepath> C /LINK, where C is the drive letter. |
Schick
| Comments | We create a “CDR.Application” object in VB and launch Schick CDR DICOM for Windows with parameters from Denticon. This bridge only works with Schick version 3 and above. |
Sirona (Sidexis) Imaging — Sidexis 4 only
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Sirona\ApplicationLocations — SubKey: Path |
| Default EXE File | C:\sidexis\sidexis.exe |
| Launch Program Command | Confirm C:\sidexis\sifiledb.ini exists (otherwise: “could not be found — is Sidexis installed properly?”). Read the ini file’s [FromStation0] File value to find the comm/sendbox file location (siomin.sdx). Set [OfficeManagement] OffManConnected=1 in the ini so Sidexis is ready to accept a message, then write patient data. |
| Comments | No support for Sidexis XG/2. Example: [FromStation0] File=F:\PDATA\siomin.sdx. Denticon then sets [OfficeManagement] OffManConnected=1 before the “Taken” step. |
Sota / Cliosoft Imaging
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\ClioSoft.exe — SubKey: (Default) |
| Default EXE File | C:\Program Files\ClioSoft\ClioSoft.exe |
| Launch Program Command | -Id;FirstName;LastName;DateOfBirth;SocialSecurityNumber; |
Sopro Imaging (Chrome only)
| Registry EXE File Path | HKEY_LOCAL_MACHINE\SOFTWARE\Sopro - ActeonGroup\SOPRO-Imaging\ — SubKey: ApplicationPath |
| Default EXE File | C:\Program Files(x86)\Sopro Imaging |
TigerView
| Default EXE File | C:\Program Files\TigerView\Tiger1.exe |
| Launch Program Command | Slave1 <PatientID> <FirstName>+<LastName> <SSN> |
| Comments | Works like the Dexis bridge — on 64-bit desktops, the Tiger1.exe must be placed under C:\Program Files. If using the INI method, confirm C:\Windows\Tiger1.ini exists. |
Visix Imaging
| Default EXE File | C:\Program Files\Visix\Tiger1.exe |
| Launch Program Command | Slave1 <PatientID> <FirstName>+<LastName> <SSN> |
| Comments | Copy tiger.exe into Program Files, not Program Files (x86). |
XDR Digital Radiology 4.0
| Registry EXE File Path | HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\XDR.exe — SubKey: Path |
| Default EXE File | C:\XDRClient\Bin\XDR.exe |
| Comments | Create and use a Denticon.txt file as a parameter, created in the Custom directory (C:\XDRClient\Custom\Denticon.txt). |
XDR Digital Radiology 1.0 / 2.0 / 3.0
| Comments | No configuration details on file for these versions — confirm current setup requirements with engineering before bridging. |
Other Third-Party Programs
CamSight (aka Denttio)
| Default EXE File | c:\cdm\cdm\cdmx\cdmx.exe |
| Launch Program Command | [path]Application name;PatientID;First Name;Last Name;SSN;Birthdate |
| Comments | The user supplies the program path, just like MedicTalk. |
MedicTalk
| Comments | No configuration details on file — program path is user-supplied, same pattern as CamSight. |