Consider the following scenario. You install a Microsoft Operations Manager (MOM) 2005 agent on
a domain controller that is running a 64-bit server version of Windows. Then, you install a Microsoft System Center Operations Manager 2007
Service Pack 1 (SP1) agent on the same domain controller. In this scenario, you
receive many alerts in the MOM 2005 Operations Console.
These alerts
are issued from the MOM Active Directory Management Pack. For example, you may
receive alerts that resemble the following:
Name: Script Based Test Failed to Complete
Description:
While running 'AD General Response' the following consecutive errors were encountered:
Failed to create object 'McActiveDir.ActiveDirectory'.This is an unexpected error.
The error returned was 'The specified module could not be found.' (0x8007007E)
Failed to create object 'McActiveDir.ActiveDirectory'.This is an unexpected error.
The error returned was 'The specified module could not be found.' (0x8007007E)
Failed to create object 'McActiveDir.ActiveDirectory'.This is an unexpected error.
The error returned was 'The specified module could not be found.' (0x8007007E)
Failed to create object 'McActiveDir.ActiveDirectory'.This is an unexpected error.
The error returned was 'The specified module could not be found.' (0x8007007E)
A message will be generated when the script succeeds which has details of all the errors that have occurred. Look for a message from AD General Response with ID = 21001
When you install an Operations Manager 2007 Service Pack 1
(SP1) agent on a computer that already has a MOM 2005 agent installed, the
Operations Manager 2007 SP1 agent replaces the 32-bit Active Directory helper
object (OOMADS) that is used by the MOM 2005 agent. Specifically, this 32-bit Active Directory helper object is replaced with a 64-bit Active Directory
helper object. Therefore,
the MOM 2005 agent cannot call the 64-bit Active Directory helper
object.
Update Information
To resolve this problem, obtain the latest version of Microsoft System Center Operations Manager 2007. For more information, refer to this Microsoft Web site:
http://www.microsoft.com/systemcenter/operationsmanager/en/us/how-to-buy.aspx
(http://www.microsoft.com/systemcenter/operationsmanager/en/us/how-to-buy.aspx)
Hotfix information
A
supported hotfix is available from Microsoft. However, this hotfix is intended
to correct only the problem that is described in this article. Apply this
hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download
available" section at the top of this Knowledge Base article. If this section
does not appear, submit a request to Microsoft Customer Service and Support to
obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required,
you might have to create a separate service request. The usual support costs
will apply to additional support questions and issues that do not qualify for
this specific hotfix. For a complete list of Microsoft Customer Service and
Support telephone numbers or to create a separate service request, visit the
following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for
which the hotfix is available. If you do not see your language, it is because a
hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must have System Center Operations
Manager 2007 Service Pack 1 installed.
Restart requirement
You do not have to restart the computer after you apply this
hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
Preinstallation instructions
Before you apply this hotfix on a computer that hosts
the MOM 2005 agent and the Operations Manager 2007 SP1 agent, you must first remove those
agents from the computer. Additionally, you must remove the Active Directory
helper object by using the
Add or Remove Programs item in Control Panel.
Installation instructions
You must apply this hotfix on each computer that hosts one of the
following components or roles:
- Operations Manager Root Management Server
- Operations Manager Management Server
- Operations Manager agent that was manually
installed
To apply the hotfix, follow these steps:
- Copy the following file from the hotfix package to a local
folder or to a shared folder:
SystemCenterOperationsManager2007-SP1-KB956184-IA64-X64-ENU.msi
- Run the file that you copied in step 1.
- On the Select Installation Folder page of
the installation wizard, you can specify a folder in which the hotfix will be
installed. By default, this hotfix is installed in the following location:
%ProgramFiles%\System Center 2007 Hotfix Utility\Q956184
- Click Everyone.
- Click Next two times.
When
you do this, an updated Oomads.msi file is saved in
the following folders:
- An x64 folder for x64 platforms
- An ia64 folder for Itanium
platforms
You
can opt to deploy an Operations Manager 2007 SP1 agent by using the Discovery
Wizard or to manually install the Operations Manager 2007 agent and the Oomads.msi
package.
To deploy an Operations Manager 2007 SP1 agent by using the
Discovery Wizard, follow these steps:
- Install Operations Manager 2007 SP1 and the latest Active
Directory Management Pack if they are not installed yet.
- On the computer that hosts Operations Manager 2007 Root
Management Server or Operations Manager 2007 Management Server, locate the
Oomads.msi file in the following folder:
%ProgramFiles%\System Center Operations Manager 2007\AgentManagement\platform
Note The platform placeholder represents
the platform version of the Active Directory helper object. - Replace the x64 version and the IA-64 version of the
Oomads.msi file with the Oomads.msi file that was saved in the Q956184
folder.
- Run the Discovery Wizard, and deploy the agent to the
monitored domain controllers.
To manually install an Operations Manager 2007 agent and the
Oomads.msi package, follow these steps:
- Copy the MOMAgent.msi file to each monitored domain
controller from the Agent\platform folder on the Operations Manager 2007 installation
media.
- Copy the updated Oomads.msi file from the Q956184 folder to
each monitored domain controller.
- On each monitored domain controller, run the MOMAgent.msi
file and the Oomads.msi file.
- Verify that the Oomads.dll file is installed in the
following folder:
%ProgramFiles%\Common Files\Active Directory Management Pack Objects
File information
The English version of this hotfix has the file
attributes (or later file attributes) that are listed in the following table.
The dates and times for these files are listed in Coordinated Universal Time
(UTC). When you view the file information, it is converted to local time. To
find the difference between UTC and local time, use the
Time
Zone tab in the
Date and Time item in Control
Panel.
System Center Operations Manager 2007 Service Pack 1 agent for IA-64 platform
Collapse this tableExpand this table
| File name | File version | File
size | Date | Time | Platform |
|---|
| Oomads.dll | 6.0.5734.0 | 179,200 | 12-Mar-2007 | 04:06 | IA-64 |
System Center Operations Manager 2007 Service Pack 1 agent for x64 platform
Collapse this tableExpand this table
| File name | File version | File
size | Date | Time | Platform |
|---|
| Oomads.dll | 6.0.5734.0 | 87,040 | 12-Mar-2007 | 04:02 | x64 |
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. This problem was first corrected in Microsoft System Center Operations Manager 2007 R2.
For a list of issues that are fixed in Microsoft System Center Operations Manager 2007 R2, refer to the following article in the Microsoft Knowledge base:
971410Â
(http://kbalertz.com/Feedback.aspx?kbNumber=971410/
)
List of issues that are fixed in System Center Operations Manager 2007 R2
For more information about
software update terminology, click the following article number to view the
article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates