July 25, 2016 at 7:57 am
We have 3 SQL servers. 2 are Enterprise Edition, 1 is Standard Edition. On the 2 Enterprise servers, I have linked servers to DB2 that are working fine. On the Standard server, I have a linked server to DB2 that worked at one time, but now does not work. I am not sure when it stopped working.
All 3 servers have DB2 Connect installed on them, and have ODBC DSNs to the DB2 instances. I am using the provider 'Microsoft OLE DB Provider for ODBC Drivers' in SQL Server to connect to the DB2 databases on all 3. I have verified on all 3 servers that ODBC settings match. I have verified that 'Allow in process' is set for the provider in SQL Server. I am able to connect to DB2 through DB2 Connect command line utilities and query the database, so I know the connection to DB2 is good. However, when I try to create the linked server in SQL Server Management Studio, I get the following error:
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "TEST-LINK".
OLE DB provider "MSDASQL" for linked server "TEST-LINK" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "TEST-LINK" returned message "[IBM][CLI Driver] SQL1031N The database directory cannot be found on the indicated file system. SQLSTATE=58031
". (.Net SqlClient Data Provider)
Any help is greatly appreciated.
July 26, 2016 at 8:59 am
This turned out to be a UAC issue. As soon as UAC was turned off and the server was rebooted, the linked server worked without issue.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply