BlackBerry® Enterprise Solution

[ravenlite]

Twice in the two months that BES 4.1.7 for MDS has been installed, the services stopped.  I don't believe I have done anything to cause it, we are just going through testing and tweaking of the IT policies. 

Once the services stop, I can't get them started again.  I try through services, and nothing.  In teh BB Manager the status says stopped and the SRP status says Unknown.  If I try to start it via the Manager the status will say restarting and then stopped.

I go into the BlackBerry Server Configuration and test everything in there, it tests fine.  I have done the tests listed in KBs for the router.  Every test passes, though I can't start the services.  I restart the server and it does no good.

The only "fix" I have found for it is to run through the server installation twice.  The first time will stop and remove all of the services.  The second time will readd and restart all the services and it works like a charm.  I would like to figure out what's causing this and fix it instead of the band aid I have now.

The errors I get on the services is that it can't connect to the SQL database, though all tests to that pass just dandy.  I have tried to stop and restart the services in the recommended order and no love. 

Any ideas on that hiccup that is happening and what I'm doing wrong?

Thanks!!

[knottyrope]

any errors in teh MAGT log?

default location :\Program Files\Research In Motion\BlackBerryEnterprise Server\Logs

Also look in event veiwer to seef if any errors or warnings pertain to your issue

Please post back the log info minus personal info

[ravenlite]

There was a MAGT log on the day it went down and not again until it came back up.  Here is what it says at the end of that log, otherwise nothing else in there looks different from any other to my eye:

[40000] (06/29 11:55:34.723):{0x1C28} SRPClientSessionReceiver thread stopped
[30000] (06/29 11:55:34.723):{0x1C28} [DIAG] EVENT=Unregister_thread, THREADID=0x1C28, THREADNAME="BIPPa_ClientSessionReceiver"
[20000] (06/29 11:55:34.973):{0x1D58} BIPPaClient::Connect: Error calling host "localhost" [127.0.0.1] (10061)
[40000] (06/29 11:55:34.973):{0x1D58} [BIPP] Connection failed
[30293] (06/29 11:55:34.973):{0x1D58} [BIPPa] Connection dropped, Error=0
[40000] (06/29 11:55:34.973):{0x1D58} SRPClientSession thread stopped
[30000] (06/29 11:55:34.973):{0x1D58} [DIAG] EVENT=Unregister_thread, THREADID=0x1D58, THREADNAME="BIPPa_ClientSession"
[40507] (06/29 11:55:35.348):{0xE84} ExtUDPLogThread: Code on closing = 0
[30000] (06/29 11:55:35.348):{0xE84} [DIAG] EVENT=Unregister_thread, THREADID=0xE84, THREADNAME="ExtUDPLogThread"
[30000] (06/29 11:55:35.380):{0x1994} [DIAG] EVENT=Unregister_thread, THREADID=0x1994, THREADNAME="StarterThread"
[30000] (06/29 11:55:35.395):{0x1A74} [DIAG] EVENT=Unregister_thread, THREADID=0x1A74, THREADNAME="StarterThread"
[30000] (06/29 11:55:35.395):{0x1910} [DIAG] EVENT=Unregister_thread, THREADID=0x1910, THREADNAME="StarterThread"
[30000] (06/29 11:55:35.426):{0x1AC8} [DIAG] EVENT=Unregister_thread, THREADID=0x1AC8, THREADNAME="StarterThread"
[30000] (06/29 11:55:35.442):{0x1FC0} [DIAG] EVENT=Unregister_thread, THREADID=0x1FC0, THREADNAME="StarterThread"
[30000] (06/29 11:55:35.442):{0x978} [DIAG] EVENT=Unregister_thread, THREADID=0x978, THREADNAME="StopperThread"
[30000] (06/29 11:55:35.442):{0xDC} [DIAG] EVENT=Unregister_thread, THREADID=0xDC, THREADNAME="StopperThread"
[30000] (06/29 11:55:35.442):{0x1988} [DIAG] EVENT=Unregister_thread, THREADID=0x1988, THREADNAME="GlobalStatsThread"
[30065] (06/29 11:55:35.551):{0x197C} BlackBerry Mailbox Agent 1 for Server SERVER shutdown complete

And then just finding this in the Event logs.   The password hasn't change recently, but they (server gurus) are wanting me to change all the BES services to start with localhost and not with the local admin account.  Maybe that'll help, though I have yet to do anything with that. 

The BlackBerry Controller service was unable to log on as .\LocalAdmin with the currently configured password due to the following error:

Logon failure: unknown user name or bad password.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).

Thank you so very much and hope this helps at least a little.

[knottyrope]

it looks as if BES was unable to talk to itself and MDS stopped.

The BES services can not be run that way, they have to use the BESAdmin service account with excetption of attachment service.

you will find out soon enough after a reboot of BES.

[ravenlite]

Thank you VERY kindly as usual! 

I'd send you chocolate if I wouldn't eat it all before putting it in the mail.

[knottyrope]

make sure you get the huge Herhey bar and dont get sick