Solved

Event ID 20000 with multiple BES warnings

Posted on 2009-05-05
4
2,861 Views
Last Modified: 2012-05-06
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!!
0
Comment
Question by:OSC-IT
  • 3
4 Comments
 
LVL 26

Accepted Solution

by:
Gary Cutri earned 500 total points
ID: 24305138
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
 
LVL 26

Expert Comment

by:Gary Cutri
ID: 24305148
Also after the restart ensure that all the BlackBerry Services are started.
0
 

Author Comment

by:OSC-IT
ID: 24305516
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
 
LVL 26

Expert Comment

by:Gary Cutri
ID: 24306315
Great to hear :)
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

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

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Find out what you should include to make the best professional email signature for your organization.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
This video discusses moving either the default database or any database to a new volume.

831 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