CODEWITHSUNDEEP
sql-servercrystal-reports
Pat
Pat

Reputation: 51

Attempting to connect to SQL Server through Crystal Reports

I am attempting to connect Crystal reports to a SQL Server database. Here is what I have done so far.

File > Log On or Off Server

Create New Connection > OLE DB (ADO)

Under provider I selected Microsoft OLE DB Provider for SQL Server and click next.

I select the server from the drop down list and put in the username and password for the local admin account. I am able to remote to the server using this account. For the database field I have tried to enter the database name and the path to the .mdf for this database. I get the same error either way.

Login failed.
Details: ADO Error Code: 0x80040e4d
Source: Microsoft OLE DB Provider for SQL Server
Description: Login failed for user 'server\admin'.
SQL State: 42000
Native Error: 18456 [Database Vendor Code: 18456 ]

Crystal Reports version: 14.0.4.738 RTM
SQL Server 2012

I did find some similar error messages through google, but the situations were different, so it was not helpful.

Upvotes: 2

Views: 19276

Answers (2)

FutbolFan
FutbolFan

Reputation: 13763

When you get a "Database Vendor Code" error, this means that the error code was passed back from the database. So, we know this is a SQL Server error, not a Crystal error.

I found this post quite interesting, so I started researching what other people had to say regarding this subject matter. I stumbled upon this blog which seems to be a few years old. But, this talks about the Native Error: 18456 (which is the exact error code you are getting). So, I am hoping that if you try to create a udf file like the article suggests. You might end up getting something out of it. Here is the link to the article:

Crystal Reports Generating SQL Server Error 18456 Severity 8 Error Logs

Upvotes: 2

Lan
Lan

Reputation: 1361

You may have permissions to remote to the Windows server , but the user should be added also to the SQLServer

Upvotes: 0

Related Questions