Dispatcher, Policy Service stuck on "starting" after reboot on 4.1.6
I was having a problem starting last week maybe monday-tuesday on a 4.1.6 server with Exchange 2007 (on a Small Business Server 2008) The BES server is on a separate box. Basically the users said they could receive emails but could NOT send them. I haven't done anything to either server except for some automatic Microsoft updates every once in a while.
I visited the site last Friday and without knowing what else to do just tried restarting the BES server in case there was a problem with a patch not finishing. It's basically stuck now and will never finish rebooting - I can't even get to the login screen. I can however connect to C$ shares and open the services panel remotely from my other server and I can see the Blackberry Policy Services and Blackberry Dispatcher are both frozen in the "starting" state. I can't even RDP to this box or login locally. Everything has been working flawlessley since February so I'm sure I don't have any settings messed up, unless it could have something to do with recent OS patches or exchange patches?
I'm trying to get the business to re-up their support contract with RIM but they are having cash flow problems and scrambling to come up with funding to do it. Has anyone seen this issue and may know what I'm looking at here?
Stop all BES services or set to manual and see if it boots up.
That should rule out BES being the issue.
Yeah, something is definitly messed up. I left it all weekend and those services are STILL sitting on "starting" after a couple days. Since it's still in the process of trying to turn on services it won't let me make any changes remotely. I'm going to have to drive back out there and get into safe mode.
I supposed I was hoping that this was a common problem that other people would know off the top of their head - searches and KB articles haven't gotten me anywhere yet.
I've experienced this as well recently (BES 4.1 SP6 MR5). My workaround was to set the Dispatcher service to manual and to manually start this service everytime it has to be rebooted (once / month for Microsoft patching). I'm hoping this problem goes away after we upgrade to 5.0 (next few weeks).
|All times are GMT -5. The time now is 07:02 AM.|
Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.