Secondary Management Server install fails if Reporting is already installed with DW action account and RMS action account are the same
Published Feb 14 2019 08:22 PM 213 Views
First published on TECHNET on May 13, 2008

Issue: If you try to install a secondary Management Server (MS) in a scenario with Root Management Server(RMS) and Reporting installed with Data Warehouse(DW) action account and Root Management Server action account (default action account) is the same, the secondary Management Server setup rolls back with an error in the setup log:

Error from 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 OpsMgr Service Pack 1 setup if DW Action account is same as RMS action account we do not configure DW RunAs profile. So, when you attempt to install second MS we try to configure its DW RunAs profile with DW Action account by looking at RMS DW RunAs profile which is empty. (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).


Create a ‘Windows’ Run As Account with same domain user as that of RMS Action Account.

Associate this account to ‘Data Warehouse Account’ RunAs profile

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). Re-run Management Server setup.

Needless to say this will be fixed in Service Pack 2.


Version history
Last update:
‎Mar 11 2019 08:02 AM
Updated by: