I've gone through all the SendAs permission steps, BESAdmin has SendAs permission on every object that is trying to send outgoing mail, and the privileges are sticking. None of these users are members of Doman Admins. I've restarted both the BES server and the Exchange server, stopped the blackberry router after restarting the information store for 20 minutes, etc. I really have no idea.
I am almost positive this is not a permission issue, as I've applied the SendAs permission at the domain level, and it has properly propagated to all the user objects (it's a small company, so this is no big deal).
The only thing I can think of is that BESAdmin is corrupt for some reason.
All these issues arose after I installed the UTC Exchange patch on Exchange 2003 to fix calendars not syncing properly (which awesomely enough, still does not work properly). I've read multiple documents about this issue, and they all point back to SendAs permissions. I have checked, checked, and double checked this, i have even run the command for the adminSDHolder (even though none of these users are members of Domain Admins or any other Admin group).
Please help me out, I've been banging my head on the wall for three days over this issue.
I'm seeing those errors. I removed the propogated permissions, and gave BESAdmin SendAs on each individual user, restarted Information Store and BB Router. I guess now all I can do is wait.
I am still unable to send, and now the agent logs are telling me it won't log send failures because the BB router has been restarted more than 10 times in 24 hours :-
I finally got it working, as far as I can tell, what fixed it is creating a new BESAdmin account (in my case I just named it BES_Admin) and re-doing all the privileges in AD, on the BB services, and the SQL server. The import/export of the registry for the old account was an excellent tip during these instructions as well.
If I had more posts, I'd definitely post the beer cheersing emoticons for you Knot. Thanks a bunch.