Error Examples:If you note that you cannot find the provider in the list or that trying to validate a connection will generate an error relating to missing files for the provider.
Troubleshooting Steps:
Improper InstallationThe installer did not install the providers correctly or there are multiple installations (for Cloud Connector) which causes the providers to interfere with each other. See Verification Failed: Could Not Load File or Assembly for how to deal with this. Provider Missing from ListCloud Connector: If the providers are missing from the drop-down, it is likely that the wrong architecture version was installed for the provider. By default, the Backend Service runs in 64-bit mode. Any 32-bit drivers will not work in this mode, but you can set the service to run in 32-bit mode. You need to go to the Connection Manager node in the top left, and then check the box for "Force Backend Service to Run in x86 Mode", then finally click "Save Configuration Changes". This will cause the BackEnd service to restart (and abort any currently running connections). Same as before, 64-bit drivers will not work while x86 mode is active. There is also an issue where the names of the provider may be different than before or as listed in some documentation for version 7.8+. This is because the drop-down menu in version 7.8+ is now showing the description and not the name of the provider. For example, ".Net Framework Data Provider for SqlServer" is the exact same provider as "SqlClient Data Provider".
OleDB-Specific IssuesSee The Provider is Not Registered on the Local Machine (OleDB). ODBC-Specific IssuesThe ODBC driver needs to be the architecture version for the installed product and set up under the correct ODBC Data Sources tool. In modern Windows, both 32- and 64-bit versions of these are listed under Administrative tools. For older 64-bit Windows, only the 64-bit ODBC Data Sources tool is seen under Administrative tools. If the user needs to configure a 32-bit DSN, then they need to go to the %systemdrive%\Windows\SysWoW64 folder to invoke the 32-bit version of odbcad32.exe. The version under the %systemdrive%\Windows\System32 folder is the 64-bit one. It is required that the DSN be set up as a System DSN. There may be other configuration options required in the DSN setup. See the provider documentation for more information. If you've verified that the ODBC sync works as "manual" but fails as the service sync, this usually means they set a User DSN and not a System DSN, and the service account cannot see the DSN definition. See Data Source Name Not Found and No Default Driver Specified (ODBC). Note that the tool by default is running in 64-bit mode (there are no separate installers for the different bit versions). If you need to use the 32-bit ODBC drivers, you must enable X86 mode using the directions above under Providers Missing From List. Machine.config IssuesFor ADO .NET providers, they should appear in the machine.config file appropriate to the providers .NET and bit version. Thus it could appear in one or more of the 4 files on the host machine. Issues that arise from this file have to do with missing entries or incorrectly formatted entries. The 'DBProviderFactories' section can only appear once per config file This specific error means that there are two <DbProviderFactories> nodes in the machine.config file. This maybe is caused by a mistake with the provider install (common with the IBM providers). Reinstalling the provider or editing the machine.config to remove the duplicate node reference should fix the issue. See this StackOverflow thread about where to look for the config file (the first answer isn't as relevant). |
General Provider Issues
