[chrislehr]

When I shutdown our BES 5.0.1 MR2 on Windows 2008 R2 server and restart it, I get prompted to enter a reason for the unexpected shutdown. If I stop all BES services before I shut down or restart, I don't get this. Is there something that I can do to make Windows 2008 R2 wait for BES services to stop gracefully before if shuts it self down?

I found these articles that somewhat references shutdown of services but doesnt really include the how to.
WS2008: Service Shutdown and Crash Handling - Ask the Performance Team - Site Home - TechNet Blogs
Windows Administration: Inside the Windows Vista Kernel: Part 2

Anyone else had this problem? Other than stopping the BES services manually, have you found a better fix?

[RadHaz75]

+1

i have experienced this too and never knew why.

[TargetIT]

You could just write a script that stops the services...

net stop <insert BB service here>
net stop <insert BB service here>
net stop <insert BB service here>
net stop <insert BB service here>
net stop <insert BB service here>
net stop <insert BB service here>
shutdown /r

Save it as a .bat on the desktop and away you go.

[chrislehr]

Originally Posted by TargetIT

You could just write a script that stops the services...

net stop <insert BB service here>
net stop <insert BB service here>
net stop <insert BB service here>
net stop <insert BB service here>
net stop <insert BB service here>
net stop <insert BB service here>
shutdown /r

Save it as a .bat on the desktop and away you go.

Well aware of this workaround. But it's just that, its working around the problem. Perhaps this is more a Windows 2008 R2 question than a BES question. Ill post on Technet later today and see if I get any feedback there on a way to make the OS wait patiently for services to stop.

[TargetIT]

Perhaps, or perhaps it's the order in which it's trying to shut the services down in. How long does it take from the moment you hit restart to the moment it reboots? 30 seconds? 5 minutes? This is the reg key if you want to play with it:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\WaitToKillServiceTimeout

[RadHaz75]

what is the value unit? mine is currently set to 12000. im assuming its milliseconds, which would equate this to 12 seconds. i changed it to 60 seconds (60000) and the error still occurred. so i then i tried 2 minutes (120000) still with no success.

[TargetIT]

It's ms. But is it taking 2 minutes to shutdown? In other words, is it really getting stuck on shutting down the services or is it something else it's having issues with.

[chrislehr]

I just did another install on 2008 R2 - this time BES enteprise Express.. and have the exact same problem. I am going to bump the WaitToKillService from the default (600000ms, or 10 minutes) to 20 minutes (1200000) and will see how that works.

[RadHaz75]

Originally Posted by TargetIT

It's ms. But is it taking 2 minutes to shutdown? In other words, is it really getting stuck on shutting down the services or is it something else it's having issues with.

it definitely did not wait the full 2 minutes. so either bes services are shutting down properly and something else is causing the error or the key does not work correctly and is not waiting the set time

[kjarrodc]

+2

I can attest to having this problem as well.

[plauderer]

I'm experiencing the same issue

my details:
Windows Server 2008 R2 Std. 64bit
BlackBerry Enterprise Server 5.0.1 MR2

Anyone found an explanantion/solution for this yet?

[chrislehr]

One of you has to have a T-support account to escalate this with? (I don't, I work customer networks only)

[plauderer]

Not me. Same situation as yours. Telco-Provider can't help either.

[r2k]

Hi folks,

same here with 5.0.2 :(

[BettyB-IT]

I am experiencing the same issue. Windows server 2008 R2 x64. BES 5.

I've opened a case with Microsoft and they are currently telling me it's a hardware issue and I need to talk to Dell.

So - has anyone resolved this?

[RadHaz75]

Originally Posted by BettyB-IT

I am experiencing the same issue. Windows server 2008 R2 x64. BES 5.

I've opened a case with Microsoft and they are currently telling me it's a hardware issue and I need to talk to Dell.

So - has anyone resolved this?

bwahahaha M$. mine are on VM

[TargetIT]

Originally Posted by RadHaz75

bwahahaha M$. mine are on VM

"Oh, well you should be running Hyper-V, we don't support VM - nor do our licensing models..."

[HammerofDawn]

I have the same problem, Windows Server 2008 R2 x64 on Dell PowerEdge R510. I just upgraded to BESX 5.0.2, but the problem is persisting. Has anyone contacted RIM Tech Support?

[kovan]

Me too !

Installed a new Windows 2008 R2 x64 VM (with all updates) on top op our Xenserver 5.6 virtual infrastructure. Then installed 5.0.1.31. Each time I reboot or shutdown the VM, after restart I receive the same 'last shutdown was unexpected' error.

So this is definitely not hardware related.

[RadHaz75]

does anyone have 5.0 sp2 and still have this issue. this is listed as a fixed issue in sp2 and sounds similar to what has been discussed in this thread...

When the BlackBerry® Controller stopped, it did not use the timeout value of the AgentShutdownTimeout registry key. (DT 485302)