1115 ошибка shutdown

Davoud Teimouri

Davoud Teimouri is as a professional blogger, vExpert 2015/2016/2017/2018/2019/2020/2021/2022, vExpert NSX, vExpert PRO, vExpert Security, VCA, MCITP. This blog is started with simple posts and now, it has large following readers.

I had an issue last night when a remote server that I was applying windows updates to, hung while it was shutting down. I will still able to ping the server, and access its file shares, but was unable to get RDP access. I was cursing at this point, with the prospect of a long journey the following day to investigate and bring the server back online. I then considered what other steps I could take to try and force the server to reboot remotely. I used the PSTools command psexec to see if I could still get command line access to the remote server, and fortunately I could. Next I tried to force a reboot of the remote server using psexec and the shutdown command as follows, where REMOTE_SERVER_NAME is the name of the remote server that I was trying to reboot:

psexec \REMOTE_SERVER_NAME shutdown /r /t 01

alternatively you could use:

shutdown /m \REMOTE_SERVERNAME /r /t 01

This returned the following error:

1115 A system shutdown is in progress

This basically meant that a system shutdown was already in progress,  and therefore the command was unable to force a reboot. In the end I used the pskill command to stop the winlogon service on the remote server to try and release whichever process wass causing the server to hang on shutdown. I should stress that this was a last resort, and not something that I would recommend doing unless essential:

pskill \REMOTE_SERVER_NAME  winlogon

Anyway, after another few minutes the remote server did finally restart, although there are a few other things that I should mention that happened in the process. The operating system on this machine was Windows Server 2008 R2. After the server came back up (verified by ping -t REMOTE_SERVER_NAME) I tried to RDP the box again. I was able to enter my credentials and the logon process appeared to start, but after a few seconds the following message appeared on the screen:

Please wait for the Windows Modules Installer

The machine sat like that for quite some time, and then started ‘Configuring Updates’. My RDP session then abruptly ended and the server restarted itself again. Again, when it was back up I tried to RDP the server again and received the ‘Please wait for the windows modules installer message’ for a second time. Thankfully, after a few minutes and another ‘configuring updates’ message, logon continued and ther server was back up and running. On checking the event log and windows update log I was able to verify that all the updates had installed OK, and there were no other errors worthy of note. So in summary, if you want to save yourself a long trip, to most likely press a power or reset switch, you may want to try the above first.    

Recently I had an issue with one of our remote physical machines that hang during the reboot phase. Once I have initiated a reboot of the machine through the RDP connection after the system update I could see that I wasn’t able to connect to it even after 15 minutes.

Once I have tried to restart the machine using CMD with shutdown -r -m -m command I got the following warning message:

hostname: A system shutdown is in progress. (1115)

So, in order to reboot a remote physical machine I had to download and use PSTools from HERE and kill the WinLogon process on the remote machine.

Once downloaded, extract contents of the .ZIP file and run Command Prompt from the same location.

Type the following command:

pskill \hostname winlogon

where hostname is the name of the remote machine.

Once the process is killed the reboot process should continue and you’ll be able to access the remote machine again.

Comments are welcome!