This has been brought to my attention users are having issues with sending mail through their BB, when they try and send it comes back with a Red x if they resend it will go through (sometimes they have to retry more than once) I have looked at the BES server and noticed the event log is getting flooded with the following

Description:
MailboxManager::CreateProfile (BES_CDO_7012_7) - ConfigureMsgService (80040115) - Ensure that IPv6 is disabled on the Exchange Server or configure the BES to use the closest global catalog server

IPV6 can cause an agent to crash and can cause the netbios to resolve improperly. I don't think you can remove IPV6 from Server 2008, but you can disable it. Google that and you can find the steps. There is also a regedit change you can add as well.

Check your Controller logs to see if you see something like this. Checkout KB04646.

I am getting this error code:
[20000] (10/05 10:56:57.254):{0x2BC} Could not connect to Service Control Manager at \\127.0.0.1: 1722
in your post, have you figured out what is the cause of this and a solution? I have looked over several KB articles and onlined with RIM and we havent come up with a solution. I am also getting a controller error:

Unable to connect to Dispatcher 'BLACKBERRY'

I have tried talking to RIM and have troubleshot several articles and now they want me to rebuild the server.

I don't know why yet but check the subnet of both your exchange server and your bes server. We are finding they need to be the same. For those of you who do not know what a subnet is, look at the second set of digits of the IP address. ie if the exchange servier is 10.20.xx.xx, then the BES server should be also.

I don't know why yet but check the subnet of both your exchange server and your bes server. We are finding they need to be the same. For those of you who do not know what a subnet is, look at the second set of digits of the IP address. ie if the exchange servier is 10.20.xx.xx, then the BES server should be also.

when i applied the NSPI changes, my primary BES server started to work perfect after a reboot, but passive node had issues still. when i failover to passive node i got all sorts of MAPI and dispatcher errors, so failback to working server, some more digging got me to this BlackBerry Dispatcher