So maybe I am the only one that has done this, but I have been dumb enough to now have done this twice so maybe there is someone else out there that is as 'smart' as I am! In my demo environment, I have an OpsMgr 2007 SP1 RMS on a W03 SP2 server with the Operations DB, Report DB, and ACS DB located on a remote W08 server with SQL 2005 SP2. SQL 2005 Report Services is also located on the W08 server as well. The problem? Well, I have found that if you suffer some type of corruption in your OperationsDW (I suffered a power outage in my environment which somehow put the OperationsDW in a Suspect state. And no, of course I did not have a backup of the DB!!!) DB and/or have a reason to re-install OpsMgr Reporting, the act of uninstalling OpsMgr Reporting renders the instance of SRS unusable - you will continually get errors if you try to re-configure/reset SRS back to a usable state and therefore are SOL if you wish to re-install OpsMgr Reporting on this instance. The following are some of the symptoms I have observed:
Basically, the fix for me was the following:
You should then be able to go to http://server/reports or http://reportserver without error now... Therefore, you should ten be able to re-install OpsMgr Reporting.
Oh yeah - I found out that technically we do not support running OpsMgr Reporting on W08 just yet - thus explains why I had to run through a lot of hoops above. However, it seems to work for me with the exception of having to reset SRS if you ever have to reinstall...