Here is another interesting problem I came across today. I had a lot of trouble installing SCOM Reporting on SQL 2008 R2, running on Windows 2008 R2. If you can imagine this setup.
Server 1 = RMS Server
Server 2 = OpsMgr DB
Server 3 = Data Warehouse DB + SQL Reporting Services
All servers are running Windows 2008 R2, and all SQL Database servers are running SQL 2008 R2. When installing SCOM Reporting, the Data Writer and Data Reader accounts were both domain service accounts.
Now here was the problem. Every time I would go to install SCOM Reporting, the installation with fail when attempting to connect to the management group with the following messages.
The setup wizard was interrupted before Operations Manager 2007 R2 could be installed. Your system has not been modified. To complete installation at another time, please run setup again.

After I click Finish, I get this message:
The setup failed. Do you want to open the setup log file (search for “value 3″ in the file for locating failure)?

Searching the log file for “value 3″ revealed several errors, however the first instance of “value 3″ in the log file looked like this….
2011-04-14T15:44:36.4234862+10:00 Error: ManagementGroupDisconnectHelper error: ManagementGroupConnectOrDisconnectHelper: LogonUser failed with error code 1385.
2011-04-14T15:44:36.4283692+10:00 Error: StackTrace: at
Microsoft.Reporting.Setup.ReportingManagedCAs.ManagementGroupDisconnectHelpe(Session session, String sqlServer, String databaseName,
string domain, String user, String password, String mgGuid, String mgDefaultName)
2011-04-14T15:44:36.4293458+10:00 Debug: ManagementGroupConnectHelper: Prepare connect MG SCOM_Management_Group
2011-04-14T15:44:37.5436464+10:00 Error: ManagementGroupConnectOrDisconnect error: Login specified as Management Group Writer Login
is already specified as writer login for another pending Management Group connect operation. Choose different login or confirm/reject previous
connect operation.
2011-04-14T15:44:37.5495060+10:00 Error: StackTrace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean
breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
String method)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at Microsoft.Reporting.Setup.ReportingManagedCAs.ManagementGroupConnectHelper(Session session, String sqlServer, String databaseName,
String domain, String user, String password, String logOnName, String mgGuid, String mgDefaultName)
at Microsoft.Reporting.Setup.ReportingManagedCAs.ManagementGroupConnectOrDisconnect(Session session)
CustomAction _ManagementGroupConnect returned actual error code 1603 (note this may not be 100% accurate if translation happened inside
sandbox)
MSI (s) (AC:80) [15:44:37:595]: NOTE: custom action _ManagementGroupConnect unexpectedly closed the hInstall handle (type MSIHANDLE)
provided to it. The custom action should be fixed to not close that handle.
Action ended 15:44:37: InstallFinalize. Return value 3.
Now you’ll see I’ve highlighted some bits. Even though the SCOM Reporting installation wizard tells you to look for “value 3″, the actual error is
before that bit of text in the log file – which you can see I’ve highlighted in yellow.
The Solution:
In my particular scenario, I had two different problems. Firstly, since I am working down in a secure environment, the infrastructure team had configured the service accounts with Deny Logon Locally. This was a problem. Even though there’s no documentation up on TechNet regarding this, the Data Writer account must have Log On Locally rights, along with local administrator rights to the Reporting Services server where you are installing it. If you’re unsure about what rights the Data Writer and Data Reader accounts need (and there are a few) – take a look at the spreadsheet here in Kevin Holman’s blog: http://blogs.technet.com/b/kevinholman/archive/2008/04/15/opsmgr-security-account-rights-mapping-what-accounts-need-what-privileges.aspx.
Once you’ve sorted out the correct permissions required for your service accounts – try the installation again. If it works, then that was your issue. If it doesn’t work, then you have the same problem I did and there is an extra step you need to do.
You may need to reject a Management Group from your Data Warehouse database. You will know if you need to do this by doing the following procedure. This is for SQL 2008 R2, but it should work if you have the same issue in SQL 2005 or SQL 2008. I’m assuming you’re an SQL administrator when you perform these tasks.
1. Open the SQL management console on your Data Warehouse database server, connecting to the correct instance.
2. Expand Databases -> OperationsManagerDW (or whatever your DW database is called) -> Tables.
3. Look for dbo.ManagementGroup -> right click -> Select Top 1000 Rows
4. If you have a pending management group, the ManagementGroupDefaultName field may contain the incorrect name of your management group. ConnectConfirmedDateTime will be NULL, and WriteLoginName will contain the name of the data writer account you’re trying to use. If this is your case, you need to reject this management group to give SCOM a chance of reinstalling it correctly.
To do this, copy the GUID out of the ManagementGroupGUID field. In the SQL Management Studio console, click on your data warehouse database, and start a New Query. Run the following query.
EXEC ManagementGroupRejectConnect ‘yourGUID’
Ensure your GUID is contained within ‘ ‘ quotes.
Execute the command, and it should clear the management group. Now have another try at installing SCOM Reporting. For me – this worked and ended several hours of frustration.