iSCSI Management Missing in SnapDrive

[kumar_savi]

Hi All,

Currently I am facing one issue with SnapDrive. Not able to see the iSCSI Management Option in SnapDrive after one reboot. Before rebooting was able to connect the storage successfully.

Please can anyone have an idea on this. Thanks in advance.

Its kind of urgent.

Regards,

Savi

[NDELAMOTTEGSP]

I have the same problem :

snapdrive 6.5

DSM 4.0

Windows server 2012 datacenter with Hyper-V

with

without

And after seeing some fetaures on the snapdrive, the snapin hangs and failed. After the reboot, i loss the iscsi management.

and failed

Is there something between windows server 2012 and snapdrive that I missed?

Thank you for your help

[brauntvr2swiss]

Hi Savi

We have had the same Problem with Snapdrive under 2003 and 2008. Our workaround was to configure following Service Dependency:

- Open a cmd

     sc config SDMgmtSvc depend= SWSvc

This config guarantee, that first start the Snapdrive Service and then the Snapdrive Management Service.

regards

Thomas

[NDELAMOTTEGSP]

When i made the recommandation of braunt-vr2swiss, the snaping hangs on "connecting" :

[brauntvr2swiss]

Hi Nicolas

Are the 2 Services Started?

regards

Thomas

[NDELAMOTTEGSP]

yes they are both started :

[NDELAMOTTEGSP]

but app chrashes :

Fault bucket 97375060, type 4

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: SWSvc.exe

P2: 6.5.0.5474

P3: 50d0499b

P4: StackHash_6d63

P5: 6.2.9200.16384

P6: 5010acd2

P7: c0000374

P8: PCH_62_FROM_ntdll+0x0000000000002BEA

P9:

P10:

Attached files:

C:\Users\VMM_ManageHost\AppData\Local\Temp\WERAD4E.tmp.appcompat.txt

C:\Users\VMM_ManageHost\AppData\Local\Temp\WERAEB6.tmp.WERInternalMetadata.xml

C:\Users\VMM_ManageHost\AppData\Local\Temp\WERAEB7.tmp.hdmp

C:\Users\VMM_ManageHost\AppData\Local\Temp\WERC3ED.tmp.mdmp

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SWSvc.exe_feedbadfbd33797dba297eac2d8b171f18ce760_cab_0839c522

Analysis symbol:

Rechecking for solution: 0

Report Id: 19c03a78-802b-11e2-93f0-0017a47700ba

Report Status: 8

Hashed bucket: dc12ad703f4bdafc3706e4f63e432eb5

[NDELAMOTTEGSP]

when I restart the service :

[martin_fisher]

By the looks of things you probably need to re-install SnapDrive. Have you tried this at all ?

[NDELAMOTTEGSP]

Finally, We found the problem.

I linked my server in a freenas environnement and it was this iscsi connexion that failed my snapdrive environnment.

I removed the freenas connexion and the snapdrive service works well now.

Thank you for your help.

ps :  I hope that Netapp will able to fix this behviour in another version...

[aferia]

Guys  today I have the same issue  and I found a KB  explaining the solution  and  the root cause, I apply the solution and it work for me

hope it help

Symptoms

Computer Management shows SnapDrive disk snap-in, but does not show iSCSI management

Cause

There is not enough paging space.

Internal Note

BUG 137799

Solution

SnapDrive snap-in is the software module that integrates with the Microsoft Management Console (MMC) to provide a graphical interface for managing virtual disks on the filer. If the iSCSI management is not seen, try increasing the paging space by following these steps:

1. Open Windows Explorer
2. Right-click on My Computer
3. Select Properties > Advanced > Performance Settings > Advanced > Virtual Memory > Change
4. After increasing the maximum paging file size, click OK.

If the problem persists, try the re-installation procedure of the iSCSI initiator found in 2011913: The SnapDrive service fails to start with Error 6: This handle is invalid. Also refer to the Release Note.

This may also happen if the SnapDrive service loads before the Microsoft iSCSI Initiator service loads. To fix that problem, set the SnapDrive service to be dependant on the iSCSI service.