It only took one search with the full text of the error to come up with the solution to the problem.
I needed to rework the encryption setup in the SQL Reporting Services Configuration:
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjEUorOB3ROvPxE6UMfUOiM8S1evFzcKA6OJTB-IQdhvlDQMR3eHYa09nJH-YzXl-xwishrTE-JXAPAi7Yf9OcuiT4X5PES5LIgWDsjQ10V2oGyJmmS0CJ337CbiGd7IWCRw4JdijiaO6S5/s400/SQL+2005+Report+Services+Configuration.jpg)
Connect to the default instance:
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjdpDs1J3RJM0zCz-qX4a__crbqmBfdE6BGEha1m62nZNSm-t82cCHWcKVPCOebRH2oUMW-egM9dtBjhLbDITAVjgDptRAtkU1ikpt1P0UZJvTE8Bv-_QVO0RaGTJSo_kwjNAh8nzqGqqRo/s400/SQL+2005+Report+Services+Configuration+-+Connect+To.jpg)
Then, backup, delete, and backup again.
Once I did that process, the error was gone.
We have a few SBS 2K3 R2 Premium installs out there with the number growing.
It is a whole new challenge to get to know SQL 2005! :D
The first source: IPDG3.COM
Which lead to an article on MSDN.
Happy SBSing,
Philip Elder
MPECS Inc.
Microsoft Small Business Specialists.
No comments:
Post a Comment