Machine Rebuild - restored ReportServer database

I recently had to rebuild my local machine. As such, I backed-up all
of the relavent local databases that I needed (including the RS dbs).
After the rebuild, I have attempted to connect my new instance of RS to
a restored version of the ReportServer database. The instance
initialized after I got the encryption keys worked out (finally
remembered the password), however, when trying to run any saved report
(or any function other than directory browsing for that matter), I get
an error of:
The feature: "Scale-out deployment" is not supported in this edition of
Reporting Services. (rsOperationNotSupported) (rsRPCError).
Important things to know about my install:
1. My machine name is now different than before.
2. The orginal SQL instance was named, now it is the default
3. Was, and still am, running the Standard edition
I know that the scale-out deployment is not available in the Standard
edition. However, the install is completely local. My only thought is
that the restored database has kept the original machine name and/or
SQL instance name somewhere and RS is comparing against that. Is there
a way to correct this or am I up a creek?
Any help would be greatly appreciated - I am rather new to RS . . .
Thanks,
ScottI will save someone some time by stating that I was able to:
1. Save the report and model definitions from the original restored
database locally
2. Repointed my RS instance to the newly setup ReportServer database
3. Upload the definitions
4. Recreate datasources
5. Reconfigure the models to point a new data sources.
The reports came up ok - a little bit of a hassle, but got everything
working. Fortunately, just local development and I only had a couple
of reports.
Thanks,
Scott

LSN Error

SQL 2k WIn 2k.
I just restored a dB and now I am receiving the following error on my
log reader for the restored dB.
The LSN (169614:314254:8) passed to log scan in database 'StoreMain' is
invalid.
I cannot find anything online. Any one have any ideas?
Larry...
Did you also restore the distribution database as well as the subscribers?
When the log reader starts, it reads an entry from the distribution database
that designates the last LSN read from the transaction log. The Log Reader
then starts to read the transaction log forward of that marker. If you have
restored the publisher without also addressing the distribution database and
the susbcriber, then the Log Reader is not going to find the LSN that it is
looking for and will then throw this error. The cleanest way to fix this is
to reinitialize, because your subscribers can have data that is out of synch
with the publisher.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1136841382.142705.313890@.f14g2000cwb.googlegr oups.com...
> SQL 2k WIn 2k.
> I just restored a dB and now I am receiving the following error on my
> log reader for the restored dB.
> The LSN (169614:314254:8) passed to log scan in database 'StoreMain' is
> invalid.
>
> I cannot find anything online. Any one have any ideas?
> Larry...
>
|||How will reinit fix the LSN problem?
The cleanest way to fix this is to reinitialize, because your
subscribers can have data that is out of synch with the publisher.