Resolving DPM Install Error – Report Configuration Failed

During a recent attempt to do some testing in the lab with DPM I encountered the following error during the DPM install:

Report Configuration Failed.
Verify that SQL Server Reporting Services is installed properly and that it is running.
ID: 812

DPM Install Error – Report Configuration Failed ID: 812

My SQL server had an instance created for DPM and I verified that Reporting Services was configured and accessible from the SQL server and the DPM server. It was a pretty puzzling problem.

The DPM install logs proved invaluable in tracking this issue down. You can located the install logs here: C:\Program Files\Microsoft System Center 2012 R2\DPM\DPMLogs

[8/29/2016 10:13:43 PM] * Exception :  => Report configuration failed.Verify that SQL Server Reporting Services is installed properly and that it is running.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: exception ---> Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.ReportDeploymentException: exception ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.0.100.6:443
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---

[8/29/2016 10:26:54 PM] * Exception :  => Report configuration failed.Verify that SQL Server Reporting Services is installed properly and that it is running.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: exception ---> Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.ReportDeploymentException: exception ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.

The logs revealed that DPM was attempting to access the reporting services over 443. As this was a lab setup, I had not taken steps to configure encryption which was causing the failure.

On the SQL server I created a self signed certificated using New-SelfSignedCertificate.

I placed this certificate into the Trusted Root Certification Authorities Certificate store on both the SQL server and the DPM server.

Certificate MMC – Trusted Root Certification Authority Certificates

I attempted the install again, and it still failed throwing the same DPM Install error – Failed ID: 812!

A quick review of the SQL Reporting Services configuration showed that I had forgotten to also set the Web Service URL to utilize SSL. A quick configuration adjustment to utilize the newly created self-signed certificate and I was ready to attempt the install again.

SQL Server 2012 Reporting Services Configuration Manager Web Service URL

With the SQL Reporting Services configured for SSL the DPM Install error was resolved:

Successful DPM install