topic Re: SnapManager for Hyper V wmi error in Microsoft Virtualization Discussions

SnapManager for Hyper V wmi error

afranchetto — Thu, 05 Jun 2025 07:11:29 GMT

Hello, I have a WMI error when I want list the virtual machine of my Windows 2008 R2 Hyper-v WFC Cluster. You can see the error in the attachment.

The host wizard was run successfully.

Can you help me please?

Snapdrive 6.2

FC host utlilities 5.3

DOT 7.33

MPIO 3.3

Re: SnapManager for Hyper V wmi error

vkarinta — Mon, 26 Jul 2010 03:37:32 GMT

Hi,

I am not able to understand the message in the event log since its non-english.

Can you please run the following command from the command prompt on the Hyper-V Server, [You need to have SnapDrive for Windows installed on this sytem]

sdcli hyperv list

If you are able to see the VM listed here, then restart the SnapMgrServiceHost process and try to view the VMs from SnapManager for Hyper-V MMC SnapIn/

Other wise you need to upload the ONTAPWinDC output from this system, In that case it's better to contact NGS to get a faster attention to this issue.

Thanks,

Vineeth

Re: SnapManager for Hyper V wmi error

alexleucart — Mon, 26 Jul 2010 08:00:44 GMT

I work with afranchetto. You can find the event in english below :

Access to the root\MSCluster namespace was denied because the namespace is marked with RequiresEncryption but the script or application attempted to connect to this namespace with an authentication level below Pkt_Privacy. Change the authentication level to Pkt_Privacy and run the script or application again.

We have tried the command : 'sdcli hyperv list' and no result appear in the list.

We will try ONTAPWinDC on the hyper-v system.

Thanks,

Alex

Re: SnapManager for Hyper V wmi error

dennis_von_eulenburg — Fri, 30 Jul 2010 07:39:03 GMT

Hi afranchetto,

I've got the same problem last week

But don't panic, it is pretty simple to fix. In the most non-english versions of windows 2008 this error occurs. You have to install Snapdrive 6.2P1 and SMHV 1.0P1 on every Clusternode.

You can run the SD 6.2P1 setup without deinstall SD 6.2 and also without a reboot. For safty reasons, I would move the VMs from one Clusternode to another while updating SD & SMHV.

P.S: I had the problem with a german Windows 2008 but your problem with a french System exactly looks the same. Also the Event ID is the same one.

Hope this helps

Dennis

Re: SnapManager for Hyper V wmi error

amritad — Fri, 30 Jul 2010 09:13:53 GMT

I would agree with Dennis. We did see localization issues which got fixed by SD 6.2 P1 patch. We have seen these on French and German OS. So please upgrade SDW. In case you still see issues please do let us know.

Regards

Amrita

Re: SnapManager for Hyper V wmi error

afranchetto — Tue, 10 Aug 2010 09:24:36 GMT

Hello, thanks for your reponse.

The SP1 patch have resolved the bug but now snapdrive crash on the vm backup. The Event id is 1000 and the description is :

Nom de l’application défaillante SWSvc.exe, version : 6.2.0.5007, horodatage : 0x4b950b67

Nom du module défaillant : MSVCR90.dll, version : 9.0.30729.4926, horodatage : 0x4a1750b0

Code d’exception : 0xc0000417

Décalage d’erreur : 0x0000000000054fc0

ID du processus défaillant : 0x1518

Heure de début de l’application défaillante : 0x01cb3868a4cab967

Chemin d’accès de l’application défaillante : C:\Program Files\NetApp\SnapDrive\SWSvc.exe

Chemin d’accès du module défaillant: C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba83fe554\MSVCR90.dll

ID de rapport : 29627ced-a45f-11df-926a-d8d385fd7d6c

and after, I have an another event 106 :

SnapManager for Hyper-V backup failed to complete

Backup of the Dataset Name: soft

Backup id: 434e61f4-d3d7-442b-ac15-a5257d08f935 failed to execute

Error :Fatal Error: The Hyper-V virtual machine enumeration failed.

Backup status of the virtual machines involved in this backup operation are given below

Backup Failed for

VM Name: SRVIMP2 VM ID: C34635CE-0D26-45FC-B8BE-D37847A83796

My version of windows is French

Do you have some idea?

thanks

Re: SnapManager for Hyper V wmi error

amritad — Tue, 10 Aug 2010 10:14:53 GMT

CAn you try 1 thing. Restart SDW first and then SMHV. Then try a fresh backup. What happens after that?

REgards

Amrita

Re: SnapManager for Hyper V wmi error

dennis_von_eulenburg — Tue, 10 Aug 2010 10:49:20 GMT

Hi afranchetto,

is it possible that the partitionstyle of your Clustersharded Volume is MBR?

Re: SnapManager for Hyper V wmi error

afranchetto — Tue, 10 Aug 2010 14:38:34 GMT

No change after restart sdw, smhv and reboot all nodes of cluster

Re: SnapManager for Hyper V wmi error

barve — Tue, 10 Aug 2010 17:07:31 GMT

If the backup is still failing with SWSVC crash, I would recommend taking a new ONTAPWinDC and opening a case with NGS.

Re: SnapManager for Hyper V wmi error

afranchetto — Tue, 10 Aug 2010 18:04:57 GMT

all luns has being created with snapdrive. I have not make a modification of the partition.

Re: SnapManager for Hyper V wmi error

vkarinta — Tue, 10 Aug 2010 18:16:32 GMT

MBR partition for the CSV is not supported in SMHV 1.0, the backup will fail during the rename snapshot step if the CSV LUN has MBR partition

[Microsoft volume guid mismatch issue ]. But we did not see this issue causing SnapDrive crash.

In your case looks like the SnapDrive crash happened while enumerating the VMs for a host during the SMHV backup.

Please upload the ONTAPWinDC and open the case with NGS for this issue.

Thanks,

Vineeth

Re: SnapManager for Hyper V wmi error

afranchetto — Tue, 10 Aug 2010 20:30:22 GMT

Hello it's a GPT Partition, you cas see WINDC log after.

Thanks

UNC Path: None
LUN Path: SRVNAS1:/vol/vol_san/lun_quorum
Storage System: SRVNAS1
Storage System Path: /vol/vol_san/lun_quorum
Type:   lun
Disk serial number: P3mcOoXxD48T
Backed by Snapshot Copy:
Shared:   Yes
BootOrSystem Disk: No
SCSI port: 4
Bus:   0
Target:   0
LUN:   0
Readonly: No
Size:   1027 MB
Snapmirror Source: No
Snapvault Primary: No
Disk Partition Style: GUID Partition Table (GPT)
Clone Split Restore status: Normal
DiskID:   3
Volume Name: \\?\Volume{136f33f7-d3e6-42b7-a64e-7694879e0812}\
Mount points: Q:\
IP Addresses: 128.2.1.232
FC initiator WWPN: 10:00:00:00:c9:b0:99:04

UNC Path: None
LUN Path: SRVNAS1:/vol/vol_san/lun_smhv_snapinfo
Storage System: SRVNAS1
Storage System Path: /vol/vol_san/lun_smhv_snapinfo
Type:   lun
Disk serial number: P3mcOoXzGLUy
Backed by Snapshot Copy:
Shared:   Yes
BootOrSystem Disk: No
SCSI port: 4
Bus:   0
Target:   0
LUN:   3
Readonly: No
Size:   20481 MB
Snapmirror Source: No
Snapvault Primary: No
Disk Partition Style: GUID Partition Table (GPT)
Clone Split Restore status: Normal
DiskID:   1
Volume Name: \\?\Volume{f6a328e9-58e9-4523-a4cc-3ad2a787f897}\
Mount points: T:\
IP Addresses: 128.2.1.232
FC initiator WWPN: 10:00:00:00:c9:b0:99:04

UNC Path: None
LUN Path: SRVNAS1:/vol/vol_san/srvexch1_mailbox_log/lun_srvexch01_log
Storage System: SRVNAS1
Storage System Path: /vol/vol_san/srvexch1_mailbox_log/lun_srvexch01_log
Hyper-V Passthrough: Yes
Hyper-V VM Name: SRVEXCH01
Type:   lun
Disk serial number: P3mcOoYMJqs0
Backed by Snapshot Copy:
Shared:   Yes
BootOrSystem Disk: No
SCSI port: 4
Bus:   0
Target:   0
LUN:   8
Readonly: No
Size:   10244 MB
Snapmirror Source: No
Snapvault Primary: No
Disk Partition Style: GUID Partition Table (GPT)
Clone Split Restore status: Normal
DiskID:   9
Volume Name: <Not Available>
Mount points: <Not Available>
IP Addresses: 128.2.1.232
FC initiator WWPN: 10:00:00:00:c9:b0:99:04

UNC Path: None
LUN Path: SRVNAS2:/vol/vol_san/lun_hyperv_vol1
Storage System: SRVNAS2
Storage System Path: /vol/vol_san/lun_hyperv_vol1
Hyper-V VHD Present: Yes
Hyper-V VMs Name: SRVIMP1, SRVEXCH01, SRVAD2, SRVTS1, GLPI, INTRANET, TAXATION, ORACSERV3, SRVAPP1, SRVTS01, SRVBADGE, ORACSERV2, ORACSERV1, SRVIMP2
Type:   lun
Disk serial number: P3mcNZXxDJkA
Backed by Snapshot Copy:
Shared:   Yes
CSV Disk: Yes
BootOrSystem Disk: No
SCSI port: 3
Bus:   0
Target:   0
LUN:   1
Readonly: No
Size:   614486 MB
Snapmirror Source: No
Snapvault Primary: No
Disk Partition Style: GUID Partition Table (GPT)
Clone Split Restore status: Normal
DiskID:   2
Volume Name: \\?\Volume{dc1ae0b6-728f-4371-bdb6-ecc1b51d20f4}\
Mount point: <Not Available>
CSV Reparse Point: C:\ClusterStorage\Volume1
IP Addresses: 128.2.1.233
FC initiator WWPN: 10:00:00:00:c9:b0:97:b1

UNC Path: None
LUN Path: SRVNAS2:/vol/vol_san/lun_RAW1
Storage System: SRVNAS2
Storage System Path: /vol/vol_san/lun_RAW1
Type:   lun
Disk serial number: P3mcNZXyRyzX
Backed by Snapshot Copy:
Shared:   No
BootOrSystem Disk: No
SCSI port: 4
Bus:   0
Target:   1
LUN:   2
Readonly: No
Size:   15366 MB
Snapmirror Source: No
Snapvault Primary: No
Disk Partition Style: GUID Partition Table (GPT)
Clone Split Restore status: Normal
DiskID:   8
Volume Name: <Not Available>
Mount points: <Not Available>
IP Addresses: 128.2.1.233
FC initiator WWPN: 10:00:00:00:c9:b0:99:04

UNC Path: None
LUN Path: SRVNAS2:/vol/vol_oracserv1/lun_oracserv1
Storage System: SRVNAS2
Storage System Path: /vol/vol_oracserv1/lun_oracserv1
Hyper-V Passthrough: Yes
Hyper-V VM Name: ORACSERV1
Type:   lun
Disk serial number: P3mcNZY0eFUa
Backed by Snapshot Copy:
Shared:   Yes
BootOrSystem Disk: No
SCSI port: 4
Bus:   0
Target:   1
LUN:   4
Readonly: No
Size:   30725 MB
Snapmirror Source: No
Snapvault Primary: No
Disk Partition Style: GUID Partition Table (GPT)
Clone Split Restore status: Normal
DiskID:   4
Volume Name: <Not Available>
Mount points: <Not Available>
IP Addresses: 128.2.1.233
FC initiator WWPN: 10:00:00:00:c9:b0:99:04

UNC Path: None
LUN Path: SRVNAS2:/vol/vol_oracserv2/lun_oracserv2
Storage System: SRVNAS2
Storage System Path: /vol/vol_oracserv2/lun_oracserv2
Hyper-V Passthrough: Yes
Hyper-V VM Name: ORACSERV2
Type:   lun
Disk serial number: P3mcNZY0eZq6
Backed by Snapshot Copy:
Shared:   Yes
BootOrSystem Disk: No
SCSI port: 4
Bus:   0
Target:   1
LUN:   5
Readonly: No
Size:   30725 MB
Snapmirror Source: No
Snapvault Primary: No
Disk Partition Style: GUID Partition Table (GPT)
Clone Split Restore status: Normal
DiskID:   5
Volume Name: <Not Available>
Mount points: <Not Available>
IP Addresses: 128.2.1.233
FC initiator WWPN: 10:00:00:00:c9:b0:99:04

UNC Path: None
LUN Path: SRVNAS2:/vol/vol_oracserv3/lun_oracserv3
Storage System: SRVNAS2
Storage System Path: /vol/vol_oracserv3/lun_oracserv3
Hyper-V Passthrough: Yes
Hyper-V VM Name: ORACSERV3
Type:   lun
Disk serial number: P3mcNZY0fMml
Backed by Snapshot Copy:
Shared:   Yes
BootOrSystem Disk: No
SCSI port: 4
Bus:   0
Target:   1
LUN:   6
Readonly: No
Size:   30725 MB
Snapmirror Source: No
Snapvault Primary: No
Disk Partition Style: GUID Partition Table (GPT)
Clone Split Restore status: Normal
DiskID:   6
Volume Name: <Not Available>
Mount points: <Not Available>
IP Addresses: 128.2.1.233
FC initiator WWPN: 10:00:00:00:c9:b0:99:04

UNC Path: None
LUN Path: SRVNAS2:/vol/vol_srvexch1/srvexch1_mailbox_data/lun_srvexch1
Storage System: SRVNAS2
Storage System Path: /vol/vol_srvexch1/srvexch1_mailbox_data/lun_srvexch1
Hyper-V Passthrough: Yes
Hyper-V VMs Name: SRVEXCH01, SRVEXCH1
Type:   lun
Disk serial number: P3mcNZY0fooY
Backed by Snapshot Copy:
Shared:   Yes
BootOrSystem Disk: No
SCSI port: 4
Bus:   0
Target:   1
LUN:   7
Readonly: No
Size:   117773 MB
Snapmirror Source: No
Snapvault Primary: No
Disk Partition Style: GUID Partition Table (GPT)
Clone Split Restore status: Normal
DiskID:   7
Volume Name: <Not Available>
Mount points: <Not Available>
IP Addresses: 128.2.1.233
FC initiator WWPN: 10:00:00:00:c9:b0:99:04
The operation completed successfully.