7 Days of KB Articles ... Part 5 of 7 (Unable to send email after GC / Ex Reboot)
Posted 08-22-2009 at 04:00 AM by hdawg
So, for me I always recommend reboots of a BlackBerry Enterprise Server when there is a scheduled restart / failover of an Exchange or Global Catalog server (heck, BES needs both to work!). Unfortunately, not everyone can do this, and reboots / restarts / failovers aren't always planned.
BES isn't an Exchange cluster-aware application, so it can't effectively handle failovers like we'd all want it to ... well at least until Exchange 2010 (aka E14) is released and then with all MAPI traffic going through a CAS, BES should be able to handle the failovers ... well ... I hope and will keep my fingers crossed at least.
... and the KB:
KB11103 - Some BlackBerry smartphone users are unable to send email messages after the Microsoft Exchange Server or the Global Catalog servers were restarted
Environment
<content>
<hr class="section">
Overview
Some existing BlackBerry smartphone users are unable to send email messages. The application log will display the following entries:
Event Type: Warning
Event Source: BlackBerry Messaging Agent BES Agent 1
Event Category: None
Event ID: 20154
Date: 11/16/2006
Time: 14:27:02 PM
User: N/A
Computer: BES
Description:
The description for Event ID ( 20154 ) in Source ( BlackBerry Messaging Agent BES Agent 1 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: User not started.
Event Type: Warning
Event Source: BlackBerry Messaging Agent BES Agent 1
Event Category: None
Event ID: 20265
Date: 11/16/2006
Time: 14:27:06 PM
User: N/A
Computer: BES
Description:
The description for Event ID ( 20265 ) in Source ( BlackBerry Messaging Agent BES Agent 1 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: {@<domain>} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80004005) failed.
</domain>
<hr class="section">
Cause
<content> The Microsoft® Exchange Server has been restarted, which disrupts the Messaging Application Programming Interface (MAPI) connections made from the BlackBerry Enterprise Server.
</content>
<hr class="section">
Resolution
Important: Restarting the BlackBerry Enterprise Server will delay email message delivery to BlackBerry smartphones. For more information, see KB04789. Restart the BlackBerry Enterprise Server to restore correct MAPI connections.
Whenever one or more Microsoft Exchange messaging servers or Global Catalog servers have been restarted, the BlackBerry Enterprise Server should also be restarted.
BES isn't an Exchange cluster-aware application, so it can't effectively handle failovers like we'd all want it to ... well at least until Exchange 2010 (aka E14) is released and then with all MAPI traffic going through a CAS, BES should be able to handle the failovers ... well ... I hope and will keep my fingers crossed at least.
... and the KB:
KB11103 - Some BlackBerry smartphone users are unable to send email messages after the Microsoft Exchange Server or the Global Catalog servers were restarted
Environment
<content>
- BlackBerry® Enterprise Server for Microsoft® Exchange
- BlackBerry smartphone
<hr class="section">
Overview
Some existing BlackBerry smartphone users are unable to send email messages. The application log will display the following entries:
Event Type: Warning
Event Source: BlackBerry Messaging Agent BES Agent 1
Event Category: None
Event ID: 20154
Date: 11/16/2006
Time: 14:27:02 PM
User: N/A
Computer: BES
Description:
The description for Event ID ( 20154 ) in Source ( BlackBerry Messaging Agent BES Agent 1 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: User not started.
Event Type: Warning
Event Source: BlackBerry Messaging Agent BES Agent 1
Event Category: None
Event ID: 20265
Date: 11/16/2006
Time: 14:27:06 PM
User: N/A
Computer: BES
Description:
The description for Event ID ( 20265 ) in Source ( BlackBerry Messaging Agent BES Agent 1 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: {@<domain>} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80004005) failed.
</domain>
<hr class="section">
Cause
<content> The Microsoft® Exchange Server has been restarted, which disrupts the Messaging Application Programming Interface (MAPI) connections made from the BlackBerry Enterprise Server.
</content>
<hr class="section">
Resolution
Important: Restarting the BlackBerry Enterprise Server will delay email message delivery to BlackBerry smartphones. For more information, see KB04789. Restart the BlackBerry Enterprise Server to restore correct MAPI connections.
Whenever one or more Microsoft Exchange messaging servers or Global Catalog servers have been restarted, the BlackBerry Enterprise Server should also be restarted.
Total Comments 0
