[Dan Slaby]

I'm getting the following errors in my event log from the ExchangeConnector:

[SRP] Connection Failed
SRP Client::Connect: Error calling host "127.0.0.1" (10061)
{Name.1} UpdateUserInfo: Session to BES Agent is not established

Any troubleshooting suggestions or fixes? Thanks

[dev]

It seems that your Exchange server may have been restarted at some time. This usually breaks the MAPI connections to the BES. You'll have to restart the BES services as well to re-establish the connection.

[Michael Van Ryan]

Yet I've restarted my BES, can confirm the SRP connectivity via the test executable, and have confirmed what my Exchange Environment is functioning normally.

Any other suggestions?

Started occuring local time 5:21.

[bl0rb]

This issue can be caused by one of the following:

1. Port 3101 is not open or is refusing outbound connections.
2. The Internet connection timed out.

Cause 1

The BlackBerry Enterprise Server is not connecting to the BlackBerry Infrastructure through the firewall.
Resolution 1

Verify if the BlackBerry Enterprise Server connects through the BBSrpTest.exe utility.

1. Browse to C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Utility\.
2. Run the BBSrpTest.exe file and look for a Successful response in the command prompt window.
3. If the command prompt window shows a failed message or a winsock error code, verify that your SRP credentials are correct.
4. If your SRP credentials are correct, contact your network administrator.

Note: Firewall port 3101 should be open for outbound initiated, bi-directional traffic.
Cause 2

The Network Access Node key in the Microsoft Windowsxxx174; Registry is set to an IP address or NetBIOS name other than localhost.
Resolution 2

Modify the NetworkAccessNode value to localhost in the registry.

Warning: Modifying the computer registry can cause substantial damage to the Microsoft Windows operating system. Document and back up the existing registry entries prior to implementing any changes.

1. Click Start > Run and type regedit.
2. Browse to HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry Enterprise Server\Dispatcher\.
3. Change the NetworkAccessNode Value data field to localhost and close the Registry Editor.
4. Go to Control Panel > Administrative Tools > Services.
5. Stop and Start the BlackBerry Dispatcher

[BlackBerryLinks]

Originally Posted by Michael Van Ryan

Yet I've restarted my BES, can confirm the SRP connectivity via the test executable, and have confirmed what my Exchange Environment is functioning normally.

Any other suggestions?

Started occuring local time 5:21.

Check if someting is changed in the Windows Policies. if you get 127.0.0.1 in the error, it is the local host. Check if all the required services are still running.

The following Microsoft Windows services are required to run the BlackBerry Enterprise Server:

* Event Log
* NT LAN Manager (NTLM) Security Support Provider
* Windows Time service
* Workstation

Also if you installed new/other software on the BES (e.g. Backup software) check for port conflicts.

Regards,
Bob

[dluczyk]

ok so i had the same thing and what i realized is many of my bes services on the server were using my account credentials and I recently changed my password. So I had to change the password in the services and start them up properly which fixed the issue. Sounds simplistic I know ...but just in case this helps someone else!

[hdawg]

Did you install the BES as your account or as a BESAdmin account?

[DarienA]

I get random SRP failures. Not all the time and not regularly(not every day, not even every month, just seemingly at random), but oftentimes in the wee early hrs of the morning... it can range from 5 min to the most recently one 2 hrs(which ran from 2:23am to 4:22am on the 7th).... There's nothing going on out of the ordinary, on the network during these time periods, and I'm just baffled as to what could be causing this...

Anyone have any ideas as to what I might want to look at? There are no other reports of Internet connectivity issues in any other network logs, firewall logs, etc... during these periods.