"BlackBerry Messaging Agent BLKBSRV01 Agent 1 (Application Event Log on BLKBSRV01): 11/28/2005 16:50:29 (AFFF4E20) -> {user.name@mm-games.com} Send() failed: ERR_SUBMIT_MAIL, Tag=38644"

Can anybody tell me what's causing the failure? I've googled but get no results. The user is still able to receive to the handheld, but is unable to send. I get these sporadically for mutiple users.

BES 4.0.3, Exchange 2k3 (Cluster).

Does this fail for all users or one in particular?

Sporadically for several users. I also receive the following warning messages:

BlackBerry Messaging Agent BLKBSRV01 Agent 1 (Application Event Log on BLKBSRV01): 11/28/2005 20:21:01 (AFFF4F29) -> {user.name@mm-games.com} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80004005) failed.

I've never seen either of those. Are there any other 0x800xxxxx errors in the logs?

0x80004005 recurs quite often, but there are no other errors. Only 4 of 10 users are affected. There have been no changes to the cluster, and running handheldcleanup -u on the server mitigated the issue for about a day, then went right back to failing.

What version of Emsmdb32.dll are you running on your BES? It's in the windows\system32 directory.

Along with that are you seeing any mapi out of memory errors near these messages

No out of memory errors. Not sure on the version, but the date on the file is 4/2/2004 (server was not built until a few months ago), and the size is 953kb.

...other source.

I got this error after applying the newest exchange patches; after that, we came on with the "send-as" Workaround. Everything works fine, except for one user; he can receive Mails on his handheld, but if he tries to send one via his SonyEricsson P910 i have this error twice and the following in the eventlog:
BlackBerry Messaging Agent <Blackberryserver> Agent 1
ID 20000
{UserMailAdress} Send() failed: SUCCESS, Tag=137460

everyone has the same problem and can help?

This is related to the MS Hotfix,revoking the Send As
Read MS KB 912918

Oh and also read RIM KB Article Number: KB-04707

I've already done the steps mentioned in these 2 articles.
that worked for all the clients except the one mentioned above. He can receive messages but cant send any.

thanks for any replies

Is the above user member of any Windows Protected Groups

Eg Domain Admins,Schema Admins,Enterprise Admins etc?

actually not
but we discovered, that somehow inheritation was disabled by this user; when i enabled it via my workstation (mmc) it looked like everything was ok, but after a short time, my made settings were resetted. When i changed the settings via logon at a domain-controller i discovered that these settings were not resetted any more.
This was the problem, now he's able to send , but i think his AD-User is bugged
thanks for the replies anyway
kind regards

I am having this issue with a couple users in the Domain Admins group. they can receive but not send after SP2 was installed (effecting me also). All my other users can send and receive just fine.

I know I am just overlooking something somewhere, but am at wit's end...

Thank you

I discovered, that the one user, who had this prob, somehow was in an Builtin Admin Group with no admin rights.
With deleting his membership in this group this problem was solved.

If you have some admin users that cannot be removed from AdminSD groups, just make an blackberry - dummy - user for the mailboxes of these users, like described in the MS KB Article No. 912918, chapter "Special rules for adminSDHolder protected Accounts.

Or, if possible, you create a new user with all the AD-rights necessary, assign the fuill mailbox rights of the old users mailbox and delete all the Active Directory Memberships the old user doesnt need any more.

Kind regards,

I saw this with a few users and it looked to me like a haywire Agent process. I stopped the dispatcher service and restarted it and the problem was resolved instantly. In my evironment, all the affected users were on the same server and the same BES Agent was responsible for them.

The EventID associated with it was:

EventID: 20265
Source: BlackBerry Message Agent BESNAME Agent X

{user@domain.com} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80004005) failed


I'm considering setting up a MOM alert that monitors for this EventID and restarts the dispatcher service if it is logged x times in x minutes.

So, I had the same issue.

Turns out that you must have the particular users with this problem inheriting permissions in Active Directory.

If you cannot login to a workstation on your domain as tha BESAdmin account (or your BBES services account login), then send a message with Outlook while attached to that user....it won't work.

Verify that the user in question is inheriting permissions within AD.

Good luck.

I am having this issue for just one user and it happened a few weeks back. The Send As is not the problem as I'm able to send mail in Outlook when logged into the user's profile. The user can respond to meeting invitations since they use CDO, but he can't draft or reply to messages since they get rejected on the handheld when attempting to send.

The BES Agent log shows(personal info removed):

[20000] (02/13 14:33:48.475):{0x149C} {first.last@domain.com} Send() failed: ERR_SUBMIT_MAIL, Tag=229195

I currently have a case open with TSupport and they can't figure it out and we're closing in on an hour...



In my case, TSupport thinks the "SendAs" permission has become corrupted on the user AD account object. I removed inheritance in AD for this user (since we use inheritance to propogate that permission) and made sure that permission was gone from the account. I'm going to wait 20 minutes for the BlackBerry router service to pick up the change, then turn inheritance back on for the user's AD account, ensure the SendAs permission has been added again, and then wait another 20 minutes for the BlackBerry router to pick up the change. If I don't report back, assume it worked.

FYI - TSupport determined it was a SendAs permission problem due to the MAPI error in the MAGT log for this user's BlackBerry Agent. Below is the line with the MAPI error - the "0x80070005" indicated permission denied to send the message.

[20265] (02/13 14:33:47.725):{0x149C} {first.last@domain.com} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed