2

I have migrated SQL server 2005 database to sql server 2008 using side by side upgrade. I have copied Reportserver and reportservertempdb database across and configured SQl server Reporting services 2008 to use this new database. I am not able to restore SSRS key over to new SSRS 2008 server. The key restore reports:

Microsoft.ReportingServices.WmiProvider.WMIProviderException: An error occurred when attempting to connect to the report server remote procedure call (RPC) end point. Verify that the Report Server Windows service is running, and then retry the operation.

 ---> System.Runtime.InteropServices.COMException (0x800706B3): The RPC server is not listening. (Exception from HRESULT: 0x800706B3)
   --- End of inner exception stack trace ---
   at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.ThrowOnError(ManagementBaseObject mo)
   at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.RestoreEncryptionKey(Byte[] encryptedBytes, String password)
   at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.RestoreEncryptionKey(Byte[] encryptedBytes, String password)

I can open SSRS website but just not the encrypted content because of failure in restoring SSRS key.

Can anyone help please?

mhu
  • 123
Manjot
  • 333

4 Answers4

4

Late reply, but I just ran into this issue with moving SSRS 2008 R2 to a new server.

Had the same problem as described above, but going through the Database and Credentials wizards fixed it for me, even though I made no changes and everything was displayed correctly.

Go to Database -> Change Credentials/Change Database in the configuration manager and click through both wizards.

After that I was able to restore the keys.

uuwe
  • 51
1

What error do you get in Reporting Services Configuration Manager when you try and restore the encryption key through there?

SQL3D
  • 670
  • 1
  • 6
  • 12
0

My Solution:

On the server I went into "Reporting Services Configuration Manager" -> Service Account -> Changed to network service Account -> Apply-> Used my current user credentials to login to SQL on the prompt -> changed back to Virtual Service -> Apply -> current credentials again

It applied permissions and then allowed me to import the key

0

I think we need to go through verifying the credentials and database settings before applying the key. I had a similar issue and went through all of them and it did seem to refresh. After that I was able to restore the key without any issues.