Event Type: Warning
Event Source: OnePoint Operations
Event Category: None
Event ID: 21248
Date: 07/08/2002
Time: 22:26:52
User: NT AUTHORITY\SYSTEM
Computer: DC
Description: The Agent was unable to contact any Consolidator.

The last attempt to connect to mom failed.

Details: No connection could be made because the target machine actively refused it.
--------Event Type: Warning
Event Source: OnePoint Operations
Event Category: None
Event ID: 21248
Date: 07/08/2002
Time: 22:26:52
User: NT AUTHORITY\SYSTEM
Computer: DC
Description: The Agent was unable to contact any Consolidator.

The last attempt to connect to mom failed.

Details: No connection could be made because the target machine actively refused it.

Contributed By: Mike Betts [MVP MOM]
Things to do:-

1. Restart Onepoint service on DCAM machine
2. Restart Onepoint on agent having this problem.

The message is basically saying that there is some sort of networking problem when the agent offers the consolidator information, so the problem could be either end. If you’re getting it on all agents then it is probably on the consolidator.

Contributed By: Nissim Ben-Maor [MVP MOM]
Do you have the DCAM listed in the Managed Computer Rules for either itself or other DCAMs? The reason I ask is that if the DCAM is listed as an agent it may overlay registry entries that lead the DCAM to believe it is simply an agent and refuse connections from other agents connection attempts.

The key in question can be found at:

HKLM\Mission Critical Software\OnePoint\Configurations\"config group name"\MCSApplications\Operations Agent.

This key should not exists on a DCAM.

Also the value of

HKLM\Mission Critical Software\OnePoint\Configurations\"config group name"\Operations\Agent\Consolidator\PeerCount

key value is set to 0 on the DCAM.