cancel
Showing results for 
Search instead for 
Did you mean: 

ADO Error Code: 0x80004005 for SQL Server

Former Member
0 Kudos

Opening a report with vistual stuido and verify database (SQL Server 2012), it is fine.

But when verify database in the same report in SQL Server 2014, there comes a error:

Logon failed.

Details: ADO Error Code: 0x80004005

Source: Microsoft OLE DB Provider for SQL Server

Description: [DBNETLIB}ConnectionOpen

(SECCreateCredentials0.]SSL Security error

SQL Stae: 08001

Native Error: 18 [Database Vendor Code: 18]

I saw the datasource provider is SQLOLEDB . When I change the datasource provider in report manually to SQLNCLI11, then the error was gone.

How to fix this issue without changing the provider manually?

Is there some mistake confirguation for SQL Server ?

Accepted Solutions (0)

Answers (1)

Answers (1)

Ask Microsoft to update their MDAC SQL Drivers to fully support SQL 2008 and above.

Search MS site, they noted the MDAC drivers do not fully support new versions of SQL Server.

No option in CR to make it work, that error is being generated by the SQL Server Clients.

Don

Former Member
0 Kudos

Hi Don,

Thank you for your explain, but there is still an question that I can not get it.

You said the MDAC SQL Drivers did not fully support SQL 2008 and above.

Why I can verify database in my local environment using SQL Server 2012 but failed in the virtual machine using SQL Server 2014? They are all above SQL 2008.

Is this means that the way set in crystal reports files to connect to database was matched with the way my SQL Server 2012 connects to the database server, but not matched with the way SQL Server 2014 conncets to database?

0 Kudos

I don't know why it works locally, look at the files being loaded by your app.

Use what works and is supported...

Don

Former Member
0 Kudos

Hi Don,

I add a FieldHeading report object to a report with code just like this:

report.ReportClientDocument.ReportDefController.ReportObjectController.Add

(fieldHeading,report.ReportClientDocument.ReportDefController.ReportDefinition.FindSectionByName(SectionName))

the 'fieldHeading' is an heading of an section, and I have checked that the section is not null,and 'FindSectionByName' function can get the section, but there came out an error:Report object not found, I feel strange about this.

Why this error comes out ,is there some mistake?Could you help me?

0 Kudos

New question, new post please