When I try to set the Datasource connection for one of my reports to the ODBC connection I created, I get the following error: I can log onto the ODBC connection in CR X1. 'Some tables could not be replaced, as no match was found in the new data source. Please specify the table required for any unmodified tables.' SQL Server Native Client 11.0 supports connections to, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012 (11.x), SQL Server 2014 (12. When I drill down to the SP and try to update the datasource location of the SP directly I get the following errors:Īs I said, I don't have any problems when using the SQL Server 2000 driver. I leave these blank since I'm using Windows Authentication.Attempting to connect using the SQL Server Native Client 10.0 Results in the below error: One other thing to mention, when I initially connect to the ODBC connection in CR X1 with the SQL Native Client driver, it asks for a username and password. Shared Memory Provider: No Process is on the other end of the pipe.įorcing the connection to use TCP just changes the error to a TCP error with similar contents On my laptop in ODBC console I see 3 SQL drivers installed: The only driver that I need is SQL Server Native Client 11.0. In Un-install feature I see the following: My question: how could I know which apps in Un-install console correspond to 2 drivers that I want to remove. I have never had this issue before with the same basic deployment scenario (SQL Server 2014 and Windows Server 2012 R2) Using the SQL Server Native Client 11.0 works fine, unfortunately the application I am trying to connect with does not give me that option as the built in SSIS Packages were built for SQL Server 2008. ODBC and OLE DB sources that connect to SQL Server, Oracle, and Access. I have been googling the issue but all the issues I can find relate to general connection issues, not ones that only occur with the Native Client 10.0. No errors show up in Windows or SQL Event logs when this happens I checked the listed solutions like checking the protocols are enabled, firewalls and services are running regardless and everything appears configured correctly which explains why the Native Client 11 works You can also use text files, Excel files, and XML files. I have also updated to the latest release of the SQL Native Client which has not helped Point odbcinst.ini to the driver in /etc/odbcinst.ini. FreeTDS Description v0.91 with protocol v7.2 Driver MYDRIVERPATH. where MYDRIVERPATH is the path of the libtdsodbc.so file. Hint Look in the /usr/lib/mylinuxdistro/odbc folder Will implement script in the future to install/automate this for linux solutions. The same problem occurs no matter what software I initiate the connection from (e.g.