Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.
On a Hyper-V host that is managed by System Center Virtual Machine Manager 2008 (VMM 2008), an event ID 113 or event ID 1 is logged every 30 minutes or more:
On the SAN you may see iSCSI session login/logout's occur at the same time. During the Host Refresh, SCVMM generates a SendTargets=ALL request to the SAN to determine if there have been any changes.
Automatic or manual VMM Host refresh can create these events. VMM queries a WMI path during the scan of physical disks which includes iSCSI SAN disks.
WMI path: schemas.microsoft.com/wbem/wsman/1/wmi/root/wmi/MSiSCSIInitiator_MethodClass
Some storage providers have confirmed this event can be seen and reproduced in some configurations when making WMI queries to the above namespace. This specific warning message can be safely ignored.
During the refresh, VMM is performing a scan for changes on the host machine, checking changes to items such as the following:
• Updates to virtualization host properties and status
• Updates to physical disks and SAN information
• Updates to networking information like physical nics and virtual switches
It is during the scan of physical disks and SAN information that the iSCSI devices are being polled and the above event is logged with a status of0xefff0003 // ERROR_PATH_NOT_FOUND.
Keywords: vkball, kb