Pavleck.NET

This particular issue happens a lot on Domain Controllers, and especially DCs that you’re running as a gateway server. In the OpsMgr event log, you’ll receive a lot of events from the Health Service Script source with event IDs 1 and 1000.

OpsMgr Event ID 1000 Warning from Health Service Script

The text of the alert is:

Event Type:    Warning
Event Source:    Health Service Script
Event Category:    None
Event ID:    1000
Date:        2/13/2009
Time:        12:18:16 PM
User:        N/A
Computer:    BADDC01
Description:
AD Database and Log : The script ‘AD Database and Log’ failed to create object ‘McActiveDir.ActiveDirectory’.
The error returned was: ‘ActiveX component can’t create object’ (0×1AD)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

and

OpsMgr Event ID 1 Warning from Health Service Script

the text of which is:

Event Type:    Warning
Event Source:    Health Service Script
Event Category:    None
Event ID:    1
Date:        2/13/2009
Time:        12:18:09 PM
User:        N/A
Computer:    BADDC01
Description:
AD Op Master Response : The script ‘AD Op Master Response’ failed to create object ‘McActiveDir.ActiveDirectory’.  This is an unexpected error.
The error returned was: ‘ActiveX component can’t create object’ (0×1AD)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Cause: For whatever reason, the Active Directory helper object is not being installed as part of the active directory management pack.

Solution: Install the helper object OOMADs.msi. This can be found in 1 of 2 places.
First, look in the install directory of OpsMgr on the server with the issue – typically that would be C:\Program Files\System Center Operations Manager 2007\HelperObjects

If it’s not there, then you can also find it on the install media under \HelperObjects\<ARCH> (Where arch is amd64, i386 or ia64).
Restart your agent, and it should clean itself up.