Blackberry Server problems, user cannot send email

Posted on 2011-03-06
Last Modified: 2012-05-11
Hi guys.

Our Blackberry Server stopped allowing mail to be sent. All tests pass in the server configuration app. We are running Blackberry Server on SBS 2003. Error log says that Blackberry Agent Controller Stopped. There is one user on this system. They can receive messages but not send. This was working fine until this morning. I'm reluctant to dive in and mess things up when it was a perfectly working system. We did not install any updates or make any changes in the last 24 hours.

Blackberry Log:
[20000] (03/06 15:34:17.953):{0x484} LogReceiver: Failed to bind a socket
[10000] (03/06 15:34:17.953):{0x484} Could not start the syslog receiver subsystem, exiting...
[50091] (03/06 15:34:17.953):{0x484} Stopping BlackBerry Agent Controller
[50093] (03/06 15:34:17.953):{0x484} BlackBerry Agent Controller Stopped

System log:
Event Type:      Error
Event Source:      BlackBerry Controller
Event Category:      None
Event ID:      10000
Date:            3/6/2011
Time:            1:57:08 PM
User:            N/A
Computer:      XXXXXX
The description for Event ID ( 10000 ) in Source ( BlackBerry Controller ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Could not start the syslog receiver subsystem, exiting....

How do I fix this?
Question by:EStechLA
  • 4
  • 2

Author Comment

ID: 35048964
This is another error message in the event log:

Event Type:      Warning
Event Source:      BlackBerry Router
Event Category:      None
Event ID:      20000
Date:            3/6/2011
Time:            3:34:29 PM
User:            N/A
Computer:      XXXXXXXXX
[RELAY_SRP:UNKNOWN:00b75d80] Send_failure

Author Comment

ID: 35049293
Update: Stopping the DNS Server service, starting the Blackberry Controller service, and then restarting the DNS Server service allowed me to start the Blackberry Controller. However, the user is still unable to send email.

Accepted Solution

Scovndrel earned 250 total points
ID: 35053751
The Blackberry Server does not have a role in sending e-mail from the handhelds. It delivers e-mail to the handhelds, and it syncs calendar items, contacts, and read/unread status, and deletions.

When the handhelds send e-mail, it goes out from the handheld through RIM, who relays it to the recipients. In my experience, RIM frequently has outages that affect the ability to send e-mail.

I believe that tearing apart your local Blackberry server looking for errors is barking up the wrong tree. I believe what you want to be doing instead is contacting the service providers and RIM technical support and finding out if there is an outage.

By the way, you can prevent that problem with the Blackberry service not starting when the DNS Server service is running, if you reserve some ports. The DNS Server service began stomping all over other well-known ports after MS released a hotfix - and they still haven't fixed it. You'll need to find out what ports BES uses and reserve them. Here's the MS KB article describing the problem and how to reserve ports. The article references SBS,but I've seen this problem in regular Windows 2003 and used the same resolution.
How our DevOps Teams Maximize Uptime

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us. Read the use case whitepaper.


Author Comment

ID: 35060615
Thank you so much for the detailed response. The issue was with the service book on the BB. Once removed and rebooted the client was able to send email.

Author Closing Comment

ID: 35060645
Thank you so much for the detailed response. The issue was with the service book on the BB. Once removed and rebooted the client was able to send email.

Expert Comment

ID: 35060666
Good to know. I've heard of re-sending the service book as a a shotgun fix, and have used that as a tool in the past to fix sync issues. It hasn't worked for me regarding sending e-mail, but I'm glad it did the trick in this case.

Featured Post

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Exchange 2013 DL hack 4 38
SBS secondary domain installation 9 38
Exchange 2013 to another 2013 forest move request 2 18
exchange , office 365 3 20
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In-place Upgrading Dirsync to Azure AD Connect
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
how to add IIS SMTP to handle application/Scanner relays into office 365.

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question