The MOM agent or the MOM server does not start, and event 9029 is logged in Microsoft Operations Manager 2005 (883347)
The information in this article applies to:
- Microsoft Operations Manager 2005
SYMPTOMSIn Microsoft Operations Manager (MOM) 2005, the MOM agent or the MOM server does not start, and the following event is logged in the Application event log:Event Type: Error
Event Source: Microsoft Operations Manager
Event Category: MOM Server
Event ID: 9029
Description:
The Microsoft Operations Manager service (MOMService.exe) was unable to run under the supplied credentials. Please use the SetActionAccount utility to set an action account which meets the guidelines documented in the Microsoft Operations Manager documentation.CAUSEThis problem may occur if any one or more of the following conditions are true: - A domain controller is not available to perform the logon.
- The action account is disabled or deleted.
- The action account's password has expired.
- The action account that the MOM service uses does not have permissions to log on locally. By default, only administrator accounts automatically receive Allow Logon Locally permissions on domain controllers. The account that is used by the MOM service must be able to log on locally to the computer.
RESOLUTIONTo resolve this problem, make sure that a domain controller is available on the network, that the action account is active, and that the action account's password has not expired, and that the action account that MOM uses has Allow Logon Locally permissions. To make sure that the action account has Allow Logon Locally permissions, follow these steps: - Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
- Right-click the domain object, and then click Properties.
- On the Group Policy tab, click the domain policy, and then click Edit.
- Expand Computer Configuration\Windows Settings\Security Settings\Local Policies, and then click User Rights Assignment.
- Double-click Allow log on locally, and then click Add User or Group.
- Type the user account, click OK, and then click OK.
- Quit Group Policy Object Editor.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 7/8/2005 |
---|
Keywords: | kbtshoot kbService kberrmsg kbEvent kbUser kbSecurity KB883347 kbAudITPRO |
---|
|