Microsoft KB Archive/936219

= Error message when you try to install System Center Operations Manager 2007 Reporting: &quot;The wizard was interrupted before Operations Manager 2007 could be installed&quot; =

Article ID: 936219

Article Last Modified on 11/6/2007

-

APPLIES TO


 * Microsoft System Center Operations Manager 2007

-



SYMPTOMS
When you try to install Microsoft System Center Operations Manager 2007 Reporting, the installation fails and rolls back. Additionally, you receive the following error message:

The wizard was interrupted before Operations Manager 2007 could be installed.



CAUSE
This problem occurs if you configure Operations Manager 2007 to use the Local System account as the OpsMgr SDK Service account. In this configuration, the installation queries Active Directory Domain Services (AD DS) for the computer account that is associated with the root management server. In a large Active Directory domain, this query may time out before AD DS returns the queried data.



RESOLUTION
A fix for this problem is included in the hotfix that is described in the following Microsoft Knowledge Base article:

936481 You cannot install the System Center Operations Manager 2007 Reporting feature in a disjointed namespace environment

Installing hotfix 936481 will correct this problem.



WORKAROUND
To work around this problem, configure the OpsMgr SDK Service to use a domain account instead of the Local System account. After you install Operations Manager 2007 Reporting, you can configure the OpsMgr SDK Service to use the Local System account. Be aware that you must configure the OpsMgr Config Service to use the same account as the OpsMgr SDK Service.

For more information about how to change the service accounts, click the following article number to view the article in the Microsoft Knowledge Base:

936220 How to change the credentials for the OpsMgr SDK Service and for the OpsMgr Config Service in Microsoft System Center Operations Manager 2007



MORE INFORMATION
To verify that this problem occurs because the query times out, you can examine the Microsoft Windows Installer log that the Operation Manager 2007 Reporting Setup program generates. When you perform an interactive installation, verbose MSI logs are written to the %temp% folder of the current user. These log files follow the MomReporting .log name pattern. In this name pattern,  is a number that increments every time that you run the Operation Manager 2007 Reporting installer file. To examine the log file, follow these steps:  Open the %temp% folder, and then open the MomReporting .log file in Notepad.

Note The file that has the largest  number is the most recent file.  Search for the following text: SetPropertiesToManagementServerActionAndSDKAccountCA error 

The complete text that contains the error resembles one of the following samples:

Sample 1 SetPropertiesToManagementServerActionAndSDKAccountCA error: Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException : The time limit for this request was exceeded.

MSI (s) (C0!94) [18:11:15:989]: PROPERTY CHANGE: Adding UnableToGetUserNameFromManagementServerActionAccount property. Its value is 'SetPropertiesToManagementServerActionAndSDKAccountCA error: Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException : The time limit for this request was exceeded. '. MSI (s) (C0!94) [18:11:15:989]: PROPERTY CHANGE: Adding UnableToGetUserNameFromManagementServerSDKAccount property. Its value is 'SetPropertiesToManagementServerActionAndSDKAccountCA error: Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException : The time limit for this request was exceeded. '. StackTrace:   at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex) at Microsoft.EnterpriseManagement.DataAbstractionLayer.AdministrationOperations.GetServiceAccount at Microsoft.EnterpriseManagement.Administration.ManagementGroupAdministration.GetServiceAccount at Microsoft.Reporting.Setup.ReportingManagedCAs.GetManagementServerSDKAccount(String momServerFQDN, String& sdkServiceDomainAndAccount) at Microsoft.Reporting.Setup.ReportingManagedCAs.SetPropertiesToManagementServerActionAndSDKAccountCA(Session session) Action ended 18:11:16: _SetPropertiesToManagementServerActionAndSDKAccountCA. Return value 3. Action ended 18:11:16: INSTALL. Return value 3. Sample 2 SetPropertiesToManagementServerActionAndSDKAccountCA error: System.DirectoryServices.ActiveDirectory.ActiveDirectoryObjectNotFoundException : The specified domain does not exist or cannot be contacted. MSI (s) (B4!84) [09:28:29:505]: PROPERTY CHANGE: Adding UnableToGetUserNameFromManagementServerActionAccount property. Its value is 'SetPropertiesToManagementServerActionAndSDKAccountCA error: System.DirectoryServices.ActiveDirectory.ActiveDirectoryObjectNotFoundException : The specified domain does not exist or cannot be contacted.'. MSI (s) (B4!84) [09:28:29:505]: PROPERTY CHANGE: Adding UnableToGetUserNameFromManagementServerSDKAccount property. Its value is 'SetPropertiesToManagementServerActionAndSDKAccountCA error: System.DirectoryServices.ActiveDirectory.ActiveDirectoryObjectNotFoundException : The specified domain does not exist or cannot be contacted.'. StackTrace:   at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context) at Microsoft.Reporting.Setup.ReportingManagedCAs.GetSAMAccountName(String machine) at Microsoft.Reporting.Setup.ReportingManagedCAs.GetManagementServerSDKAccount(String momServerFQDN, String& sdkServiceDomainAndAccount) at Microsoft.Reporting.Setup.ReportingManagedCAs.SetPropertiesToManagementServerActionAndSDKAccountCA(Session session) Action ended 9:28:29: _SetPropertiesToManagementServerActionAndSDKAccountCA. Return value 3. Action ended 9:28:29: INSTALL. Return value 3. Sample 3 SetPropertiesToManagementServerActionAndSDKAccountCA error: Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException : The specified domain does not exist or cannot be contacted. MSI (s) (58!68) [12:10:53:565]: PROPERTY CHANGE: Adding UnableToGetUserNameFromManagementServerActionAccount property. Its value is 'SetPropertiesToManagementServerActionAndSDKAccountCA error: Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException : The specified domain does not exist or cannot be contacted.'. MSI (s) (58!68) [12:10:53:565]: PROPERTY CHANGE: Adding UnableToGetUserNameFromManagementServerSDKAccount property. Its value is 'SetPropertiesToManagementServerActionAndSDKAccountCA error: Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException : The specified domain does not exist or cannot be contacted.'. StackTrace: at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex) at Microsoft.EnterpriseManagement.DataAbstractionLayer.AdministrationOperations.GetServiceAccount at Microsoft.EnterpriseManagement.Administration.ManagementGroupAdministration.GetServiceAccount at Microsoft.Reporting.Setup.ReportingManagedCAs.GetManagementServerSDKAccount(String momServerFQDN, String& sdkServiceDomainAndAccount) at Microsoft.Reporting.Setup.ReportingManagedCAs.SetPropertiesToManagementServerActionAndSDKAccountCA(Session session) Action ended 12:10:53: _SetPropertiesToManagementServerActionAndSDKAccountCA. Return value 3. Action ended 12:10:53: INSTALL. Return value 3.

Keywords: kberrmsg kbtshoot kbexpertiseinter kbprb KB936219

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.