Fix Bad Data Error After Restore

Our test server had a hardware failuare and I restored the Report Server db's and app - no problem - so it seemed. I am getting a Bad Data Error when trying to run a report. From a previous post I see the issue relates to a different encryption key being used. The autoher noted to fix by reloading catalog.sql. If I do that, won;t i lose the previous deployed reports settings, descriptions etc. Is there a way to keep that info without having to manually redeploy if a hardware failure occurs'Yes, but you must backup (before the failure) and restore the key
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jen" <Jen@.discussions.microsoft.com> wrote in message
news:46813D69-6259-4A82-BA7F-881C52616518@.microsoft.com...
> Our test server had a hardware failuare and I restored the Report Server
db's and app - no problem - so it seemed. I am getting a Bad Data Error
when trying to run a report. From a previous post I see the issue relates
to a different encryption key being used. The autoher noted to fix by
reloading catalog.sql. If I do that, won;t i lose the previous deployed
reports settings, descriptions etc. Is there a way to keep that info
without having to manually redeploy if a hardware failure occurs'|||Ah - I did back up and was able to restore. What is the mysterious key?
The only painful part of the server restore was redeploying and reconfiguring RSS (reports in the right folders, group permissions, etc). After restoring ReportServer db to the server and getting the bad data error, I then restored the ReportServer db to my local PC and copied and pasted necessary report descriptions and other info from the previous install back into the new install using the web interface. It was not terrible but it would have been much nicer to just have restored the ReportServer db versus the redeploy/reconfigure. Is redeploy/reconfigure the only way to recover from hardware failure? Am I missing something with regards to how to do recover better in the event hardware fails again?
All my jobs, db's, etc were operation from restored backups.
"Jason Carlson [MSFT]" wrote:
> Yes, but you must backup (before the failure) and restore the key
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Jen" <Jen@.discussions.microsoft.com> wrote in message
> news:46813D69-6259-4A82-BA7F-881C52616518@.microsoft.com...
> > Our test server had a hardware failuare and I restored the Report Server
> db's and app - no problem - so it seemed. I am getting a Bad Data Error
> when trying to run a report. From a previous post I see the issue relates
> to a different encryption key being used. The autoher noted to fix by
> reloading catalog.sql. If I do that, won;t i lose the previous deployed
> reports settings, descriptions etc. Is there a way to keep that info
> without having to manually redeploy if a hardware failure occurs'
>
>|||Look for the topic "key management" in Books Online. You use the rskeymgmt
utility to backup and restore the encryption key.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jen" <Jen@.discussions.microsoft.com> wrote in message
news:8463A8BA-A3A9-4AD6-8864-60A537234A19@.microsoft.com...
> Ah - I did back up and was able to restore. What is the mysterious key?
> The only painful part of the server restore was redeploying and
reconfiguring RSS (reports in the right folders, group permissions, etc).
After restoring ReportServer db to the server and getting the bad data
error, I then restored the ReportServer db to my local PC and copied and
pasted necessary report descriptions and other info from the previous
install back into the new install using the web interface. It was not
terrible but it would have been much nicer to just have restored the
ReportServer db versus the redeploy/reconfigure. Is redeploy/reconfigure
the only way to recover from hardware failure? Am I missing something
with regards to how to do recover better in the event hardware fails again?
>
> All my jobs, db's, etc were operation from restored backups.
> "Jason Carlson [MSFT]" wrote:
> > Yes, but you must backup (before the failure) and restore the key
> >
> > --
> >
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Jen" <Jen@.discussions.microsoft.com> wrote in message
> > news:46813D69-6259-4A82-BA7F-881C52616518@.microsoft.com...
> > > Our test server had a hardware failuare and I restored the Report
Server
> > db's and app - no problem - so it seemed. I am getting a Bad Data
Error
> > when trying to run a report. From a previous post I see the issue
relates
> > to a different encryption key being used. The autoher noted to fix by
> > reloading catalog.sql. If I do that, won;t i lose the previous deployed
> > reports settings, descriptions etc. Is there a way to keep that info
> > without having to manually redeploy if a hardware failure occurs'
> >
> >
> >