question

MohdArif-7817 avatar image
0 Votes"
MohdArif-7817 asked AlexZhu-MSFT edited

WMI is in stopping state

I have 5 Hyper V nodes in cluster. Recently two nodes were not able to connect cluster name. And error was like mentioned in below doc, but one more line was added in error in the last line "Access denied". I read below document at MS.

https://docs.microsoft.com/en-us/archive/blogs/askcore/unable-to-launch-cluster-failover-manager-on-any-node-of-a-20122012r2-cluster

  1. At node A, I restarted Windows Management Instrumentation service but no luck, then ran "c:\windows\system32\wbem>mofcomp.exe cluswmi.mof". I was able to connect with cluster name immediately

  2. at node B, I opened cmd as admin, then ran same above command "c:\windows\system32\wbem>mofcomp.exe cluswmi.mof" but still I was not able to connect cluster name. Then I thought , may be a restart of WMI is required before running this command but now WMI service is stuck at "STOPPING". I tried to kill WINMGMT process but I do not see any process like this. I tried using command to query this process but no luck.

How can I fix this WMI "STOPPING" problem? this is a hyper v host and have some local VM hosted so very difficult to reboot.



windows-serverwindows-server-hyper-vwindows-server-2012
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

I would like to check if the reply could be of help? If yes, please help accept answer, so that others meet a similar issue can find useful information quickly. If you have any other concerns or questions, please feel free to feedback.

Thank you for your support!

Best regards
Joann

0 Votes 0 ·
MohdArif-7817 avatar image
0 Votes"
MohdArif-7817 answered

Actually I had tried following option but it will not give any output
sc queryex Windows Management Infrastructure

I had logged case with MS, they killed WMI Adapter process and then WMI service was started and my cluster connection came to normal state .

At other server where there was problem, I ran and it fixed the problem. So I missed killing WMI Adapter, I thought it may create some serious problem that's why I logged case with MS. Thank you very much for your help.

c:\windows\system32\wbem>mofcomp.exe cluswmi.mof"

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

jiayaozhu-MSFT avatar image
0 Votes"
jiayaozhu-MSFT answered

Hi,

Thank you for your posting!

You can follow these steps to kill WMI service process:

1) Find out the PID of the service. Open an elevated command prompt and type in:

sc queryex Windows Management Infrastructure

Make note of the PID

2) Kill the PID. From the same command prompt type in:

taskkill /f /pid [PID]

Where [PID] is the service number.

If it is successful you should receive the following message:

SUCCESS: The process with PID XXXX has been terminated.

Be careful of what you are killing though. Since WMI is a critical windows service you may end up forcing the machine to reboot on it own.

3) Restart your WMI first, and run "c:\windows\system32\wbem>mofcomp.exe cluswmi.mof" as you have done for node A. Just click the Start menu and type in the search bar type 'services.msc', find WMI and right-click "restart":
86076-case3456.jpg



Thank you for your time!

Best regards
Joann


If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


case3456.jpg (134.6 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.