BES – Message Status: Desktop email program unable to submit message.

BES – Message Status: Desktop email program unable to submit message.

Windows 2003 SBS with Blackberry Professional Software Server installed in the SBS server.

I ran into this problem at a side job/contract job, that I worked last weekend.  Although we don’t use SBS at the church, and this particular problem didn’t happen at the church, I wanted to post it on my blog for anyone doing a google search on the same problem.  Hopefully you’ll find this blog sooner than later and save time troubleshooting.

You can install Blackberry Professional Software on Windows 2003 SBS.  You’ll need to create your BESAdmin account in AD and be sure the account is a member of Domain Users (not admins).  You’ll also need to make sure that BESAdmin has Send As rights on your Exchange Server.  Then log into the SBS as BESAdmin.  Once you have BES running correctly, you can log out and log back in as Administrator to mange your SBS server.  If you need to do anything to BES, log back out and back in as BESAdmin.

Here’s the problem we ran into: the user could receive e-mail, and the calendar, contacts, etc seem to sync.  But when the user tried to send an e-mail, he would get:  Message Status: Desktop email program unable to submit message.  We checked the users Security in AD and had to add the BESAdmin to the Security with Send As rights.  Within 30 minutes later, the BESAdmin had disappeared from the Security on the account.  Ultimately, our problem was that this particular user was part of the “domain power users” group.  This is a privileged group.  We removed the user from the group and all is well.

Check out this link for a more detailed and official explanation of the problem: 


BES – Message Status: Service Blocked

Out of 11 Blackberry’s on our Blackberry Professional Server that I manage onsite at our church, I had trouble with two.  They both could not Activate wirelessly.  When I plugged in the cable, I could successfully activate via Desktop Manager. However, once I unplugged the cable, I could not send/receive e-mail, nor sync with Calendar, Contacts, Tasks, etc. When I tried to send an e-mail, I received a Message Status: Service Blocked.  When I called the service provider, the moment I told her I had a BES online, they said “I’m sorry, there’s nothing we can do since you have your server you’ll need to go through Blackberry.  I can help you wipe the phone as a troubleshooting step, but from there, I’ll have to transfer you to RIM.”  So they transfered me.  After spending almost an hour on hold, I spoke with RIM.  I gave him the PIN numbers of both Blackberry phones and sure enough, they said that neither phone had the service provisioned on their phones to allow them to connect to a Blackberry Enterprise Server.  He told me to call back the service provider and ask them to be sure that the phone has the correct plan to work with a Blackberry Enterprise Server.  After doing this, we found out that the phone had a service plan that allowed for Blackberry Internet Mail (not BES).  They upgraded the plan, reprovisioned the phone, and all is working.

So… if you are receiving  Message Status: Service Blocked, call your service provider and ask them to verify that your account is provisioned to work with a Blackberry Enterprise Server.  Once they change the plan and re-provision the account, you should be all set to Activate Wirelessly.

Blackberry Professional Server Online!

Update from my earlier post on the VMware Converter…

 After shutting down the Physical EMSWEB server, I successfully brought up the Virutal EMSWEB that I was able to convert from the Physical server using VMware Converter.  Upon booting up for the first time, I installed VM-Tools.  Everything is working great.  I had to disable a sound driver that was giving trouble, and I had to reconfigure the Static IP, but once I did this, I was able to use this server from the network.  No one ever knew that a change took place.

 I gave it most of the week last week to make sure all was working well.  Then, Thursday, I took the physical EMSWEB machine, unplugged the network cable, and turned the machine back on.  I renamed the server, forced it back to workgroup, and reconfigured the Static IP for the server.  Then I plugged the network back in and rejoined the server to the domain as the new Blackberry Professional Server.  I have installed Blackberry Professional Express and it is working great.  If you or anyone on staff is using a Blackberry and you do not have a Blackberry Server, I highly recommend this.  It is very easy to setup and provides the security you need for your Blackberry and your network.  The server includes secured connections from your phone to your network, and the ability to set IT policies, such as require passwords on the phone and enable/disable certain features if needed.  Should the user misplace their phone, you can change the password remotely.  And if they can’t find it long term or it was stolen, you can remotely wipe and disable the phone from the Blackberry Server.  This is a great feature also available with Exchange ActiveSync 2003 and later (we have Blackberry & Windows Mobile Devices).  The Blackberry Server also gives you the ability to not only redirect e-mail, but to synchronize with your Calendar, Contacts and Tasks as well.

 Now that I have my Blackberry configured and working with the new server (which was a free download with one free device CAL), I’ll purchase the licenses for the other 15 or so Blackberry’s that we have on our network.  As I said before, this is a great solution if you have 30 or less Blackberry’s.  Once you reach 30, you can upgrade to Blackberry Enterprise Server.