Hi I am trying to install DPM 2012 SP1 on a VM running Windows 2012.

I am trying to use a remote instance of SQL server 2012 running on a windows 2008 R2 machine.

During the last step of installation I get Error 812.

Going through the install logs I see the following failure:

[9/24/2013 1:22:31 PM] * Exception : Invoking Watson with Exception:  => 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.81.185.225: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, Int32 timeout, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Reporting.ReportingService2005.ListSecureMethods()
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.ConnectToReportServerUrl(String RSUrl, Boolean throwExcecption)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.ConstructReportServerUrl(String sqlServerName, String sqlInstanceName)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.GetReportServerUrl(String sqlServerName, String sqlInstanceName)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateReportProxyObject(String sqlServerName, String sqlInstanceName)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateReportRootFolder(String serverName, String instanceName, Boolean recreate)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.InstallReports(Boolean calledFromSetup, String sourceFolderPath, String sqlServerName, String sqlInstanceName, String dbConnectionString)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.DeployReports(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
   --- End of inner exception stack trace ---
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.DeployReports(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.DeployReports(String reportserverConfigFilePath, Boolean isOemSetup, Boolean isRemoteDb, String sqlServerMachineName, String instanceName)
*** Mojito error was: ReportDeploymentFailed; 0; None
   --- End of inner exception stack trace ---
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.DeployReports(String reportserverConfigFilePath, Boolean isOemSetup, Boolean isRemoteDb, String sqlServerMachineName, String instanceName)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.DpmInstaller.DeployReports(Boolean isRemoteDb, Boolean isUpgrade)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallerThreadEntry()
*** Mojito error was: ReportDeploymentFailed; 0; None

I have confirmed that the Reporting services is running properly on the SQL server.

Also i have checked that no other service is using port 443.

The DPM server is a dedicated brand new VM. I am using a dedicated instance of SQL server.

Has anyone faced a similar problem.

Regards

Mukul

Hi,

This problem happens if the server you are trying to install DPM on or the remote SQL Server used for the DPMDB is already configured to use TCP port 80 with another service.  SQL Server Reporting services will fall back to using TCP port 443 (SSL) if port 80 is already in use.  However, DPM requires that SQL Server Reporting services be installed using port 80.

Run the following command on the SQL Serer to display the IP address, port and application using it. 

From this you can isolate the applications that are using port 80 and either reconfigure it to use another port or un-install the application..

    netstat -anob

Port 80 is only used by PID 4.

After researching a lot i found that http.sys was using it. I stopped it and now nothing is listening on port 80.

I confirmed that using netstat -anob.

The Installation is still failing with the same error.

Hi,

See if the tips in this thread helps.

http://social.technet.microsoft.com/Forums/en-US/b29885d9-b28e-4380-8bc8-3d66ab6e3538/setup-fails-in-scdpm-2012-rc-ssrs

Also, what else is using that instance of SQL server ?  Was it installed exclusively for DPM use ?

The steps did not help.

I am using a dedicated instance of SQL server which is being used exclusively for DPM.

Hi,

Please un-install SQL and re-install it using the steps outlined in this TechNet document.  I know you are using SQ 2012, but the options should be pretty much the same. 

Installing a Remote Instance of SQL Server 2008
http://technet.microsoft.com/en-us/library/ff399612.aspx

Be sure to add the following firewall rules using the below example, adjust accordingly.

A) Open up Services.cpl - locate the SQL Server (Instance_name) - doubleclick to get the "Path to executable"
B) Copy the path IE: "C:\program files\Microsoft SQL Server\MSSQL11.Instance_name\MSSQL\binn\sqlservr.exe"
C) Open up firewall.cpl - advanced settings - inbound rules - then make the following new rules.

    Rule Type: o Program
    This program path: C:\program files\Microsoft SQL Server\MSSQL11.INSTANCE_NAME\MSSQL\binn\sqlservr.exe
    0 Allow the connections
    0 Domain profile
    name: DPM_SqlServr.exe
   
    Rule Type: o Port
    Port:  UDP
    Specific local ports: 1434
    0 Allow the connections
    0 Domain profile
    name: DPM_UDP_Port_1434
   
    Rule Type: o Port
    Port:  TCP
    Specific local ports: 80
    0 Allow the connections
    0 Domain profile
    name: DPM_TCP_Port_80
   
Alternatly, you can use the following command line. Be sure to use correct program path.

netsh advfirewall firewall add rule name=DPM_SqlServr.exe dir=in action=allow program=\"%PROGRAMFILES%\Microsoft SQL Server\MSSQL11.INSTANCE_NAME\MSSQL\binn\sqlservr.exe\" profile=Domain 
netsh advfirewall firewall add rule name=DPM_UDP_Port_1434 dir=in action=allow protocol=UDP localport=1434 profile=Domain
netsh advfirewall firewall add rule name=DPM_TCP_Port_80 dir=in action=allow protocol=TCP localport=80 profile=Domain

 

I figured out the problem.

Turns out in the RS confugration manager we had to do two things:

Changing the Web Service URL Virtual Directory to:

ReportServer_InstanceName

And changing the Report Manager virtual directory to:

Reports_InstanceName

• Marked as answer by Mukul Rathi 20 hours 54 minutes ago

I figured out the problem.

Turns out in the RS confugration manager we had to do two things:

Changing the Web Service URL Virtual Directory to:

ReportServer_InstanceName

And changing the Report Manager virtual directory to:

Reports_InstanceName

• Marked as answer by Mukul Rathi Thursday, October 03, 2013 2:13 PM

I figured out the problem.

Turns out in the RS confugration manager we had to do two things:

Changing the Web Service URL Virtual Directory to:

ReportServer_InstanceName

And changing the Report Manager virtual directory to:

Reports_InstanceName

• Marked as answer by Mukul Rathi Thursday, October 03, 2013 2:13 PM

I figured out the problem.

Turns out in the RS confugration manager we had to do two things:

Changing the Web Service URL Virtual Directory to:

ReportServer_InstanceName

And changing the Report Manager virtual directory to:

Reports_InstanceName

• Marked as answer by Mukul Rathi Thursday, October 03, 2013 2:13 PM

I figured out the problem.

Turns out in the RS confugration manager we had to do two things:

Changing the Web Service URL Virtual Directory to:

ReportServer_InstanceName

And changing the Report Manager virtual directory to:

Reports_InstanceName

• Marked as answer by Mukul Rathi Thursday, October 03, 2013 2:13 PM

I figured out the problem.

Turns out in the RS confugration manager we had to do two things:

Changing the Web Service URL Virtual Directory to:

ReportServer_InstanceName

And changing the Report Manager virtual directory to:

Reports_InstanceName

• Marked as answer by Mukul Rathi Thursday, October 03, 2013 2:13 PM

Hi We have the same problem and that was the solution now the DPM is installed and we can explorer the reports Thx Mukul :)