DPM 2025 install fails with ID 812 — SSRS refuses to execute ReportSRV10.dll (Server 2025 + SQL/SSRS 2022)

Question

DPM 2025 Installation – Error ID 812 Issue Report

This report documents an installation failure encountered when installing Microsoft System Center Data Protection Manager (DPM) 2025 on a New installation of Windows Server 2025 using SQL Server 2022 and SSRS 2022. The failure manifests as Error ID 812 during report deployment due to SSRS refusing to execute the DPM report assembly (ReportSRV10.dll) under default Code Access Security (CAS) policy.

Environment

·       OS: Windows Server 2025

·       DPM: System Center Data Protection Manager 2025 (fresh install)

·       SQL: SQL Server 2022, default instance (MSSQLSERVER)

·       SSRS: SQL Server Reporting Services 2022 (native mode), Web Service URL on HTTP port 80 only

·       SQL service accounts: DOMAIN\DPMADMIN for SQL Engine and SQL Server Agent

·       SSRS service account: Network Service

Symptom

DPM setup passes Inspect and SQL detection, then fails during report deployment with ID: 812. The DPMSetup.log shows a SOAP CreateReport failure, and SSRS LogFiles show:

Error while loading code module: 'ReportSRV10, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. Details: Could not load file or assembly 'ReportSRV10 ...' or one of its dependencies. Failed to grant permission to execute. (Exception from HRESULT: 0x80131418)

Expectation

The DPM installer should ensure SSRS trust requirements for its report assembly are satisfied automatically, or pre-check and offer a guided fix, rather than failing with ID 812.

Validated Prior to Failure

·       SSRS reachable at http://<server>/ReportServer (v16 WMI detected)

·       SQL Engine & Agent running as DOMAIN\DPMADMIN (not NT SERVICE accounts)

·       SecureConnectionLevel = 0 (HTTP only)

Workaround That Resolved the Failure

1.       Confirmed ReportSRV10.dll exists at C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\bin\ReportSRV10.dll.

2.       Added a FullTrust CodeGroup in rssrvpolicy.config targeting ReportSRV10.dll (UrlMembershipCondition).

3.       Granted NTFS Read & Execute to NT AUTHORITY\NETWORK SERVICE and DOMAIN\DPMADMIN on ReportSRV10.dll.

4.       Restarted SSRS (stop → start) to reload policy.

5.       Installed ReportSRV10.dll into the GAC using System.EnterpriseServices.Internal.Publish.GacInstall().

6.       Restarted SSRS and re-ran setup — installation completed successfully.

Request to Microsoft

·       Update DPM 2025 installer to auto-configure SSRS trust for ReportSRV10.dll (safe CodeGroup insertion or registering the signed assembly in the GAC).

·       Add a prerequisite check with an automated “Fix” action for SSRS custom assembly trust before installation commits.

·       Update DPM/SSRS install docs to explicitly call out this scenario and the remediation steps.

Attachments Available (on request)

·       DpmSetup.log excerpt around the SOAP CreateReport failure (ID 812).

·       SSRS LogFiles excerpt showing ReportSRV10 “Failed to grant permission to execute”.

·       Exact build numbers (OS, SQL, SSRS, DPM).

Answer 1

The installation issue you are facing with DPM 2025, specifically Error ID 812, occurs when SQL Server Reporting Services (SSRS) refuses to execute the ReportSRV10.dll due to restrictions imposed by the Code Access Security (CAS) policy. This error typically arises during the report deployment phase of the installation process.

To address this issue, you can follow these steps:

1. Confirm the Presence of ReportSRV10.dll: Check that the ReportSRV10.dll file is located at C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\bin\ReportSRV10.dll.
2. Update rssrvpolicy.config: Modify the rssrvpolicy.config file to include a FullTrust CodeGroup that targets the ReportSRV10.dll, allowing it the necessary permissions to execute.
3. Adjust NTFS Permissions: Ensure that both NT AUTHORITY\NETWORK SERVICE and DOMAIN\DPMADMIN have Read & Execute permissions on the ReportSRV10.dll file.
4. Restart SSRS: After applying the above changes, restart the SSRS service to ensure the new policy settings take effect.
5. Install ReportSRV10.dll into the GAC: Use the System.EnterpriseServices.Internal.Publish.GacInstall() method to install the ReportSRV10.dll into the Global Assembly Cache (GAC).
6. Re-run the DPM Installation: Finally, restart SSRS once more and attempt to run the DPM setup again.

By following these steps, you should be able to resolve the installation failure. It may also be beneficial for Microsoft to enhance the DPM installer to automatically handle SSRS trust configurations for ReportSRV10.dll and to include checks for SSRS custom assembly trust prior to installation.