Hi all,

Anyone got a clue as to what this is?

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

Been happening for a while and I can't find any support for it.

Much appreciated in advance.

Acid_Reflux (it's not just a screen name ... it's a state of being!)

It could be that the security settings on your BES server does not allow you to local logon. Also look if all Dependencies of the BlackBerry services are running (e.g. NT LM Security Support Provider). To do this:

- go to Services
- double click on the BlackBerry service
- click on the Dependencies TAB
- look if all dependencies services are running

Do this for all the BlackBerry services.

Regards,
Bob Hillesum

What version of Windows are you using? If it's Small Business Server then check out this KB -
http://www.blackberry.com/knowledgec...65876&vernum=3

Hi everyone,

I'm getting this problem as well. We are being absolutely driven nuts by it.

We are trying to support someone who previously had another person install a Small Business Server 2003. They also installed BES 4.1 and failed repeatedly. We have come in to try and resolve this but are coming to roadblocks we have not been able to find an answer for.

Now I know it is not a supported install but this is also a PDC.

In this case we have gone through the permissions a number of times, completed a 'clean uninstall' and then reinstalled the BES installation again. I have checked the dependancies as above and have ensured the BES was installed with the BESAdmin account.

The SBS is service packed to SP1.

We have gone through a KB article on RIMs website about needing to change a registry key for SMB but this has not helped either.

The main errors we are seeing occur as follows:

CTRL log:

Unable to connect to Dispatcher '[SERVER NAME]'
Could not connect to Service Control Manager at \\127.0.0.1: 1722

The REALLY strange thing we are seeing is that there is no MAGT log created (the log name hasn't been changed either) and the MAGT service is not even showing in the 'Services' window!!

This seems to suggest to me that it is not even establishing a connection with Exchange.

Is there some security setting within SBS that will block communication with Exchange components by default?

I'm really lost here guys and would really appreciate any help you may have.

Again, I realise that it shouldn't be done on a PDC but CAN you do it on a PDC. If so, does someone know the settings I need to use as you can only convince the customer of so much.

Yours in desperation
Davinci1969

Did you ever resolve this? I am having the same problem. I suspect its MAPI related. Please post how you fixed this.