Skip to Content
Aug 09, 2019 at 10:43 PM

Crystal Reports are nor running when TLS 1.2 is enabled



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.


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");