Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

Running Hyper-V server and 1 of the v-servers froze

Running Hyper-V server and 1 of the v-servers froze. User were still able to access the database but when trying to browse to a report, the server would just hang.
When attempting to connect , server just hung when trying to clicking on anything...
Finally had to shut off and this resolved the issue...
Isolated the problem to occur right around the following event:
event 1:
The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout.
event 2:
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.

The server has been running fine and the only change is memory was added last week to the cluster... also there are 3 other v servers in the cluster and they were fine.


  • 2
1 Solution
Brian BIndependant Technology ProfessionalCommented:
So one of the guests froze? Has the problem occured since?

If it has been okay since, I would not worry about it too much. Just make sure you have backups in case the server totally fails.

I have seen these DCOM errors on a lot of machines that are working just fine. Try filtering the event log on the ID associated with that error and see if it has happened at other times. Sometimes bad coding in an application causes these. Having said that, the errors can be fixed by fixing the security settings on the key mention. However, you don't want to take away security if you can avoid it.

The second event may indicate where the problem originated. That almost seems to indicate some sort of loss of network connectivity. So I would also recommend checking the logs on the host around that time and see if there are any associated errors.
cslingerAuthor Commented:
This is the only time and there are no other events concerning DCOM logs.
I did notice an amber light on my cluster (DELL PE 710) with attached MD3200 array.
Looking into this error further, the message is :

There is a problem accessing the virtual disk through the preferred RAID Controller Module listed in the Recovery Guru Details Area. The virtual disk is being accessed on the non-preferred path (alternate RAID Controller Module). This procedure will help you pinpoint the problem along the data path. Because the virtual disk is on the alternate RAID Controller Module, it should still be accessible.

I did speak with DELL and I am going to change it to the preferred controller after hours...
Do you think this could have caused the problem ?
Brian BIndependant Technology ProfessionalCommented:
It could be a combination of items... The controller glitched, which caused it to fail over to secondary. This caused an interruption in the data stream which threw off the data communications, hence the DCOM error. So the server locked up.

I had something like that happen on the hardware side and with instructions from Dell, the switchover was fairly easy.

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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