I am running BES 4.0.0 and MS Exchange Server 2003.
Recently users have not been able to send messages. They receive them fine, and the BES is syncing all other information but when you go to send (or reply) an email, you get the red x, and the Message Status says "Unlisted message error".
I have reset the BES, tried stopping and starting all the services, and still can not send.
The BES was just kind of thrown in my lap, and I am really not sure how to proceed.
Should I start installing the service packs, starting with SP1? I am worried about losing the existing functionallity if I start upgrading before the sending error is fixed.
Any help is appreciated. Thank you.

No worries we wil make besadmin out of you . Before you start changing things to fix it, look at what might have changed to cause it. You need a really good understanding of your existing architecture before you can understand what effect changes can/will have.

So I would be looking at the following things to get you going, we can get into details later -

1. when did this start?
2. do you know of anything at all on the BES or Exchange servers which has changed since then? Nothing is too small a change to be relevant (well, nearly nothing)
3. could anyone have changed any Exchange permissions which would cause this (specifically the access besadmin has to Exchange)

I am wondering if you just applied the latest Exchange security patch and that has caused an issue. Find out if you did and if yes, was it on Exch only or Exch and BES.

It might be handy to know your MAPI32.dll and CDO.dll versions from Exch and BES now, just in case.

After some reseach it looks as though this issue did start after an exchange security patch. I will get the MAPI32.dll and CDO.dll versions as soon as i get a chance.
Thanks

If it was after the latest one, you can try the following (from other threads here) -

1. uninstall security patch on BES, reboot (or just restart services) then reinstall the patch
or
2. uninstall patch on BES, reboot (or just restart services)

Leave it on the Exchange boxes though.

1 has worked for others who broke after applying it to the BES and 2 is how a lot of us are right now (patch on Exch but not on BES).

The MAPI32.dll and CDO.dll files in the programfiles/exchangesvr/bin directory are both version 6.5.7654.12.
I dont think that any permissions were changed. The only things that appear to have been changed were some of the settings on the backup program.

Ok so try my last post and see how it goes.

I might be confuesd here, but I think the exchange server and the BES are the same box in my case. We only have one "physical" server.

Wirelessly posted

BES and exchange on the same box is a really bad idea and not supported. You sure its exchange 2003 and not SBS?

How can I tell for sure if it's 2003 and not SBS?
In the add remove programs menu all of the secrurity updaes say "Update for Exchange 2003"

I removed the update, rebooted and still get the red x.
I am gonna recomend that the BES be ugraded as soon as the boss is back in town.
Thanks for your help.

check your active directory, user register on BES, must add group "BES name" (default : BESAdmin).

this problem cause hotfix of mail server mail box.

Hope it will solve