If that is happening to my Ethernet then it appears that Hyper-V is recovering from the transient failure, but the Essentials VM may not be recovering? I have two other VMs on this Hyper-V server. In which people with a similar error mentioned seeing their Intel Ethernet drop off the network and then recover. I came across two earlier events that might have something to do with my problem? I haven't had time to look at these in detail yet, but it looks like the Intel Ethernet is occasionally taking some type of a hit/error? I came across some postings The replication was interrupted and I took a look at the Event Log. I started trying to replicate from this Hyper-V server to another yesterday. Is responding, but the Essentials VM has lost its network connection? But I'm not 100% sure the VM is responding? Would PINGs be offloaded to the physical adapter such that the Ethernet adapter I am able to PING the Essentials VM (after the Kerberos error has occurred) and am getting less than 1 ms response time. I'm a SOHO user and not familiar with some of the Microsoft terminology, but I believe Essentials is my DC? Given that I have to reboot to recover I'm not aware of any way I could capture packets on the DC and preserve the trace over a reboot? So what should I be looking for to find my problem? I tried searching from the bottom towards the top looking for "err" or "fail," but none of the messages I came across looked significant.
Although there are some gaps in the timestamps none of the messages looked obvious to me that they're pointing towards my problem. I tried going to the bottom of gpsvc.bak and working backwards. I was hoping to use that as a reference point to know that I could ignore any messages that came after the reboot (which appears to occur before the new gpsvc.log file is created). It was not obvious to me where my reboot began. GPSVC(2c8.2d8) 21:24:19:134 CGPNotify::RegisterForNotification: Exiting with status = 0 As the timestamp of the last line in the gpsvc.bak is very close to the timestamp of the first line in gpsvc.log. GPSVC(384.390) 21:24:20:074 CGPService::Start with flags = 0x0.īut the logging seemed to continue after I started the reboot. This seems to be the "start" of something. These type of messages appear at the top of both files. I assume gpsvc.bak was data collected prior to my reboot? I rebooted it once this morning and by the time I got home it seemed to be hung (Kerberos problem) again so I had to reboot it again.įrom the URL you mentioned I found gpsvc.log and gpsvc.bak files. Essentials has hung at least twice today. Thanks for any assistance in resolving my problems. The winlogon notification subscriber is taking long time to handle the notification event (CreateSession). The winlogon notification subscriber took 120 second(s) to handle the notification event (CreateSession).
Tp link tg 3468 windows server 2008 r2 driver windows 8.1#
I did see these two alerts, but I think that these are symptoms of the same problem that is causing the Windows 8.1 logoff When I checked the Event Log on Essentials I don't see any messages that look liked they'd explain what is causing these problems. It may be a coincidence, but I believe about 2-3 weeks ago was the last time I updated Essentials and Windows 8.1 and picked up all the available OS patches? It may be that one of those patches has a problem? When the Kerberos problem is not happening it takes about 2 seconds for the Windows 8.1 logout to complete.ĭuring this time I am able to use Remote Desktop and logon to my Hyper-V server and everything seems to be working normally, i.e., it is not running slow. The logout eventuallyĬompletes, but it is abnormally long. I've also noticed that once this error occurs another symptom is that from the Windows 8.1 client (Domain logged on) when I try and logoff it hangs with the message "Signing Out" for 5-10 minutes (or perhaps longer). I have setup the Hyper-V Server and Windows 8.1 clients in my home network to all use Domain logons. One symptom is that from Server Manager (on my Windows 8.1 client) I get a "Kerberos authentication error" when trying to connect to the Hyper-V server or Essentials. In the past 2-3 weeks I've been having problems. I have been running Windows Server 2012 R2 Essentials as a VM on Hyper-V Server 2012 R2 (Server Core) for several months.
0 kommentar(er)
