Friday, March 23, 2012

Error when moving a report server database to another server

We have a new server (SRV63) and I followed the instructions at http://msdn2.microsoft.com/en-us/library/ms156421.aspx to move the report server database from our old server (SRV38). Everything appeared OK, however, when I went to initialize the instance in the Reporting Services Configuration tool, it shows an initialized instance (checkbox is checked) for SRV38 and and uninitialized instance for SRV63 (checkbox is not checked). Please note that I am not trying to create a scale-out deployment. I tried to initialize SRV63 but received the error below.

--

ReportServicesConfigUI.WMIProvider.WMIProviderException: The report server installation is not initialized. (rsReportServerNotActivated)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.InitializeReportServer(String installationId)

This is the only thing stopping me from shutting down SRV38 and bringing SRV63 into production. Can someone assist me with this issue?

Chuck-

Just curious if you figured this out. I have the exact same problem and can't figure out how to resolve it.

Thanks!

Laura

|||

Hi Laura. I was a bit surprised that I did not receive any response to help me with this issue as I was sure I was not the first to have experienced this issue. As I was short on time; I opted to reinstall Reporting Services and recreated all my user / group folders and securities and re-registered all my reports to the correct report folders. It was like starting from scratch; however it works and I do not have to worry about legacy items from the old server causing issues now. I believe I could have avoided this issue by turning off the Reporting Services on the old server before installing them on the new server therefore only the new Reporting Services instance would show. You might give this a try and see if it works. Sorry I don't have a more definitive answer for you.

Good luck.

|||

I was also able to solve the problem by deleting the report databases and then recreating them through the Reporting Services Configuration. Thanks for your response!

Laura

sql

No comments:

Post a Comment