<div>
I've also found that setting an override to the 'Max Missed Runs' has addressed my issue.
</div>


I've also found that setting an override to the 'Max Missed Runs' has addressed my issue.

<div>
<div class="content wysiwyg-content">
Frequently yet intermittently with no discernable pattern we have SCOM &quot;Mailflow monitor (receiver) reported a problem&quot; critical alerts go off only to resolve themselves 15 minutes later when the next mail flow message is sent and recieved successfully.<br />
<br />
Looking at the Operations Manager event log on the sending exchange server, there is always a Health Service Script Event ID 9562 when these messages fail:<br />
<br />
Exchange MOM - MFS : Mail Flow: operation timed out while sending message from EXC12MOM to EXC14MOM<br />
CPU is running at 1.24 percent.<br />
<br />
Nothing else is going on in the appliation, security &amp;&nbsp;system event log during these events. &nbsp;I've adjusted the thresholds to permit a lot of time to pass (10 minutes) before the mail flow warning is considered delayed. &nbsp;From everything I can tell, these messages just aren't being sent for some unknown reason. &nbsp;<br />
<br />
SCOM 2007, Exchange 2003 MP 6.0.6387.0.<br />
<br />
What is causing these 9562 events and how can I determine what is stopping these messages from being sent by the Mail Flow health monitoring scripts?
</div>
</div>


Frequently yet intermittently with no discernable pattern we have SCOM "Mailflow monitor (receiver) reported a problem" critical alerts go off only to resolve themselves 15 minutes later when the next mail flow message is sent and recieved successfully.

Looking at the Operations Manager event log on the sending exchange server, there is always a Health Service Script Event ID 9562 when these messages fail:

Exchange MOM - MFS : Mail Flow: operation timed out while sending message from EXC12MOM to EXC14MOM
CPU is running at 1.24 percent.

Nothing else is going on in the appliation, security & system event log during these events.  I've adjusted the thresholds to permit a lot of time to pass (10 minutes) before the mail flow warning is considered delayed.  From everything I can tell, these messages just aren't being sent for some unknown reason.  

SCOM 2007, Exchange 2003 MP 6.0.6387.0.

What is causing these 9562 events and how can I determine what is stopping these messages from being sent by the Mail Flow health monitoring scripts?

SCOM Mail Flow Event IDs 9562:  What causes these?

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Software is any set of instructions that directs a computer to perform specific tasks or operations. Computer software consists of programs, libraries and related non-executable data (such as documentation). Computer software is non-tangible, contrasted with computer hardware, which is the physical component of computers. Software written in a machine language is known as "machine code". However, in practice, software is usually written in high-level programming languages than machine language. High-level languages are translated into machine language using a compiler or interpreter or a combination of the two.

Software

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.