[gwalker]

Can anyone help with this one....

I am trying to send a message from the bess to my handheld users by email, not pin. (PIN works fine.) When I do, I get a send error that refers me to the log. The message below is in the application log:

"[ExchangeAdaptorDLL::SendBulletinByEmail] SubmitMessage failed, result=0x80070005."

I have googled this and I can't find anyhting. The other BES administrator here (who is set up identically to me) does not get this error and a message is sent from the BES's Exchange account.

BES Version 4.1.2.25

Any ideas??? Thanks Gordon.

[MWPatterson]

I get the same message on all users after I upgraded Exchage to SP2.

[gwalker]

I get when selecting all users and an individual recipient.

[matt_the_katt]

You have the send as security patch upgrade. if you are running BES on a DC and have any IIS web site where the users are not authenticated you are SOL.

SO if you have teh above, the only fix requires you to redefine global domain policy which breaks everything,

So your options are: 1) build up exchange as a member server 2) go back to desktop redirector

Also, did I say that you cannot demote exchange to a member server if it was running on a DC.....

[MWPatterson]

I finally got it. I had to do the following. Reinstalled Exchange SP2 in the BES Server. Delete all the MAPI profiles in the registry. Set them back up to use a the besadmin account and made sure that he had send as rights for the domain. Restarted the server and there, it finally started working.

Here is the excery from an email from RIM about what to do after I had gotten it working.

1. Shut down the BlackBerry Services
2. Completely uninstall Exchange System Manager
3. Delete any MAPI Profiles that do not get removed
4. Install a new copy of Exchange System manager 5. Apply the appropriate Service Pack to Exchange System Manager (Service Pack 2)
6. Create the BlackBerry MAPI Profiles
7. Start the BlackBerry Services

If this does not resolve the issue, I recommend contacting Microsoft as it would appear that the Exchange Server is accepting the permission from one source and not from another which should not happen. If you require further assistance, please don't hesitate to contact us. Thank you again for contacting us.