Component Not Found in the Registry

Component Not Found in the Registry

Fusion Servicing Director Link (SD Link) Connection Editor Error: Component not found in the registry.

Root Cause:

The most common cause for this message is the SD Link server does not have the ODBC 17 driver for SQL Server from Microsoft installed, as listed on the SD Link Pre-Install Checklist.

Workaround:

  1. Download and install the ODBC 17.x driver for SQL Server from Microsoft.  
  2. Retry the SD Link Connection Editor.

ArticleNumber:

000042322

    • Related Articles

    • Error BOServer: File Not Found

      BOServer: File note found (C:\Program Files (x86)\D+H\Servicing Director\BussObj\[file name].cbo Root Cause: This message appears when you are opening a custom add-on to your Fusion Servicing Director system and your computer does not have the ...

    • Runtime Error 53 File Not Found

      During an update, you received the following error: Runtime Error 53 File Not Found Root Cause: During the update process the file names for EZTELLERENT.EXE OR EZSUPERENT.EXE changed to EZTELL~.EXE or EZSUP~.EXE. Fusion EZTeller cannot read the ...

    • Run-Time error 339 - Component Vsflex6.ocx or One of its Dependencies is Missing.

      Run-Time error 339 - Component Vsflex6.ocx or one of its dependencies is missing. Root Cause: You are trying to view the user List in EZID and the error occurs. The file Vsflex6.ocx is missing from the Windows\System32 folder or needs to be ...

    • ReportDebug.txt Error Table Could Not Be Found

      In Fusion Servicing Director, you will receive the following error if your Customer Self-Service web applications is denied access to the table or view listed in the error: After GetReportLoc Before load After load ...

    • Application Error 1706 No Valid Source Could Be Found

      Error 1706. No valid source could be found for product Fusion Servicing Director Application. The Windows Installer cannot continue. The feature you are trying to use is on a network resource that is unavailable. Root Cause: This error can be caused ...