A bit of information.

Installed BESX 5.0.2 on Windows 2008r2

Got a lot of spurious warnings and error messages relating to Blackberry services.

One of which was

Could not connect to Service Control Manager at \\127.0.0.1: 1722

Researched it a bit and came to the conclusion that as of Windows Vista the [Automatic] start up type in Windows had changed behavior.

A new type of start up was offered to help, its seems to make the 1722 problem go away.

I changed the start up type of three BlackBerry services to [ Automatic (delayed) ]:

BlackBerry Controller
BlackBerry Dispatcher
BlackBerry MDS Connection Service

They still start up, but wait for all the other [Automatic] services to start first.

This solved not only the 1722 error, but also the MDS cannot connect to database error, which occurred because the SQL instance was not ready yet.

There seem to be a number of dependences between the services which are not handled by DependsOn registry keys.. simply setting these to (delayed) just works around the problem.. could also explain 1722 on older Win2003 installs.

All event logs are now clean, zero warnings except for this one:

ExtUDPNtfThread::NotifyDatabase: COM Error 0x80040E57 - IDispatch error #3159 - Source: "Microsoft SQL Native Client" - Description "String or binary data would be truncated." - Command "ExtUDPNtfThread::NotifyDatabase"

Which I think is a database field that is being overflowed. I think it could be fixed by elarging the database field if I understood the database well enough.

Correction the Synch service problem seems to be random or unreproducible.

Upon reboot the warning message did not recur.

The BESX Event Log is completely clean.

Only Info messages are occurring.