I've scoured google for help identifying what service is causing my hang, but all I get back are "Stop a hung service", which would be useful if my service hung before the shutdown. So my main question is: What can I do to walk through the shutdown process and identify the faulting service? Is there any powershell magic that could help me here, or possibly a 3rd party utility that would allow me to see what's going on during shutdown? This happened to me with a physical R2 server with the Hyper-V role installed.
I had to keep hard resetting it to get it to reboot. Then one evening, I was doing some patching and thought I would try to find out why it was doing this, rather than just hard resetting yet again. After a lot of digging, I finally realised it was due to some old VM snapshots that I had forgotten about.
During the shutdown, the server appears to hang but in the background, Hyper-V was trying to merge the VHD and snapshot files, as it was designed to do. Once it let it do its work took quite a while , that was the end of the problem. I realise your question was regarding a VM rather than a physical server but it still might be worth checking for snapshot files in your VHD folder s.
I'll go check that right now. I've had a problem with Hyper-V not merging snapshots previously said they were merged, but upon closer inspection, snapshots were still active in the repository - I didn't even think about that as an option.
When you try to stop the Server service on a computer that is running Windows Vista or Windows Server , the Server service stops responding.
This issue occurs because a race condition occurs during the oplock processing when you are using Server Message Block SMB Version 2 protocol. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem that is described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not exist, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix.
For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:. If you do not see your language, it is because a hotfix is not available for that language. For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. Do you mean that this problem occurred after you installed some updates? Would you please try the System Update Readiness Tool to see which update is not installed successfully? If there are any corrupted updates, you can try removing them and then try to install that update manually.
You can download it from the following link. After installing it, there will be an log file, named CheckSUR. Open this file to see which update caused the problem. For detailed information about how to fully remove this update, I would suggest that you post this issue in our Windows Update newsgroup to efficiently remove the update:. Besides, as this seems related to Exchange, I would like to suggest that you post this in our Exchange Server forum to efficiently resolve the problem and to prevent potential problems that may corrupt the Exchange Server.
Good luck. Best regards,.
0コメント