I recently migrated our BES to a new physical box, and restarted it. Upon startup, no one is able to connect to the BES via their phone.

Im looking at the services now, and the Blackberry Mailstore Service looks to be not started. I try starting it, and I get the error: "Windows could not start the Blackberry MailStore Service on the Local Computer. For more information, review the system event log. If this is a non-Microsoft Service, please contact the service vendor, and refer to the service-specific error code 5406."

I believe this to be why I cannot add new users to the BES, or get anyone connected, any suggestions?

Oh btw, My BES is a virtual machine, and my exchange server is a virtual machine as well. They both reside on the same physical machine.

When you installed BES on the new machine, did you install it while logged in as the BESadmin user, or some other user?

What user are the BlackBerry services currently running under?

What version and service pack of BES?

Have you verified that the BES service account has the proper permissions set to access Exchange?

BES is 5.0, OS is Windows 2k3 R2, SP2.

BES account was used in the initial installation a few months ago, and still has sufficient privilages.

Unsure what you are asking about what the BES services are running under?

In Windows Services (services.msc), there's a handful of BlackBerry services.
Each service runs as a particular user, shown under the 'Log On As' column.
What user account are your BlackBerry services showing here?

Ah, I see. They are all running under our blackberry service account.

OK, then run through this KB and make sure everything is set correctly.
KB02276 - Assigning permissions for a BlackBerry Enterprise Server service account - Port3101.org : Your BES Connection

ran it through those steps and still cannot start the service. im wondering since they are on the same physical box as the exchange server if this has anything to do with it. It is on a separate virtual machine from exchange though... not sure what blackberry says about virtualization.

Shouldn't matter that they're VMs.
Just curious... where is the BES SQL database located?

did a restore from a previous VM, all seems to be well, thank you for the help. I think the VM was corrupted somehow during the migration.

I dont mean to hijack this post but it sounds like the other gentlemen is taken care of so lets see if you can help me Penguin!

I have a similar setup:

-entirety of the infrastructure is virtualized using VMware ESX 3.5
-running BES 5.0 (havent installed update yet, having problems with that too)
-SQL is local to the VM
-all other services start except for the mailstore service
-checked all rights assignments on each exchange server, as well as on the VM for log on as a svc, local admin, etc, and AD rights are good as well

reboot, the system, still have the same isssues
if I rollback the issue is fixed like the other guys issue! but there were no changes except some JRE updates and a dot net update. Other than that we added some users (who are were working fine btw) and nothing else has changed.... any ideas?