cancel
Showing results for 
Search instead for 
Did you mean: 

Crystal Reports 2016 SP2 stopped connecting via OLEDB to SQL Server

Former Member
0 Kudos

Using SQL Server 2014. Crystal Reports 2016 SP2 has been connecting without issue to SQL Server database using OLEDB for SQL Server. As of today, reports from within Crystal will no longer connect and return the following error: "Server does not exist, or access denied. Database vendor code 17"...

When calling the same report from a custom Visual .NET program (using the same login information and OLEDB), the report accesses the server and runs fine. But when opening any of my reports directly in Crystal, none of them will access the database. These same reports worked just fine a couple of weeks ago from within Crystal, and the only difference that I know of on the client machine was an automatic update to Windows. I was able after several attempts (with a very slow response time) to get a new report to create a new OLEDB connection and logon to the server with a simple SQL command, and the report runs fine. After that, I was able to run Verify Database on a few reports and they run fine now, however, several other reports will still not access the database and won't return a successful verify database.

I am running the following on the Client:

Windows 10 Education (64 bit) Version 1803 os build: 17134.112

Crystal Reports 2016 SP2 14.2.2.1975

I have

1) rebooted both the client and the server.

2) Run a repair on the Crystal Reports Install

Not sure what else to do! Please help.

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Try upgrading to CR 2016 SP 5 and see if that helps.

DellSC
Active Contributor
0 Kudos

Which version of the SQL Server client do you have installed? You need to have the SQL Server Native Client 11, which is the latest version I believe.

-Dell