Reporting stops working after you move a reporting services point or enable TLS 1.2 in Configuration Manager

Applies to: System Center Configuration Manager (current branch - version 1902)System Center Configuration Manager (current branch - version 1810)System Center Configuration Manager (current branch - version 1806)

Symptoms


After you move the reporting services point role to a new server, or you enable TLS 1.2 on the site servers, reporting no longer works in Microsoft System Center Configuration Manager.

The following error messages are logged in the Srsrp.log file on the reporting services point:

Cause


This issue occurs because the site servers and site systems do not meet the requirements that are described in How to enable TLS 1.2 for Configuration Manager.

Resolution


To fix this issue and enable TLS 1.2 in Configuration Manager, make sure that the site servers and site systems meet the requirements that are described in How to enable TLS 1.2 for Configuration Manager.

To do this, follow these steps:

  1. Verify that .NET Framework is updated and has strong cryptography enabled on all relevant computers.

    To do this, first determine your .NET Framework version number, and then follow these guidelines:

    • .NET Framework 4.6.2 supports TLS 1.1 and TLS 1.2. No additional changes are required.
    • .NET Framework 4.6 and earlier versions must be updated to support TLS 1.1 and TLS 1.2.

      If you're using .NET Framework 4.5.1 or 4.5.2 on Windows 8.1, Windows RT 8.1, or Windows Server 2012, the relevant updates and details are also available from the Download Center.
    • All Configuration Manager client computers and site systems should have the following registry values set.

      For 32-bit applications that are running on 32-bit systems or 64-bit applications that are running on 64-bit systems:

      For 32-bit applications that are running on 64-bit systems:
  2. Verify that the SMS_Executive service is restarted after any updates are installed.