SCOM Reporting install
Fred Pan
reporting. Here's what it looks like...
All servers Windows 2008
Separate large SQL 2008 server for all databases
The data warehouse DB is on the SQL server
The reporting server has SQL reporting services install and configured. It
runs through all the install questions, but once the installation starts and
it gets to the status "connecting to management server" and it quits and
rolls back. with a "value 3" error.
Has anyone seen this before? Know what it is? I've search and not found any
answers that resolve my issue. Thanks!
Fred
Fred Pan
"Fred Pan" <fp...@hotmail.com> wrote in message
news:OMinIlz...@TK2MSFTNGP06.phx.gbl...
Alright I figured this one out myself...
It turns out the first install attempt of SCOM reporting I had the wrong
permissions and I found this posted about the roll back procedures of the
installation. This resolved my issue.
http://systemcentersolutions.wordpress.com/category/reporting/troubleshooting-reports/
Archive for the 'Troubleshooting Reports' Category
Reporting Services on a separate SQL Server
When splitting the Data Warehouse from Reporting Services, it seems you have
only one chance to get this right. If the install fails first time then the
roll back doesn't clean things up correctly and subsequent attempts to
install the Reporting Services component are doooooooomed to failure . and
ever increasing frustration.
This is due to the fact that failed instances of installation create an
invalid row in the Managmentgroup table in the OperationsManagerDW. To check
this, login to OperationsManagerDW and expand tables and look for the table
called "DBO.MANAGEMENTGROUP". Right click on that table and open the same
and copy the ManagementGroupGuid from the second column and run the below
query against OperationsManagerDW
"EXEC ManagementGroupRejectConnect 'MG GUID'" (Replace the MG GUID with the
guid that you copied from the DBO.Managementgroup" table.
Once it is executed, login with the SDK account and try with installing the
opsmgr reporting again.