From: vparc on
I am experiencing the exact same problem. Did you get this resolved? Also, I
am curious as to whether you are running a side-by-side installation with SQL
2000 (as I am) or simply using SQL 2005?

Anyone know the solution to this? I've been working on this for several days
now, to no avail


"Homam" wrote:

> I installed Reporting Services on stand-alone server from a SQL Server 2005
> Standard CD. It supposed to connect to a remote SQL Server that would host
> the ReportServer database.
>
> I went through the steps of the Configure Report Server till I got to
> "Database Setups". I created a new ReportServer database and when click on
> "Apply", I get the following warning:
>
> -- QUOTE --
> Setting Connection Info for Report Server
> Although saving tghe database succeeded, the report server cannot access
> internal information about deployment to determine whether the current
> configuration is valid for this edition. [...]
> -- UNQUOTE --
>
> When I click on the link to show me more information, I get the following
> reported exception:
>
> -- QUOTE --
>
> ReportServicesConfigUI.WMIProvider.WMIProviderException: The report server
> cannot open a connection to the report server database. A connection to the
> database is required for all requests and processing.
> (rsReportServerDatabaseUnavailable)
> at
> ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
> at
> ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ListReportServersInDatabase(RSReportServerInfo[]& serverInfos)
>
> -- UNQUOTE --
>
> I'm not trying to set up a scale-out deployment. I want this single instance
> of RS to connect to a remote database, and I verifiied that this is supported
> by the Standard Edition of SQL Server 2005.
>
> When I ignored this warning and moved the encryption keys stage of the
> configuration, I found that only the Restore and Delete are enabled. If
> clicked on "Delete", I get this error:
>
> -- QUOTE --
>
> ReportServicesConfigUI.WMIProvider.WMIProviderException: The report server
> cannot open a connection to the report server database. A connection to the
> database is required for all requests and processing.
> (rsReportServerDatabaseUnavailable)
> at
> ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
> at
> ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ListReportServersInDatabase(RSReportServerInfo[]& serverInfos)
>
> -- UNQUOTE --
>
>
> I verified that the Reporting Server was actually able to connect to the
> database to create the Reporting Server database. But somehow it cannot
> connect anymore.
>
> Any ideas as to why?
>
>
> Thanks
>
>