![]() Event id 1146 microsoft windows failover clustering tools keygen#![]() Failed to receive data for a Virtual Machine migration: An existing connection was forcibly closed by the remote host. Planned virtual machine creation failed for virtual machine ‘SRV13’: An existing connection was forcibly closed by the remote host. ![]() If the live migration fails, then an error event like the following one is likely to be found in the System event log on the host: Log Name: Microsoft-Windows-Hyper-V-VMMS-Adminĭescription: The Virtual Machine Management service initiated the live migration of virtual machine ‘SRV3’ to destination host ‘BOX2’ For example, when a live migration is initiated an event (information has been abbreviated) similar to the following will be logged in the Hyper-V-VMMS-Admin log: That’s because the Virtual Machine Management Service (VMMS) on a Hyper-V host manages many of the key functions of such hosts and the virtual machines running on those hosts. Using Hyper-V event logs for troubleshootingĪpart from the System event log, the Hyper-V-VMMS event log channel is probably where you want to start most times when you’re troubleshooting problems. Note also that some of these types of channel are only collected after the administrator has turned on logging for that particular type of channel. For example, the figure below shows four types of event logs in the Hyper-V-VMMS event channel. Note that event logs also come in various channel types such as Admin, Analytic, Debug, Diagnostic, Operational, Networking, Reservation, and Storage. For a brief but helpful explanation of what kinds of events some of these different event channels log you can see this post by Lars Iwer on the Microsoft Virtualization Blog. Analytic and Debug are two types of logs of this nature. Note also that certain kinds of event logs are only present in a channel if they have been turned on. For example, the Hyper-V High-Availability event channel requires that the Failover Clustering feature is installed on the host. Note that some of these event channels may not be present on your host if certain features aren’t enabled. The following table lists the available channels for Hyper-V in each version of Windows Server as best I’ve been able to determine based on the limited amount of documentation Microsoft provides: Event log channel And as new capabilities have been added to Hyper-V in Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 there have been corresponding changes in which event log channels are defined on these platforms. Hyper-V was first introduced in Windows Server 2008, but it’s been enhanced over the years with additional features as the Windows Server platform itself has continued to evolve. ![]() Hyper-V, of course, is the hypervisor technology that provides virtualization capabilities in the Windows Server platform. The trapped events can also be collected and analyzed by using Windows PowerShell cmdlets like Get-EventLog and Get-WinEvent. The trapped events can then be read using an event log collector tool such as the built-in Event Viewer tool. Basically, you can picture an event log channel as a kind of sink that traps certain kinds of events happening on the system. When an event of some sort occurs on a Windows Server system such as a Hyper-V host - for example when a virtual machine shuts down on the host - the event is written to the appropriate event log channel. In a future article, we’ll examine how you can use PowerShell to get events from event logs and glean useful information from them. ![]() This article examines some of the event channels you might want to use when you need to troubleshoot Hyper-V hosts and the virtual machines running on these hosts. Fourth and finally, Microsoft’s online documentation of event log channels for Windows Server is somewhat lacking, to say the least. That means, of course, that you’ll need some proficiency with PowerShell to work effectively with the event logs. Third, the Event Viewer administrative console is somewhat clunky to work with so you’re better off using Windows PowerShell to grab and analyze events. Second, the names given to event channels by Microsoft are often cryptic and unusual. First, there are a lot of different event channels in Windows Server and the ones displayed will depend upon not only on which server roles and features you have installed but also on which version of Windows Server you’re working with. Navigating them can be challenging, however, for several reasons. The event logs in Windows Server are one of the first places you should look when something goes wrong. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |