SnapManager for Hyper V wmi error

[afranchetto]

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

[vkarinta]

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

[alexleucart]

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

[dennis_von_eulenburg]

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

[amritad]

Hi

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

[afranchetto]

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

[amritad]

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

REgards

Amrita

[dennis_von_eulenburg]

Hi afranchetto,

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

[afranchetto]

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

[barve]

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