SSRS connection failing after TLS1.2 policy change

[pauline_handel]

We use SSRS to generate more sophisticated reports but it can no longer connect since last Tuesday when our ServiceNow instance was updated to enforce TLS1.2. We installed the latest ServiceNow ODBC driver on our Windows server and we're already running a TLS1.2 compliant version of SQL server. All of the scripts making API calls from internal systems to ServiceNow are working fine so I can't see that it would be a network or proxy server issue. Any suggestions?

Thanks,

Pauline

[Community Alums · Accepted solution]

Googled around and found this:

This issue occurs because SSMS, Report Manager, and Reporting Services Configuration Manager use ADO.NET, and ADO.NET support for TLS 1.2 is available only in the .NET Framework 4.6. For earlier versions of the .NET Framework, you have to apply a Windows update so that ADO.NET can support TLS 1.2 communications for the client.

Seems you will have to apply a window patch to have the SSRS running with TSL 1.2

Many thanks,
Raf

[pauline_handel]

Thanks Raf, I'll kick this across to our Wintel team. When I Googled, I came across a Microsoft whitepaper on SQL Server and TLS1.2 but we'd already got the necessary patches.

[Community Alums]

Great! Let me know if that didn't solve your issue - I know how SSRS works and probably I can point you in the right direction. Many thanks!