SSRS 2005 Install Reporting Services error

I have an installation of 2 SSRS 2005 servers running on Windows Server 2k8 R2. Each node has 3 named instances. I have one instance that is working fine from 1 node but when I try to restore the keys to connect the other node I get an error.. Now I should mention that the database was created by the first node/instance set up. So the node I am trying to connect is a new install.. However the node that I am trying to connect had the instance uninstalled mssql.3 (instance folder removed) and Registry keys for that instance removed as well. I did the fresh install ran through the configuration manager. everything is green except for the keys. When I try to restore keys backed up from the 1st node that is connected and working I get the following error.

from the ReportserverService log.
ReportingServicesService!library!8!10/1/2013-14:05:51:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information., CryptUnprotectData: Win32 error:87;
 Info: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information.
ReportingServicesService!library!8!10/1/2013-14:05:51:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.FailedToDecryptConfigInformationException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted., ;
 Info: Microsoft.ReportingServices.Diagnostics.Utilities.FailedToDecryptConfigInformationException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information.
   at Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.UnprotectData(Byte[] data, Int32 dwFlags, Boolean transitoryData)
   at Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.LocalUnprotectData(String data, Boolean transitoryData)
   at Microsoft.ReportingServices.Diagnostics.RSConfiguration.DecryptCatalogData(String encryptedData, String element)
   --- End of inner exception stack trace ---
ReportingServicesService!library!8!10/1/2013-14:05:51:: e ERROR: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.FailedToDecryptConfigInformationException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information.
   at Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.UnprotectData(Byte[] data, Int32 dwFlags, Boolean transitoryData)
   at Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.LocalUnprotectData(String data, Boolean transitoryData)
   at Microsoft.ReportingServices.Diagnostics.RSConfiguration.DecryptCatalogData(String encryptedData, String element)

As I understand it the rs Catalog gets left when you remove and reinstall an instance. However since I removed the reg entries and install folder I'm not sure that's the case. When I look at the keys table there is only one server key populated which is the node that is working correctly.. I am wondering if there is a way to recreate or fool the Catalog GUID in the RSReportserver.config?

thanks
AjarnJonesyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AjarnJonesyAuthor Commented:
Okay I figured this out.. Usually you could use the SSRS tools to delete/recreate keys.. However in this case I have an instance that was removed then reinstalled to the same Load Balanced server using the same Instance name. A kind of hokey way of doing it to fix the issue (but it works) was to change the windows service identity to local service and restart. Once I had that I changed it back to the domain account that I need to use and it created a new guid in the rsreportserver.config.  Once I had the new guid it let me connect right back up and restore the keys that were backed up from the other node. The fact that it was a fresh database had nothing to do with it.. HOWEVER I could have recreated all the keys for the original database if I would have grabbed the server guid from the keys table and added it to the rsreportserver.config.   anayway may not make much sense but it worked.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.