PDA

View Full Version : BES 3.6 SP7 - Sending Fails with 0x80070005


Shinedog
10-11-2007, 02:24 PM
We are experiencing a real strange problem lately with our BES server running 3.6 SP7 with Exchange 2003 SP2. Sporadically users will get a message on the handhelds saying the mail fails to send. In the event viewer we have the following errors when this occurs:


{email.address@<hidden>} *** MAPI *** MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed.

followed by:

{email.address@<hidden>} Send() failed: ERR_SUBMIT_MAIL, Tag=1751275837

In the BES log files, we have these errors at the same time:

[40700] (10/10 17:49:07):{0xE70} {email.address@<hidden>} Receiving packet from device, size=226, TransactionId=842692997, Tag=1751275837, content type=CMIME, cmd=0x3
[30112] (10/10 17:49:07):{0xE70} {email.address@<hidden>} Receiving message from device, RefId=2133884076, Tag=1751275837, TransactionId=842692997
[40291] (10/10 17:49:07):{0xE70} {email.address@<hidden>} Refers to original message, RefId=-49791081
[40182] (10/10 17:49:07):{0xE70} {email.address@<hidden>} *** MAPI *** MAPIMailbox::RefIDtoEntryID - Found RefId=-49791081.
[20265] (10/10 17:49:07):{0xE70} {email.address@<hidden>} *** MAPI *** MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed.
[41169] (10/10 17:49:07):{0xF10} GetMDSStats: no data for BESSERVER
[20000] (10/10 17:49:07):{0xE70} {email.address@<hidden>} Send() failed: ERR_SUBMIT_MAIL, Tag=1751275837
[40277] (10/10 17:49:07):{0xE70} {email.address@<hidden>} Sending message error to device for message 2133884076
[40583] (10/10 17:49:07):{0xE70} {email.address@<hidden>} Sending message to device, Size=86, Tag=4762050, TransactionId=-956132413
[40279] (10/10 17:49:07):{0xE70} {email.address@<hidden>} SubmitToRelaySendQ, Tag=4762050

These errors will occur for user for a while but magically will clear themselves usually within an hour. It does not happen to all users at the same time and its really random as to who it happens and when.

In searching around for an answer, it appears to be the SendAs problem caused by that Exchange hotfix and we do have a later version of the store.exe. However, we have checked and double-checked the SendAs permissions for the BESAdmin account on the accounts that are known to have the problem and they are fine. The users in question are just regular users, not in protected groups or AdminSDHolders.

Not really sure where else to go here. The only thing that changed around the time that it "broke" is that we added a new Exchange server on the other side of a VPN connection. It does not hold info stores and resides in a separate routing group within the same organization. This new server uses the Lotus Notes connector to bridge in a Domino server.

Any ideas?