BlackBerry Forums Support Community

DarkPhoenixVR4 · 04-07-2010, 02:38 PM

After some troubleshooting, and wiping the device and reactivating it on the BES, only one user, out of 8, is unable to send email from her BB. Everything in her account on the BES looks okay and she can receive.

Any ideas out there?

Thanks,

Craig

penguin3107 · 04-07-2010, 02:42 PM

Is this user a Domain Admin or a member of any protected groups in your Active Directory?

DarkPhoenixVR4 · 04-07-2010, 02:43 PM

At one point, she was in the domain admin group, but we took her out last week.

penguin3107 · 04-07-2010, 02:45 PM

Quote:

Originally Posted by DarkPhoenixVR4

At one point, she was in the domain admin group, but we took her out last week.

You'll need to reassign the Send-As permissions.
http://www.port3101.org/featured-bla...n-revoked.html

DarkPhoenixVR4 · 04-07-2010, 03:26 PM

Here is the log file for the user in the BES.

Code:

[40700] (04/07 16:08:01.963):{0x17A0}{user} Receiving packet from device, size=152, TransactionId=1255830636, Tag=2126, content type=CMIME, cmd=0x3
[30112] (04/07 16:08:01.963):{0x17A0} {user} Receiving message from device, RefId=11259567, Tag=2126, TransactionId=1255830636
[20265] (04/07 16:08:01.988):{0x17A0} {user} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed
[20472] (04/07 16:08:01.993):{0x17A0} {user} Send() failed: ERR_SUBMIT_MAIL, RefId=11259567, Tag=2126
[40277] (04/07 16:08:01.993):{0x17A0} {user} Sending message error to device for message 11259567
[40583] (04/07 16:08:01.993):{0x17A0} {user} Sending packet to device, Size=44, Tag=2605, TransactionId=-876979159
[40279] (04/07 16:08:01.993):{0x17A0} {user} SubmitToRelaySendQ, Tag=2605
[40279] (04/07 16:08:01.993):{0x17A0} {user} SubmitToRelaySendQ, Tag=2126

This is after i changed the send as permissions as outlined in the KB.

EDIT: I started doing some of the stuff in this articles as well.

http://www.port3101.org/featured-bla...-messages.html

freakinvibe · 04-08-2010, 03:58 AM

On a failed message, can you scroll all the way up and indicate the exact error message, which you can find under "Message Status".

DarkPhoenixVR4 · 04-08-2010, 07:04 AM

Quote:

Originally Posted by freakinvibe

On a failed message, can you scroll all the way up and indicate the exact error message, which you can find under "Message Status".

Code:

Desktop email program unable to submit message

That is the error message I get.

I have checked all the user's permissions, as well as the BESadmin being able to "send as"

It is driving me nuts!!

tonyadfs · 04-08-2010, 07:23 AM

Her SEND AS permissions have been revoked.
Check out:
Send as permission is not enabled for a BlackBerry smartphone user
Document ID: KB17651 (blackberry website)

DarkPhoenixVR4 · 04-08-2010, 07:38 AM

Quote:

Originally Posted by tonyadfs

Her SEND AS permissions have been revoked.
Check out:
Send as permission is not enabled for a BlackBerry smartphone user
Document ID: KB17651 (blackberry website)

Already did that.

knottyrope · 04-08-2010, 09:12 AM

Did you reboot the BES server yet?

DarkPhoenixVR4 · 04-08-2010, 09:27 AM

Quote:

Originally Posted by knottyrope

Did you reboot the BES server yet?

The only thing I did do was stop the BB Router Service. I am waiting for another hour before turning it on again. I am keeping my fingers crossed on this one.

CMCAdmin · 05-25-2010, 12:00 PM

Not to drag up an old thread, but I am having the same issue. I have search though the forum and fixed the issue this morning by manually adding the BESadmin account to send-as to my account(I am a domain admin). while I was away at lunch the problem started again. Now the BESadmin permissions on my account are gone. IF I go to properties of the OU the BESadmin account is still listed with send-as. Any ideas?

Thanks Andy.

knottyrope · 05-25-2010, 12:28 PM

If you want your BES and handhelds to work correctly for everyone, all of the time, then you need to follow RIM's guidelines and best practices.

It's called the Principle of Least Privilege... and you're not following it.

Principle of least privilege - Wikipedia, the free encyclopedia
Principle of least privilege - Wikipedia, the free encyclopedia

Make yourselves normal users, and then create a secondary login with Domain Admin privileges. Only use that secondary login when necessary.

BBExpert · 05-25-2010, 12:43 PM

This is a stubborn issue. Have you looked at this KB View Document

Meanwhile let me dig in my notes for a similar problem long time ago.

knottyrope · 05-25-2010, 01:06 PM

Quote:

Originally Posted by BBExpert

This is a stubborn issue. Have you looked at this KB View Document

Meanwhile let me dig in my notes for a similar problem long time ago.

Some Expert you are, it is not a stubborn issue. A domain admin account should not have mail enabled, period! Article ID 907434 even states it.

That KB should be rewritten as only the fools or uneducated will do it.

knottyrope · 05-25-2010, 01:12 PM

snip from
View Document

It is possible to modify Microsoft Active Directory permissions to allow BlackBerry smartphone users who are members of protected groups to send email messages from their BlackBerry smartphones without creating secondary email accounts. For instructions on modifying the permissions that are associated with the AdminSDHolder Microsoft Active Directory object and have been changed by the recent Microsoft Exchange update, vist the Microsoft Support Knowledge Base web site.

Important: This procedure is not recommended by Microsoft or by Research In Motion.

CMCAdmin · 05-25-2010, 02:35 PM

Quote:

Originally Posted by knottyrope

Make yourselves normal users, and then create a secondary login with Domain Admin privileges. Only use that secondary login when necessary.

I removed myself from the admin group and stopped/started(after 20min) the router and still not working. Below are the erros in event viewer on the BES, no errors in AD or exchange.

{ABush@cincymuseum.org} Send() failed: ERR_SUBMIT_MAIL, RefId=1068254610, Tag=532
{ABush@cincymuseum.org} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed