[xwire]

Hey folks, the boss man is experiencing where he cannot send email from the blackberry unit after his domain password changed over the weekend. I was thinking that he would have to place the unit on the cradle and have it connect and re-sych up, but he disagrees with me. Problem is, the cradle and computer he uses it 200 miles away so we will have to send it over night and have somebody place it on the cradle to see if it synchs back up and to be able to get the email sending to function again. Ohh the unit can receive email though.

Am I correct that it needs to be placed on the cradle?

[juwaack68]

His domain password changing shouldn't make a difference. What happens when he tries to send mail? Does he get the red X?

[xwire]

Yes the red X, first and then the check mark, and the event log error message of this

*** MAPI *** MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed.[20000] (12/13 15:38:10):{0x7FC} {< >} Send() failed:

so I have changed what this tech sheet on the blackberry/microsoft workaround.


then I get Send() failed: ERR_SUBMIT_MAIL, Tag=36484774

Although I did not restart the services after I changed the tech sheet settings.

[|||||||]

KB-04707 says:

For BlackBerry Enterprise Server 4.0 and 4.1
1. Stop the BlackBerry Router for 20 minutes.
2. After 20 minutes, restart the BlackBerry Router.

[xwire]

What service should I stop if I have the older 3.6 BES? Or should I just restart the whole server?

[juwaack68]

Is this issue only affecting 1 user? The BB Router stop for 20 minutes is, as I understand it, to fix a 'Send As' issue that would affect all users (as it did for all 364 of my users on Sunday.

Here is what I had to do to resolve the 'Send As' issue: http://www.blackberryforums.com/bes-...-resolved.html

[ashworth]

If it is a 3.5 or a 3.5 or 2.1 BlackBerry Enterprise Server then you will need to stop the BlackBerry Server service.

[xwire]

Checked all the Send As resolutions that juwaack68 had done, I just restarted the server as hardly anyone is here. Tried to compose email from the Blackberry and still red X. Another thing, on the Blackberry Server Manager, we choose to regerate the Encryption Key Configuration, and it says pending update. So wouldnt this require the unit to be placed back on the cradle?

[juwaack68]

- What version of BES are you running?

- Is this affecting more than 1 user?

- When you get the red X, open the message, scroll up to the header, and what is in the Message Status field?

[xwire]

BES 3.6
Only have 1 user on the system, (BES small business edition)
error message = Destop Email program unable to submit message.

[xwire]

after a quick red x then the green check mark, the message says sent, granted this is only sometimes it does this. But the message never shows up.

[juwaack68]

Odd....never seen red X change to green check.....

Does the Sent email show up in his desktop account sent items folder?

[xwire]

nope, I just checked that and the sent items are not in there.

[Lamo]

Check the following as posted by HandyD in another post but I cant point to the url as I ain't made 10 posts yet(sorry)

Hopefully this maybe the cause.

1. Open AD Users and Computers

2. Select View and Advanced Settings

3. Create a Domain Local Security group at the highest OU level that contains the users accounts that have Blackberrys.

4. Add these users as members of the group.

5. Go to the Security Tab for the group.

6. Click Advanced Permissions button.

7. Click Add and select the account that you use as your BES service account.

8. On the Permissions page change the drop down for Apply Onto to read User Objects

9. Then set Send As and Read permissions

10. Make sure the Apply These Permissions to Objects Within This Container box is unchecked.

11. Click Ok out of all the permissions pages.

12. Then restart exchange system attendant to refresh the permissions cache.

13. You'll now find that the permission is inherited by all your BB users and it will now stick.

[xwire]

One thing is that the BESadmin account is in the users container, and the actual bb user is located in another container, that shouldnt matter should it? I mean this bb unit has been working like this for over a year.

[Lamo]

The containers don't matter as long as you follow the instructions HandyD wrote, I have tested this today for one of my users and it worked.

The reason they stop being able to send is that the send as permission is revoked for the BES admin account. This happens if you have applied a hot fix that was released by M$ on the 21st of June (I belive) to your exchnage 2000/2003 server.

[xwire]

I will keep at it, I am sure the hot fix is what did it, but I have or at least seem to think that I applied the workaround.

[Lamo]

The other thing you can do is to open the users and computers management console after selecting advanced features in the view menu expand the domain and select the users container.

right click on one of the affected users and select properties then select the security tab.

add the BES admin account to the Groups and users box and then grant it the send as permission in there.

Stop the router for 20Mins if 4.0 or above or the Blackberry service for 20 mins if 3.6

Try sending again. ( this however will not work if you are part of the AdminSDGroup as the hotfix is desgined to stop accounts with admin rights from also being used for the sending/receiving of mail) if this is the case you have to have one account for Admin and one for sending/receiving email

[xwire]

so if the BESadmin account is part of the administrators group and the account that sends the email then I need to create another account to do the send and receive mail?

[Lamo]

No sorry not the BES admin account I was talking about your personnal account. If your personnal account is part of the Administrators group then fix will not work on your personal account. You would have to either drop your admin rights on your admin account or create yourself a seperate account for the purpose of sending/receiving mail.