The Microsoft Data Link Error can occur when testing Business Adapter Studio's connection to Microsoft SQL Server during the "initializing provider" step. This error often occurs because the beacon doesn't have the correct native client installed. The correct native client must be installed to connect to the external database.
To verify your connection settings are correct, test the connection with a Universal Data Link (UDL) test. A UDL file enables you to test the Object Linking and Embedding Database (OLE DB) provider's connectivity to any backend database independent of a full application.
To test the connection using the SQL Server OLE DB provider, follow these steps:
Create a new text file (such as SQL_CONN.txt).
Resave the file as a UDL file (such as SQL_CONN.udl). Select Yes to the warning message about changing the file name extension.
Open the UDL file.
Select the Provider tab, then select the SQL Server OLE DB provider you use in your application, and select Next.
On the Connection tab, specify
The network protocol
The fully qualified domain name (FQDN)
The port number under Select or enter a server name
Select Test Connection.
If you don't receive an error, your settings are correct.
If you receive a similar error to the Microsoft Data Link error, follow the solution steps below.
To resolve the issue, install one or both of the following providers, depending on your TLS setting and SQL versions.
Microsoft OLE DB Provider for SQL Server (SQLOLEDB) is the most common provider. It's built into Windows and can connect to any version of SQL Server that's not configured to require TLS 1.2 channel bindings.
Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) is the latest SQL Server OLE DB provider. The provider has all the newest features, such as TLS 1.2, MultiSubnetFailover, and Azure authentication options. This provider is recommended for newer SQL Server databases.