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-4
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.
thanks
cj
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-4
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.
thanks
cj
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
I had something like that happen on the hardware side and with instructions from Dell, the switchover was fairly easy.
ASKER
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 ?