![]() OLE DB provider "MSDASQL" for linked server "LinkedServerNamehere" returned message "Client unable to establish connection". ![]() For more information see SQL Server Books Online.". Check if instance name is correct and if SQL Server is configured to allow remote connections. OLE DB provider "MSDASQL" for linked server "LinkedServerNamehere" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. ()Ĭannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "LinkedServerNamehere". The test connection to the linked server failed.Īn exception occurred while executing a Transact-SQL statement or batch. TITLE: Microsoft SQL Server Management Studio My question is why does the linked server fail after 10 minutes using the ODBC Driver 17 for SQL server.īelow is the error when testing the linked server As a matter of fact, I could get the linked server to work without even having to restart the instance. The way I fixed it was I created the DSN connection using the ODBC Driver 11 for SQL server – it supports TLS 1.2 just fine and the linked server did not fail after 10 minutes. ![]() If I restart the instance the linked server will work again for about 10 minutes and fail. The problem is that after about 12 minutes the Linked server fails – sorry I do not have the error message, but its something about cannot connect using the ODBC driver 17 for SQL server. I then created a new DSN connection and restarted the instance and the linked server tested fine. To deal with TLS 1.2 I installed the ODBC Driver 17 for SQL Server. This was working fine for many years until TLS 1.2 became required. I have a requirement to provide a linked server to another SQL Server instance and the way I had to set it up was to create a system DSN connection using the original “SQL Server” ODBC drivers on my server connecting to the remote server and then I created a linked server using the Microsoft OLE DB Provider for ODBC provider to that system DSN I have a Windows 2012 Server and have SQL Server 2014 SP3 Installed. Sorry I do not have the failure message at this point, but I can get it tomorrow This way the ODBC driver will installed and ready to use before you need it in the dialog or install stage.I have a problem where my linked server works for about 12 minutes and then fails. Then I used it in the custom action condition so that it would only run if it was not installed: (ODBC_DRIVER "Installed") AND (VersionNT > 501) OR (VersionNT = 501 AND ServicePackLevel >= 2) Key: SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers I also added a registry search (ODBC_DRIVER) for the ODBC driver: I added the custom action under Dialog Stage Paths Resolution right after CostFinalize. Start-Process "msiexec.exe" -ArgumentList $MSIArguments -Wait -NoNewWindow Param($msiPath, $MSIArguments = "/i $msiPath /passive IACCEPTMSODBCSQLLICENSETERMS=YES") # Block for declaring the script parameters. The way I worked around it was to add the MSODBCSQL_17.2.0.1 as a temp file then call it using the Run PowerShell Inline Script with the following parameters: -msiPath "" In other words we need the ODBC driver to be installed and ready to use whilst we are running our installation program rather than having to be pre-installed before we run our installation program.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |