M
miked011
Apologies if this post is misplaced. First time posting a question.
I have a 2016 file server that we found non responsive this morning. It's a VM hosted on VMware ESXi managed by vCenter. It did respond to pings, but I couldn't establish an RDP session. I tried accessing it directly through the VMware console, and that wouldn't load either. I ended up having to hard power it down in VMware and bring it back up, at which point it was fine.
Based on user complaints starting yesterday morning, I suspected that's when it went down. In looking at the event logs, I see starting around 10:00 AM on 2/9 a series of errors like this:
Unable to start a DCOM Server: {1F87137D-0E7C-44D5-8C73-4EFFB68962F2}. The error:
"1450"
Happened while starting this command:
C:\windows\sysWOW64\wbem\wmiprvse.exe -secured -Embedding
There are over 400 events like this from 2/9 through the morning of 2/10 when I powered off the server. I tried digging in forums to see what this pointed to, but while I found similar issues, I didn't find one with a 1450 error pointing at the wmiprvse.exe file. Any help on finding out what exactly was going on based on these errors would be appreciated.
Continue reading...
I have a 2016 file server that we found non responsive this morning. It's a VM hosted on VMware ESXi managed by vCenter. It did respond to pings, but I couldn't establish an RDP session. I tried accessing it directly through the VMware console, and that wouldn't load either. I ended up having to hard power it down in VMware and bring it back up, at which point it was fine.
Based on user complaints starting yesterday morning, I suspected that's when it went down. In looking at the event logs, I see starting around 10:00 AM on 2/9 a series of errors like this:
Unable to start a DCOM Server: {1F87137D-0E7C-44D5-8C73-4EFFB68962F2}. The error:
"1450"
Happened while starting this command:
C:\windows\sysWOW64\wbem\wmiprvse.exe -secured -Embedding
There are over 400 events like this from 2/9 through the morning of 2/10 when I powered off the server. I tried digging in forums to see what this pointed to, but while I found similar issues, I didn't find one with a 1450 error pointing at the wmiprvse.exe file. Any help on finding out what exactly was going on based on these errors would be appreciated.
Continue reading...