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.
I have the same problem :
Windows server 2012 datacenter with Hyper-V
And after seeing some fetaures on the snapdrive, the snapin hangs and failed. After the reboot, i loss the iscsi management.
Is there something between windows server 2012 and snapdrive that I missed?
Thank you for your help
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.
but app chrashes :
Fault bucket 97375060, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
These files may be available here:
Rechecking for solution: 0
Report Id: 19c03a78-802b-11e2-93f0-0017a47700ba
Report Status: 8
Hashed bucket: dc12ad703f4bdafc3706e4f63e432eb5
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...
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
Computer Management shows SnapDrive disk snap-in, but does not show iSCSI management
There is not enough paging space.
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:
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.