- Open OpsMgr Console, export Default Management Pack
- Edit the exported xml file to remove reference to Microsoft.Datawarehouse.Internal and also any Overrides as well
- Remove the Default Management Pack
- Remove the Microsoft.Datawarehouse.Internal MP and also Microsoft ODR MP
- Re-import the Default Management Pack from the xml file that you have edited earlier
- Remove Reporting Server via Add/Remove Programs
- Remove SSRS via Add/Remove Programs
- Remove the necessary Application Pools within IIS (Report Manager and Report Server)
- Log on to SQL Server Management Studio and Remove the following Database
- OperationManagerDW
- ReportServer
- ReportServerTempDB
- Install SSRS and Upgrade to SP2
- Run Reporting Service Config Tool and ensure that you have configured
- SSRS Virtual Directory
- Reporting Server DB
- Encryption Keys
- Web Service
- Install OpsMgr Reporting SP1
- Wait a second, how come the reports list doesn't flow in ? For this, I did something extra. I went to my DC to add my SDK account as a member of Windows Authorization Access Group group.
- Wait for a while ( 20 minutes ) and the reports will start to list one by one
- Give the reports a few tests and that should do the trick.
15 May 2008
Reinstall OpsMgr SP1 Reporting Server
I came to learn it the hard way of not toying with IIS configuration. What started with just running a simple command to switch IIS to run on Win32 Application pool eventually messed up my Reporting Server and even repairing of Reporting Server SP1 couldn't do the trick. Frantic search over the internet didn't help much and so I am left with no choice but to reinstall Reporting Server. Installation went well but then reports can't be generated and so looks like reinstalling of SQL Server Reporting Services (SSRS) is my only choice now. This is what I did along the way on my OpsMgr server;