[Hannah814]

Last Sunday & this Sunday early houts between 650-715 Bes stopped allowing users to send/receive emails on bb, there was 10gb disk space free. I’ve cleared some logs just incase.

Last week it was Sunday evening. We rebooted bes on both occasions to resolve & it did! The othe bes was not affected.
We have monitoring software which checks for server ping outs/ping down & emails us when a server ping response is down. I want to add more blackberry services onto it currently only the IPaddress is on it. But in both incidents bes was pinging ok therefore it was not down
Which are the services that should be covered? More so if Bas crashes out, what service should be looked for? So that we’re alerted therefore we can reboot rather than waiting for users to call.

Where should we configure the bes alerts to alert our alert server?

Any other windows 2003 bes services to monitor?
How about srp service?

Also if you have this appear in the MAGT log could this be the reason why it is stopping users from sending and recieving emails? What would cause this

30293] (01/31 06:58:17.354):{0x1260} SRP connection dropped
[30293] (01/31 06:58:17.354):{0x1260} [BIPPa] Connection dropped, Error=0
[45001] (01/31 06:58:17.354):{0x1260} [BIPP] Connecting to "localhost"
[40000] (01/31 06:58:17.354):{0x1260} BIPPaClient::Connect: Found 1 addresses for host "localhost"
[40000] (01/31 06:58:17.354):{0x1260} BIPPaClient::Connect: Host "localhost" @ [127.0.0.1]
[40000] (01/31 06:58:17.354):{0x1260} BIPPaClient::Connect: Trying "localhost" @ [127.0.0.1]
[50000] (01/31 06:58:17.401):{0x15B4} Controller: closing
[50000] (01/31 06:58:17.401):{0x15B4} Controller: Requested to stop

Also

Stopping BlackBerry Mailbox Agent 1 for Server

Then the users mailboxes start stopping.


User shutting down...
[40637] (01/31 06:58:17.901):{0x1CEC} {N.Gu@xxxxx.com} Mailbox Unadvise, Connection=2
[30070] (01/31 06:58:17.901):{0x1B9C} User shutting down...
[30070] (01/31 06:58:17.901):{0x1D28} User shutting down...
[30070] (01/31 06:58:17.901):{0x1D30} User shutting down...
[40971] (01/31 06:58:17.901):{0x1498} {BES_CDO_5268_138} Unable to open registry (Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Deleted Profiles\BES_CDO_5268_138)

[Jadey]

OK multiple issues here, so I'll answer what I can in chunks.

First up, a ping to a windows OS IP does NOT mean that BES is up. It means the Windows OS is up. BES could have died on it's arse to be frank - the windows box will still return a ping.

So yes, pinging a server will let you know if Windows is down. If that happens, BES is down. However, if Windows is up, doesn't mean BES is functional...

[Jadey]

Originally Posted by Hannah814

Where should we configure the bes alerts to alert our alert server?

Log in to BAS
Servers and Components
BlackBerry Domain
Component View
Alert
(Click on the SERVERNAME_ALRT that you want to configure)
Edit instance
* Enter the SMTP information that you will use to send alerts
* In the User Name section, configure recipients to receive alerts, and what level of alerts they want to receive

More info on alert levels here
BlackBerry Enterprise Server Alert Tool - Administration Guide - BlackBerry Enterprise Server for Microsoft Exchange - 5.0.2
KB00564-How to configure and set default notification levels for BES Alert

[Hannah814]

Any idea why the SRP connection would drop?

[Jadey]

Could be a few things. Mine drops occasionally, doesn't overly concern me as it comes back instantly.

How often is this occurring?

[Jadey]

I think these would be useful sections for you to read through

Managing servers

Monitoring BlackBerry Enterprise Server components - Monitoring Guide - BlackBerry Enterprise Server - 5.0.2

[Hannah814]

It happens every Sunday between 6am and 7am. I'm wondering if another process starts and pushes the BES to the back burner where it falls flat on its face.

Thank you for your help I have advised my customer the findings. See what he comes back with.

[knottyrope]

try this at the time it happens.
KB02068-How to troubleshoot SRP connectivity issues