DPM 2010 Beta Fails to Install (Error 812)
jkoebel
onto a system using an existing SQL 2008 (x64) SP1 server which has been set
up specifically for this purpose. (Brand new Hyper-V virtual machine running
Windows Server 2008 R2 with nothing but SQL installed on it.)
I receive error 812, "Report configuration failed. Verify that SQL Server
Reporting Services is installed properly and that it is running. ID: 812"
I receive the following stack trace in the detailed log file:
====
[10/15/2009 9:05:07 PM] Information : Deploy reports
[10/15/2009 9:05:07 PM] Data : Path of configuration file of SQL Server
Reporting Services = \\CSGTACSQL08A\c$\Program Files\Microsoft SQL
Server\MSRS10.MSSQLSERVER\Reporting
Services\ReportServer\RSReportServer.config
[10/15/2009 9:05:07 PM] Data : Source folder for reports (.rdl files) =
C:\Users\jkoebel\AppData\Local\Temp\DPM7EE6.tmp\DPM2010\Setup\DpmReports
[10/15/2009 9:05:07 PM] Data : Path of dll to invoke =
C:\Users\jkoebel\AppData\Local\Temp\DPM7EE6.tmp\DPM2010\Setup\DlsUILibrary.dll
[10/15/2009 9:05:07 PM] Information : Set report rendering extensions in
Reporting Services
[10/15/2009 9:05:07 PM] Information : Set tracing level in Reporting Services
[10/15/2009 9:05:07 PM] Information : Deploy reports
[10/15/2009 9:05:07 PM] Data : Source folder for reports (.rdl files) =
C:\Users\jkoebel\AppData\Local\Temp\DPM7EE6.tmp\DPM2010\Setup\DpmReports
[10/15/2009 9:05:07 PM] Data : Path of dll to invoke =
C:\Users\jkoebel\AppData\Local\Temp\DPM7EE6.tmp\DPM2010\Setup\DlsUILibrary.dll
[10/15/2009 9:05:43 PM] * Exception : =>
System.Reflection.TargetInvocationException: Exception has been thrown by the
target of an invocation. --->
Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException:
exception ---> System.Web.Services.Protocols.SoapException: The operation you
are attempting requires a secure connection (HTTPS). --->
Microsoft.ReportingServices.Diagnostics.Utilities.SecureConnectionRequiredException: The operation you are attempting requires a secure connection (HTTPS).
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.Internal.EnterpriseStorage.Dls.UI.Reporting.ReportingService2005.CreateDataSource(String
DataSource, String Parent, Boolean Overwrite, DataSourceDefinition
Definition, Property[] Properties)
at
Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateSharedDataSource(String dbConnectionString)
--- End of inner exception stack trace ---
at
Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateSharedDataSource(String dbConnectionString)
at
Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.InstallReports(Boolean
calledFromSetup, String sourceFolderPath, String sqlServerName, String
sqlInstanceName, String dbConnectionString)
*** Mojito error was: ReportingUnknownError; 0; None
--- 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)
[10/15/2009 9:05: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. --->
Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException:
exception ---> System.Web.Services.Protocols.SoapException: The operation you
are attempting requires a secure connection (HTTPS). --->
Microsoft.ReportingServices.Diagnostics.Utilities.SecureConnectionRequiredException: The operation you are attempting requires a secure connection (HTTPS).
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.Internal.EnterpriseStorage.Dls.UI.Reporting.ReportingService2005.CreateDataSource(String
DataSource, String Parent, Boolean Overwrite, DataSourceDefinition
Definition, Property[] Properties)
at
Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateSharedDataSource(String dbConnectionString)
--- End of inner exception stack trace ---
at
Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateSharedDataSource(String dbConnectionString)
at
Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.InstallReports(Boolean
calledFromSetup, String sourceFolderPath, String sqlServerName, String
sqlInstanceName, String dbConnectionString)
*** Mojito error was: ReportingUnknownError; 0; None
--- 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)
--- End of inner exception stack trace ---
at
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.DeployReports(Boolean isRemoteDb, String rsMachineName, String rsInstanceName)
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)
at
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallerThreadEntry()
*** Mojito error was: ReportDeploymentFailed; 0; None
[10/15/2009 9:05:45 PM] *** Error : Report configuration failed.
Verify that SQL Server Reporting Services is installed properly and that it
is running.
ID: 812
[10/15/2009 9:05:45 PM] Information : Data Protection Manager installation
has failed. All the items that were copied during the installation process
have been removed.
For details, click the Error tab.
====
I have verified that Reporting Services is configured for SSL on the SQL
server, but don't really know where to go from here.
This error happens both using a stand alone SQL server that I've installed,
but it also happens if I ask DPM to install its own SQL server instance on
the same machine. I get the exact same error no matter where the actual SQL
server is installed.
Any suggestions? I'd like to get DPM installed and working very much.
Thank you for your time.
Venkata Praveen Borra[MSFT]
If there are SSL certificates on your computer, by default SQL 2008
installation configures HTTPS for reporting websites. When DPM tries to
deploy reports on these websites it may fail if the reporting websites
aren't accessible (might be due to invalid/expired certificates). To
workaround this, provided you don't require HTTPS for reporting websites do
the following:
1. Edit C:\Program Files\Microsoft DPM\SQL\MSRS10.MSDPMV3BETA1EVAL\Reporting
Services\ReportServer\rsreportserver.config
2. Set the SecureConnectionLevel to 0 if the current value is 2 (A value to
2 means secure connection is required)
3. Connect to SQL reporting service configuration manager and connect to the
instance MSDPMV3BETA1EVAL
4. Click on Web Service URL, click advanced and remove SSL identities
5. Repeat the above for Report Manager URL
6. Make sure report manager URL and web service URL are accessible with out
any errors.
6. Restart report server
Now try DPM installation.
Thanks
Venkata Praveen[MSFT]
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"jkoebel" <jko...@discussions.microsoft.com> wrote in message
news:D387B9D5-B35B-4BF2...@microsoft.com...
j.w. koebel
the file "Program Files\Microsoft SQL Server\MSRS10.MSCRMRPT\Reporting
Services\ReportServer\rsreportserver.config file and changing <Add
Key="SecureConnectionLevel" value="2"/> to have value "0" and restarting the
service.
It would be a major usability update to not require manual editing of a
config file, or at least more clear information about the actual problem,
though.
luizbatista
Thank you!
Venkata Praveen Borra[MSFT] wrote:
Hi,If there are SSL certificates on your computer, by default SQL
16-Oct-09
Hi,
If there are SSL certificates on your computer, by default SQL 2008
installation configures HTTPS for reporting websites. When DPM tries to
deploy reports on these websites it may fail if the reporting websites
are not accessible (might be due to invalid/expired certificates). To
workaround this, provided you do not require HTTPS for reporting websites do
the following:
1. Edit C:\Program Files\Microsoft DPM\SQL\MSRS10.MSDPMV3BETA1EVAL\Reporting
Services\ReportServer\rsreportserver.config
2. Set the SecureConnectionLevel to 0 if the current value is 2 (A value to
2 means secure connection is required)
3. Connect to SQL reporting service configuration manager and connect to the
instance MSDPMV3BETA1EVAL
4. Click on Web Service URL, click advanced and remove SSL identities
5. Repeat the above for Report Manager URL
6. Make sure report manager URL and web service URL are accessible with out
any errors.
6. Restart report server
Now try DPM installation.
Thanks
Venkata Praveen[MSFT]
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Previous Posts In This Thread:
On Friday, October 16, 2009 12:21 AM
jkoebel wrote:
DPM 2010 Beta Fails to Install (Error 812)
I am attempting to install System Center Data Protection Manager 2010 Beta
On Friday, October 16, 2009 12:55 AM
Venkata Praveen Borra[MSFT] wrote:
Hi,If there are SSL certificates on your computer, by default SQL
Hi,
If there are SSL certificates on your computer, by default SQL 2008
installation configures HTTPS for reporting websites. When DPM tries to
deploy reports on these websites it may fail if the reporting websites
are not accessible (might be due to invalid/expired certificates). To
workaround this, provided you do not require HTTPS for reporting websites do
the following:
1. Edit C:\Program Files\Microsoft DPM\SQL\MSRS10.MSDPMV3BETA1EVAL\Reporting
Services\ReportServer\rsreportserver.config
2. Set the SecureConnectionLevel to 0 if the current value is 2 (A value to
2 means secure connection is required)
3. Connect to SQL reporting service configuration manager and connect to the
instance MSDPMV3BETA1EVAL
4. Click on Web Service URL, click advanced and remove SSL identities
5. Repeat the above for Report Manager URL
6. Make sure report manager URL and web service URL are accessible with out
any errors.
6. Restart report server
Now try DPM installation.
Thanks
Venkata Praveen[MSFT]
--
This posting is provided "AS IS" with no warranties, and confers no rights.
On Friday, October 16, 2009 12:47 PM
j.w. koebel wrote:
I'd like to note that I was able to resolve this issue, by manually editingthe
I'd like to note that I was able to resolve this issue, by manually editing
the file "Program Files\Microsoft SQL Server\MSRS10.MSCRMRPT\Reporting
Services\ReportServer\rsreportserver.config file and changing <Add
Key="SecureConnectionLevel" value="2"/> to have value "0" and restarting the
service.
It would be a major usability update to not require manual editing of a
config file, or at least more clear information about the actual problem,
though.
"jkoebel" wrote:
Submitted via EggHeadCafe - Software Developer Portal of Choice
Generate Server Side Dropdown Menues
http://www.eggheadcafe.com/tutorials/aspnet/21393e18-af39-4df3-938b-248c4cb18755/generate-server-side-drop.aspx
@discussions.microsoft.com Jedi (MCM:EX2007)
"Venkata Praveen Borra[MSFT]" wrote:
> .
>
kjartanandreassen
Venkata Praveen Borra[MSFT] wrote:
Hi,If there are SSL certificates on your computer, by default SQL
16-Oct-09
Hi,
If there are SSL certificates on your computer, by default SQL 2008
installation configures HTTPS for reporting websites. When DPM tries to
deploy reports on these websites it may fail if the reporting websites
are not accessible (might be due to invalid/expired certificates). To
workaround this, provided you do not require HTTPS for reporting websites do
the following:
1. Edit C:\Program Files\Microsoft DPM\SQL\MSRS10.MSDPMV3BETA1EVAL\Reporting
Services\ReportServer\rsreportserver.config
2. Set the SecureConnectionLevel to 0 if the current value is 2 (A value to
2 means secure connection is required)
3. Connect to SQL reporting service configuration manager and connect to the
instance MSDPMV3BETA1EVAL
4. Click on Web Service URL, click advanced and remove SSL identities
5. Repeat the above for Report Manager URL
6. Make sure report manager URL and web service URL are accessible with out
any errors.
6. Restart report server
Now try DPM installation.
Thanks
Venkata Praveen[MSFT]
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Previous Posts In This Thread:
On Friday, October 16, 2009 12:21 AM
jkoebel wrote:
DPM 2010 Beta Fails to Install (Error 812)
I am attempting to install System Center Data Protection Manager 2010 Beta
On Friday, October 16, 2009 12:55 AM
Venkata Praveen Borra[MSFT] wrote:
Hi,If there are SSL certificates on your computer, by default SQL
Hi,
If there are SSL certificates on your computer, by default SQL 2008
installation configures HTTPS for reporting websites. When DPM tries to
deploy reports on these websites it may fail if the reporting websites
are not accessible (might be due to invalid/expired certificates). To
workaround this, provided you do not require HTTPS for reporting websites do
the following:
1. Edit C:\Program Files\Microsoft DPM\SQL\MSRS10.MSDPMV3BETA1EVAL\Reporting
Services\ReportServer\rsreportserver.config
2. Set the SecureConnectionLevel to 0 if the current value is 2 (A value to
2 means secure connection is required)
3. Connect to SQL reporting service configuration manager and connect to the
instance MSDPMV3BETA1EVAL
4. Click on Web Service URL, click advanced and remove SSL identities
5. Repeat the above for Report Manager URL
6. Make sure report manager URL and web service URL are accessible with out
any errors.
6. Restart report server
Now try DPM installation.
Thanks
Venkata Praveen[MSFT]
--
This posting is provided "AS IS" with no warranties, and confers no rights.
On Friday, October 16, 2009 12:47 PM
j.w. koebel wrote:
I'd like to note that I was able to resolve this issue, by manually editingthe
I'd like to note that I was able to resolve this issue, by manually editing
the file "Program Files\Microsoft SQL Server\MSRS10.MSCRMRPT\Reporting
Services\ReportServer\rsreportserver.config file and changing <Add
Key="SecureConnectionLevel" value="2"/> to have value "0" and restarting the
service.
It would be a major usability update to not require manual editing of a
config file, or at least more clear information about the actual problem,
though.
"jkoebel" wrote:
On Friday, December 11, 2009 9:08 AM
Luiz Batista wrote:
Thanks Venkata Praveen
This solution saved my life! I have been looking to make this work for two days!
Thank you!
On Saturday, January 09, 2010 4:51 PM
Jedi (MCM:EX2007) wrote:
THANKS!!"Venkata Praveen Borra[MSFT]" wrote:
THANKS!!
"Venkata Praveen Borra[MSFT]" wrote:
Submitted via EggHeadCafe - Software Developer Portal of Choice
.NET Number and Currency Formatting
http://www.eggheadcafe.com/tutorials/aspnet/43c50121-631c-4369-a603-285e82c5e6ef/net-number-and-currency.aspx