Question Re: ODBC Connection for SQL Server in Technology Q&A

ODBC Connection for SQL Server

Former Member — Mon, 02 Nov 2020 10:39:10 GMT

Hello Everyone,

I am trying to create ODBC connection for SQL Server 2012 and 2016. The drivers I tried is SQL Server and ODBC Driver 7 for SQL Server. while creating connection I am getting attached error. Can anyone please help me to understand why I am getting this error.

I want to access Crystal reports using this connection.

Thanks,

Sujith

Re: ODBC Connection for SQL Server

ayman_salem — Mon, 02 Nov 2020 11:04:49 GMT

This error has nothing to do with BusinessObjects.

Contact your MS SQL Server administrator to check and establish the connection from the BI client / server to the DB server

Re: ODBC Connection for SQL Server

DellSC — Mon, 02 Nov 2020 14:18:19 GMT

You need to use the latest ODBC driver which, I believe, is 13. You could also try using SQL Server Native Client 11.0, which I've had a lot of success with .

-Dell

Re: ODBC Connection for SQL Server

Former Member — Tue, 03 Nov 2020 05:58:25 GMT

Tried with latest ODBC diver and SQL Server Native Client 11.0, but still same issue I am getting.

Re: ODBC Connection for SQL Server

mhmohammed — Tue, 03 Nov 2020 07:53:05 GMT

Did you try to create a 64bit ODBC connection, instead of 32bit? Use the search icon on Windows desktop and type in ODBC, you'll see 2 ODBC options come up, one for 64bit and the other for 32bit, use the 64bit option and then create an ODBC with the same details.

Thanks,
Mahboob Mohammed

Re: ODBC Connection for SQL Server

Former Member — Tue, 03 Nov 2020 09:57:13 GMT

Hi Mahboob,

Thanks for your suggestion, I tried with 64bit as well but getting same error message.

Thanks,

Sujith

Re: ODBC Connection for SQL Server

S_Sriram — Tue, 03 Nov 2020 11:24:01 GMT

Hi Sujith.

From the error screenshot error code, 53 mean the network path was not correct, Could you check your server path. refer to the SAP Note 2709727.

Regards

Re: ODBC Connection for SQL Server

denis_konovalov — Tue, 03 Nov 2020 15:58:46 GMT

As Ayman said, this error comes from your SQL server, so your DBA need to resolve it for you, or you can try Microsoft SQL knowledge base or forums to get help