Hello everyone,

using the guides here i was able to successfully setup and get a Blackberry Professional Server up and running, thanks all!

The only problem i'm having is that it will not allow the device to send emails right now.

The errors I see in the log are below.


[30000] (01/29 17:42:20.845):{0xC4C} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent Blackberry Agent 1 (Application Event Log on VENUS) | 01/29/2008 17:42:12 (AFFF4F29) -> {user@company.com} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed

[30000] (01/29 17:42:20.845):{0xC4C} [Alarm::ActivateAlarm] Queuing alarm: <N/A> | BlackBerry Messaging Agent Blackberry Agent 1 (Application Event Log on VENUS) | 01/29/2008 17:42:12 (AFFF4FF8) -> {user@compay.com} Send() failed: ERR_SUBMIT_MAIL, Tag=441

I've gone through the permission settings multiple times, As far as i can tell its correct. Send As is configured for the besadmin useraccount, and is a view only exchange administrator. Again receiving works perfectly fine and all emails are delivered correctly, only sending is an issue right now. Any help would be appreciated, thanks!

edit: FYI, email address in error changed for obvious reasons

update:

I went through RIM's knoledgebase and i do have the dreaded hotfix applied on my exchange server that causes this problem. I followed their steps exactly to fix it, but the same issue still remains.

Is this affecting all user or just a select few? If you set the Send As permission in AD make sure that the users that can't send actually have it enabled on their user object.

Some users could have inheritance turned off or might be in certain protected groups:

Domain/Schema/Enterprise Admins
Backup/Print/Account/Server Operators
Adminstrators

There might be one or two more as well. If people are in the groups then check out article 817433 on the Microsoft web site. It's got a hot fix and some AD modifications in case the hot fix doesn't work. The article also has all the affected groups listed.

Let us know if you find the resolution.

that does seem to be the issue i'm having. I will have to try the hotfix. My question is, what server do i apply this fix onto? Would it go onto my domain controller servers? The Exchange/BES server? all three of them?(2 domain, 1 exchange/bes)

MS KB articles make my eyes bleed.

Just to be clear, you have verified that the user objects have the BESAdmin with Send As. You also didn't specify if this affects everyone or just certain users.

I'm not sure about the hot fix, I've never used and I haven't seen it work to be honest. I usually recommend using either Method 2 or 3 in the article to fix the issue if it has to do with group membership.

Here is the process I would follow:

1. Ensure that Send As is set at the domain level
2. Check individual users to see that they did indeed inherit the permission
3a. If they didn't check that inheritance is enabled and check group membership
b. If inheritance is not enabled then enable it and stop the BlackBerry Router service for 2 hours or restart the Inforamtion Store service(way faster) and the start the BlackBerry Router service
c. If group membership is the issue either remove the users from the affected groups if not needed or apply one of the work arounds in 817433 and then do the stop BB Router service process
4a. If it's not inheritance or group membership, try the Outlook test
b. Log into a Windows XP machine as the BESAdmin
c. Open Outlook and point the profile to one of affected users mailboxes, you should only see that users mailbox, and don't use Cached Exchange Mode
d. Compose and new email and send
e. If the email fails to send or doesn't get received then it's permissions. You may have to use DSACLS to force the permissions to write to the mailbox

Even though the permission is set it doesn't actually write to the mailbox and DSACLS can do that. There are articles from Microsoft as well to help with using that utility. I would give you instructions but I would do more harm then good.

You can thank Microsoft for this lovely issue. It targets the BESAdmin account perfectly.

Follow the above to narrow down the issue. Let us know what you find.

sorry I forgot to add that this is only effecting domain admin users. They do not have the besadmin account with send as enabled in the permissions. Regular accounts seem ok. What i tried earlier was adding the besadmin, allowing send as, but the permission disappears. The KB article describes this as 'normal'. Its almost certainly a group membership issue.

I will follow your steps as soon as I get a chance, but probably not until next week sometime, since the only 'admin' user its affecting at the moment is myself. It is a new install and not rolled out yet for this reason, but now that i've gotten a regular user up and running, i can go ahead and order more licenses and move forward. Thanks for all the help, i'll update as i progress!

Why not follow the principle of least privilege and create yourself a second account.