SAP Knowledge Base Article - Preview

2269180 - Disabling TLS 1.0 and 1.1 causes Crystal Reports and .NET application to fail to connect to MS SQL Server

Symptom

  • Error when refreshing reports connecting to SQL Server after disabling TLS 1.0 and 1.1
  • Is Crystal Reports and Crystal Reports for Visual Studio compatible with TLS 1.x ?
  • After disabling the TLS 1.0 and 1.1, Crystal Reports and application using the SDK, fails to connect to MS SQL Server with error like:

         "Logon failed.
          Details: ADO error Code: 0x80004005
          Source: Microsoft OLE DB Provider for SQL Server
          Description: [DBNETLIB][ConnectionOpen
          (SECDoClientHandshake().] SSL Security error. SQL State: 08001
          Native Error: 18 [Database Vendor Code:18]"


Read more...

Environment

  • SAP Crystal Reports 2013
  • SAP Crystal Reports 2016
  • SAP Crystal Reports 2020
      
  • Crystal Reports for Visual Studio
      
  • MS SQL Server 2012
  • MS SQL Server 2014
  • MS SQL Server 2016
  • MS SQL Server 2017
  • MS SQL Server 2019

Product

SAP Crystal Reports 2013 ; SAP Crystal Reports 2016 ; SAP Crystal Reports 2020 ; SAP Crystal Reports, developer version for Microsoft Visual Studio

Keywords

TLS 1.0, Crystal Reports Designer, .NET, CRforVS, MS SQL Server Database , KBA , BI-DEV-NET , BI Software Development Kits (SDKs) - .NET or Other , BI-RA-CR , Crystal Reports designer or Business View Manager , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.