Data Backup and Recovery

SnapDrive Web Service failed to start Reason: 'The type initializer for 'System.ServiceModel.DiagnosticUtility' threw an exception.'



One of my clients came across something unusual and I cannot find any info on the error they're receiving.

Namely, they had SnapDrive 6.3 running on Windows 2008 R2, 64-bit, hosting SQL database and Web server and suddenly they cannot open the snap-in for SnapDrive anymore because SnapDrive service fails to start and cannot be restarted for some reason...

Virtual Disk service is running, RPC service is running, all other dependencies are ruled out, passwords are OK, time difference is < 5min, and yet whenever they try to access the SnapDrive console they get the following error:

      SnapDrive service failed to start.  Error code : SnapDrive Web Service failed to start Reason: 'The type initializer for 'System.ServiceModel.DiagnosticUtility' threw an exception.'

Server's system events report:

     The SnapDrive service terminated with the following error: %%-1073478613

And the can also see this:

     Faulting application name: SWSvc.exe, version:, time stamp: 0x4c85f54d

     Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b

     Exception code: 0xc0000005

     Fault offset: 0x000000000004d174

     Faulting process id: 0x1618

     Faulting application start time: 0x01cd423a6fac450f

     Faulting application path: C:\Program Files\NetApp\SnapDrive\SWSvc.exe

     Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

     Report Id: af40ca08-ae2d-11e1-ad2a-78e7d1e98aa8

They tried re-installing SnapDrive but they cannot get passed the "starting snap-in" part, so they cannot configure the target system and everything else. It just hangs like that for a couple of minutes (no SnapDrive service) and then the error is issued.

Any thoughts on what the cause may be?





Run the tool "Data Collection Tool for SnapDrive for Windows (ONTAPWinDC.exe)", you can download from toolchest and will able to check the errors and reasons sometimes.

You also need to check the options like options cifs.signing.enabled on and other options too.

thank you,