OpsMgr 2007: Secondary Management Server install fails if Reporting is already installed and the DW action account and RMS action account are the same


Here’s another great tip sent to me by Ritesh Grover on our OpsMgr team.  This one involves trying to setup a secondary management server and having it fail because the Data Warehouse (DW) action account and the RMS action account are the same so if this is something you’re running it check this out:


Issue: A Secondary Management Server install may fail if Reporting is already installed and the Data Warehouse (DW) action account and the RMS action account are the same.  When this happens the server install fails with value 3 and the setup rolls back at registering the management server.  You may also see this in the setup log file:

AddRunAsProfilesCA: Error: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index,
Stack: at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at System.Collections.Generic.List`1.get_Item(Int32 index)
at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.AddRunAsProfile(String profleGuid,
MonitoringObject hostedHealthService, ManagementGroup managementGroup, String currentActionUserDomain, String currentActionUserName)
at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.AddRunAsProfiles(Session session)

Cause: In the System Center Operations Manager 2007 Service Pack 1 (SP1) setup program, if the DW Action account is the same as the RMS action account we do not configure the DW RunAs profile. Because of this, when you attempt to install a second Management Server we try to configure its DW RunAs profile with the DW Action account by looking at the RMS DW RunAs profile but it is empty.

Note: This happens when default action account is same as DW action account and installation scenario is: RMS and Reporting is installed and then second MS is attempted to install.

Resolution: To resolve this issue follow the steps below:

  1. Create a ‘Windows’ Run As Account with same domain user as that of RMS Action Account.
  2. Associate this account to ‘Data Warehouse Account’ RunAs profile.
  3. Associate this account to ‘DW Configuration and Synchronization Reader Account’ profile (in SP1 this is called as ‘Reserved’, there would be three Reserved profiles in SP1, this one is third in the list).
  4. Re-run the Management Server setup.


Thanks Ritesh!

J.C. Hornbeck | Manageability Knowledge Engineer

Comments (2)

  1. Anonymous says:

    Hi, i have exactly the same issue, but itsa appeared then i uninstall and then was trying to install again my RMS, so your resolution is not working for me.

  2. Anonymous says:

    JC.  Thanks for the great post.  I do seem to have the same problem with the same cirumstances in an R2 installation.  Thing is, I've updated the above, but I use the Data Warehouse Action Account all over my management packs and I still get this error installing the server.  So, I'm extrapolating that anywhere I use that Account, it will cause the installation to fail with the index error.

    Question is, is there now a way that I can get a value into the Data Warehouse Action Account in R2, or am I still looking at replacing all of those references in order to get my server installed?

    Thanks much.


Skip to main content