Recovery from Metabase corruption

I've spent most of the day trying to recover my team foundation server from a metabase corruption (no I had not backed it up).

To date I've had to reinstall IIS,uninstall reporting services and reinstall that as well as sts and the other nonsense.

Right now the TFS installer gets most of the way through (for the 10th ) time and reports that it can't access report server.

In IIS http://localhost/reports/home.aspx I get a message

'The feature: "Scale-out deployment" is not supported in this edition of Reporting Services. (rsOperationNotSupported) (rsRPCError)'

So it's possibly correct that Report server is not running. Now whilst I find lots of stuff which tells me how to enable 'Scale-out deployment' I find none which tells me how to disable it (and I don't want to install enterprise edition).

I have reloaded the report server keys which I saved before embarking on this foolishness and that seemed to get me a bit further forward. The only other thing I did was to set the database in the report server configurator (to the local db with ReportServer. It was originally blank).

Please help!

Thanks

Iain

Moved to Reporting. Hopefully someone here can help.

-Matt

sql

recover master database questions

Before I start I'm innocent-- I had nothing to do with it and I'm just
trying to help...
Anyway, a power outage caused the corruption of a master database and sql
server won't start. I know how to recover the master database with and
without a backup. In this case there was no backup (I'm innocent!) of the
master and so I'll have to run "rebuildm.exe" and attach the existing user
database-- I know about that and understand that. The question I have is
what will the attach database do with replication? After I rebuild the
master and attach the publication database what state are things in? Does
the publication database still have a publication? If yes, are the
subscriptions still valid and ready to connect and replicate without further
intervention? My guess is that after I do the attach on the user database
that there won't be a publication and the DB will have to be cleaned up from
leftover garbage (i.e. triggers) from replication. If anyone out there has
any experience with this I'd appreciate hearing about it.
Thanks, NWOP.Hello NWOP,
I am the producer for the SQL Server website. While I am not a DBA and do no
t play one on television, I did find this article on the Product Support Sit
e which sounds like it may have some information about your issue.
PRB: sp_attach_db and CREATE DATABASE FOR ATTACH Do Not Remove Replication T
ables
http://support.microsoft.com/defaul...kb;en-us;280295
Please feel free to email me directly at msweeny@.microsoft.com if this is no
t close and I'll keep digging at this end.
marianne