If a Microsoft Operations Manager (MOM) 2005 agent cannot
communicate with a MOM 2005 Management Server, the MOM 2005 agent may
experience a deadlock situation. This symptom occurs if the MOM 2005 Management
Server shuts down or the network communication between the MOM 2005 agent and
the MOM 2005 management server is unavailable. The deadlock situation occurs while the MOM 2005 agent is trying to clear the
MOM 2005 agent queue after the communication is restored. Additionally, the following events are added to the Application log:
Event Type: Error
Event Source: Microsoft Operations Manager
Event Category: None
Event ID: 26009
Date: Date
Time: Time
User: UserName
Computer: ComputerName
Description:
The agent could not connect to the MOM Server ServerName.
Event Type: Information
Event Source: Microsoft Operations Manager
Event Category: None
Event ID: 26021
Date: Date
Time: Time
User: UserName
Computer: ComputerName
Description:
The agent has restored communication to ManagementServerName.
Event Type: Information
Event Source: Microsoft Operations Manager
Event Category: MOM Server
Event ID: 22062
Date: Date
Time: Time
User: UserName
Computer: ComputerName
Description:
The Server outgoing data processing has successfully resumed after being blocked.
Management Group: MOM2005
This problem occurs because of the method that is used to
process the backlog. This problem occurs when the scripts are putting
lots of data in the queue during the processing. If the queue is full and the
communication is restored, the MOM 2005 agent tries to clear the backlog.
Therefore, the scripts cannot put the data in the queue when the queue is full.
Hotfix information
This hotfix is included in hotfix 906858. No separate hotfix exists for this issue. If you experience this problem, apply the hotfix that is described in the following Microsoft Knowledge Base article:
906858Â
(http://kbalertz.com/Feedback.aspx?kbNumber=906858/
)
The MOM agent may generate event ID 25257 in MOM 2005
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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
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, contact 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
You must install this hotfix on each computer that meets either of
the following conditions:
- The computer hosts a MOM
Management Server.
- The computer hosts a manually installed MOM 2005 agent.
Restart requirement
You do not have to restart the computer after you apply this
hotfix. However, this hotfix restarts the MOM service.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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.
MOM 2005Collapse this tableExpand this table
| File name | File version | File size | Date | Time | Platform |
|---|
| Mom2005-rtm-kb906858-x86-ia64-enu.msi | Not Applicable | 4,090,368 | 15-Nov-2005 | 17:31 | Not Applicable |
| Momactions.dll | 5.0.2749.28 | 892,928 | 03-Nov-2005 | 17:17 | x86 |
| Momdbconnector.dll | 5.0.2749.28 | 1,524,224 | 03-Nov-2005 | 17:17 | x86 |
| Momengine.dll | 5.0.2749.28 | 1,624,064 | 03-Nov-2005 | 17:17 | x86 |
| Momengine.tlb | Not Applicable | 1,784 | 13-Aug-2004 | 11:43 | Not Applicable |
| Momforwardingconnector.dll | 5.0.2749.28 | 355,840 | 03-Nov-2005 | 17:17 | x86 |
| Momhost.exe | 5.0.2749.28 | 54,272 | 03-Nov-2005 | 17:17 | x86 |
MOM 2005 with Service Pack 1Collapse this tableExpand this table
| File name | File version | File size | Date | Time | Platform | SP requirement |
|---|
| Mom2005-sp1-kb906858-x86-ia64-enu.msi | Not Applicable | 1,399,808 | 13-Dec-2005 | 14:49 | Not Applicable | SP1 |
| Momactions.dll | 5.0.2911.1 | 900,336 | 02-Dec-2005 | 12:59 | x86 | SP1 |
Installation instructions
To install this hotfix, follow these steps:
- Copy the MOM2005-RTM-KB906858-X86-ENU.MSI file to a local
folder or to a network shared folder. If you use a network shared folder, make
sure that you can access the folder from the computers that require this
hotfix.
- Log on as an administrator to one of the computers that
requires this hotfix.
- Run MOM2005-RTM-KB906858-X86-ENU.MSI on each
computer that meets the predefined criteria. You can run the file at
a command prompt, or you can run the file by using Windows
Explorer.
- Repeat steps 2 and 3 on each computer that requires
this hotfix.
To install this hotfix in your MOM environment:
- Manually install this hotfix to each MOM 2005 server in
your MOM management groups.
- To install this hotfix for the MOM 2005 agent component,
use the following methods:
- Use the MOM 2005 Administrator Console to install this
hotfix to MOM 2005 agents with Control Level = Full. The list of the MOM 2005 agents that can be automatically
updated is shown in the Microsoft Operations Manager (ServerName)\Administration\Computers\Pending Actions folder.
- Manually install this hotfix on each MOM 2005 agent
that is set with Control Level = None. These agents are listed in the Microsoft Operations Manager (ServerName)\Administration\Computers\Agent-managed Computers folder.
- For MOM 2005 agents that were manually installed with Control Level = Full after this hotfix was installed to the MOM 2005 server, use one of these methods. Either manually install the hotfix to the MOM 2005 agents or follow these
steps to use the MOM 2005 server to install this hotfix:
- Make sure that the manual installation of the MOM
2005 agents is approved through the Pending Actions folder in the MOM 2005 Administrator Console.
- Click the Agent-managed Computers folder in the MOM 2005 Administrator Console, right-click the MOM
2005 agent in the right pane, and then click Update Agent Settings.
Microsoft has confirmed that this is a bug in the Microsoft
products that are listed in the "Applies to"
section.
For more information about the standard terminology that is used to describe Microsoft software updates, 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