Crystal Reports are nor running when TLS 1.2 is enabled

[former_member1327185]

Hi,

we have 1000s of crystal reports which are not working when client has enabled TLS 1.2, I am able to reproduce the error, I am getting error

System.Runtime.InteropServices.COMException: Error in File Invoice Status Report (Drill Down) Current Company 8-14-17 17284_29592_{B16513F0-5AF0-4B61-8EAA-516929F0C4F7}.rpt: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 18 ] at CrystalDecisions.ReportAppServer.Controllers.DatabaseControllerClass.SetTableLocation(ISCRTable CurTable, ISCRTable NewTable)

Here is our connection string.

Environment:

Sql Server 2016
Window Server 2016

We are setting connection programattically so It would be best if any other drivers are compatible we can use that


innerAttributes.Add("Connect Timeout", "60"); innerAttributes.Add("Data Source", server); innerAttributes.Add("General Timeout", "0"); innerAttributes.Add("Initial Catalog", database); innerAttributes.Add("Integrated Security", "False"); innerAttributes.Add("Locale Identifier", "1033"); innerAttributes.Add("OLE DB Services", "-5"); innerAttributes.Add("Provider", "SQLOLEDB"); innerAttributes.Add("Tag with column collation when possible", "0"); innerAttributes.Add("Use Encryption for Data", "0"); outerAttributes.Add("Database DLL", "crdb_ado.dll"); outerAttributes.Add("QE_DatabaseName", database); outerAttributes.Add("QE_DatabaseType", "OLE DB (ADO)"); //Add the QE_LogonProperties we set in the boInnerPropertyBag Object outerAttributes.Add("QE_LogonProperties", innerAttributes); outerAttributes.Add("QE_ServerDescription", server); outerAttributes.Add("QE_SQLDB", "True"); outerAttributes.Add("SSO Enabled", "False");

[DellSC]

Which version of Crystal and which version (including service pack) of the Crystal for Visual Studio SDK are you using?

[former_member1327185]

Hi Dell,
CR Runtime 13.0.22.2668
Crystal Report Designer :Crystal Report 2013 Support Pack 2 version : 14.1.2.1121
Thanks!

[former_member665074]

Harvinder,

Not sure if you have resolved this already, but MS posted a new version OLE DB Driver 18 which resolved conflicts with TLS 1.2

https://www.microsoft.com/en-us/download/details.aspx?id=56730

To resolve this, I converted all my reports to use provider = MSOLEDBSQL and installed the new OLE DB Driver on workstations that would be accessing the reports.

I built a utility that converts the 'provider' for my reports, because like you, I have 1,000's of reports. If anyone is interested in learning more or would like access to a utility to update all reports, feel free to reach out to me.

[former_member314735]

Hi Mike,

I am facing below issue when trying to run Crystal reports from SAP BO BI 4.2 SP6 on windows server 2016. My SQL DBA said they have TLS 1.2 on SQL server and crystal reports using crdb_ado seems like not using tls 1.2

Could you please share your utility to convert all such crystal reports to use MSOLEDBSQL?

ERROR:Logon failed. 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]

[former_member314735]

@mikeycastles

Could you please share your utility to convert all such crystal reports to use MSOLEDBSQL?

[ido_millet]

This is probably relevant:
2269180 - Disabling TLS 1.0 may cause Crystal Reports Designer and .NET application to fail to conne...

[former_member1327185]

ido.millet When I enabled 1.0 crystal reports started working, but client don't want to enable that protocol they want to use 1.2 only.. is there a way we can do that ?