• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 484
  • Last Modified:

Server kills rdp access on scheduled reboot - doesnt actually reboot

Hello

We have a bit of a recurring issue with one of our servers

Its a SBS 2003 box, nothing particularly special or different about the setup - but one thing that has cropped up recently is an issue that happens on its scheduled reboot

Basically, in whole - it doesn't reboot. The scheduled task fires (it emails us that it has) then is 'supposed' to reboot the server via the shutdown command

shutdown /r /t 100 /c "scheduled reboot" /f /d p:4:1

What then happens is that the server doesnt restart - we can still communicate with the server - emails, file shares and everything works fine - except we cannot connect to the server via RDP. We also cannot stop the terminal services service on the server - doesnt respond to any server commands remotely

The server just doesnt respond to RDP requests - we can still connect to the server console via the IDRAC on the machine

I've done some reading and I've seen that this can happen and that the remedy is to use the tsshutdn command in lieu - but this results in the same issue

I've also tried to stop the terminal services as part of the shutdown sequence - but this hasnt helped either

Machine is fully patched - any ideas?
0
HeronTech
Asked:
HeronTech
1 Solution
 
Venugopal NCommented:
Did the Schedule task say it run successfully, what was the exit code for the scheduled task.
0
 
Michael Ian ClaridgeActing Service Delivery ManagerCommented:
What is the resource availability look like on the server? The issue could be that the server doesn't have available memory to action the request. (Just an idea).
0
 
PaulNSWCommented:
Any anti-virus stopping it?
0
 
HeronTechAuthor Commented:
Did the Schedule task say it run successfully, what was the exit code for the scheduled task.

If you read the question - you would see that I've already addressed this. I know the scheduled task runs as the scheduled task also emails us prior to the server being rebooted (via blat)

What is the resource availability look like on the server? The issue could be that the server doesn't have available memory to action the request. (Just an idea).

Physical memory
Total physical memory - 4193500 k
Available - 2441570 k

Kernal memory
Total - 108224 k
Paged - 57064 k
Non Paged - 51144 k

Page file usage is 2.9 GB out of a total of 6 gb. It is running exchange 2003 with about 50 mailboxes or so

Any anti-virus stopping it?

Hard to say. I dont understand why the AV would allow part of the batch file to run, but not the rest. We also use the same AV on another machine in the same site that reboots in the same fashion and it does not have this same issue

Other server isnt running exchange - probably only discernable difference between the two servers
0
 
HeronTechAuthor Commented:
I ended up solving this myself - finding the overall cause to be most unusual

The scheduled reboot task - amongst other things was installing windows updates prior the reboot

This task was actually failing with no error codes. I tracked it down to a faulty update that wasnt applicable to the server - once I removed the offending update - the server has been rebooting fine since
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now