KB: Host refresh in Virtual Machine Manager generates MSiSCSI Event ID 113 every 30 minutes

KB: Host refresh in Virtual Machine Manager generates MSiSCSI Event ID 113 every 30 minutes

  • Comments 1
  • Likes

imageThis Knowledge Base article talks about an issue where doing a host refresh in VMM generates MSiSCSI Event ID 113 every 30 minutes:

Symptoms

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:

Log Name: System
Source: MSiSCSI
Event ID: 113
Level: Warning
Computer: server.contoso.com
Description:
iSCSI discovery via SendTargets failed with error code 0xefff0003 to target portal *172.16.0.10 0003260 B06BDRV\L4SC&PCI_163914E4&SUBSYS_02D41028&REV_20\5&16d0e046&0&30050200_0
Cause

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

Resolution

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.

More Information

The symptom might also appears if a manual refresh of the host is initiated from VMM.

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 of 0xefff0003 // ERROR_PATH_NOT_FOUND.

=====

For the most current version of this article please see the following:

2569351 - Host refresh in Virtual Machine Manager generates MSiSCSI Event ID 113 every 30 minutes

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • This results in Target list in Iscsi initiator being empty! Need to reboot to reconfigure.