Event ID 20000 with multiple BES warnings

We had an issue last week where our exchange server had some windows updates installed and the next day we could not send out SMTP email as it was stuck in the queue. After a few hours on the phone with MS support we were able to get email to flow.

While researching the issue myself I noticed thousands of Blackberry warnings that started on the same day and are continuing to eat up the app log. I have done some searching around but haven't found anything that fits my situation so here we are. :)

The BES is installed on the Exchange server which I cannot RDP to as well since all of this happened.

Event Type:      Warning
Event Source:      BlackBerry Synchronization Service
Event Category:      None
Event ID:      20000
Date:            5/5/2008
Time:            11:52:04 AM
User:            N/A
Computer:      OBELISK2
Description:
BIPPeClient::Connect: Error calling host "OBELISK2" [192.168.234.235] (10061)

NOTE: The IP in the above event is NOT the IP of our exchange server and it's not reachable on my network. (??)
I then get a second event identical to the one above but this time is shows the correct IP for the host OBELISK2.



Event Type:      Warning
Event Source:      ExchangeConnector
Event Category:      None
Event ID:      20000
Date:            5/5/2008
Time:            9:52:56 AM
User:            N/A
Computer:     OBELISK2
Description:
BIPPeClient::Connect: Error calling host "OBELISK2" [192.168.234.235] (10061)

Again, not my correct IP followed by a duplicate event with the correct IP


Event Type:      Warning
Event Source:      BlackBerry Policy Service
Event Category:      None
Event ID:      20000
Date:            5/5/2008
Time:            9:53:02 AM
User:            N/A
Computer:      OBELISK2
Description:
BIPPeClient::Connect: Error calling host "localhost" [127.0.0.1] (10061)

Any assistance would be greatly appreciate as always!!
OSC-ITAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Gary CutriConnect With a Mentor Data & Communications SpecialistCommented:
Hi, the first thing you need to do is restart your BES. Also if you have dual NICs (or teaming) ensure that the configuration is still correct.
0
 
Gary CutriData & Communications SpecialistCommented:
Also after the restart ensure that all the BlackBerry Services are started.
0
 
OSC-ITAuthor Commented:
I couldn't restart the actual server so I restarted all the BES services and found one that had a log on failure. I fixed that and haven't had a warning in the app log since.

I believe we're good to go.

Thanks garycutri


0
 
Gary CutriData & Communications SpecialistCommented:
Great to hear :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.