Skip to main content
NetApp Knowledge Base

SnapDrive for Windows (SDW) console crashes when SVM is added to Transport Protocol Settings

Views:
271
Visibility:
Public
Votes:
3
Category:
snapdrive-for-windows
Specialty:
legacy
Last Updated:

Applies to

  • SnapDrive for Windows

Issue

  • When entering in SVM settings in the Transport Protocol Settings within SnapDrive for Windows the UI crashes.

Snpdrvdbg.log:

09/04-02:04:37.258 PID:4284 TID:9304 localerror.cpp@82 Is_VDS_ITF_Error(): false.
09/04-02:04:37.258 PID:4284 TID:9304 localerror.cpp@94 Is_WMI_ITF_Error(): false.
09/04-02:04:37.258 PID:4284 TID:9304 FilerHelper.cpp@40 Transport Protocol is not set to connect the storage system . HRESULT 0xc0040457.
09/04-02:04:37.258 PID:4284 TID:9304 localerror.cpp@82 Is_VDS_ITF_Error(): false.
09/04-02:04:37.258 PID:4284 TID:9304 localerror.cpp@94 Is_WMI_ITF_Error(): false.
09/04-02:04:37.258 PID:4284 TID:9304 FilerHelper.cpp@63 CFilerHelper::Static_system_get_version: caught com err, filer = '<IP ADDRESS of SVM>', bipaddress = 1 09/04-02:04:37.258 PID:4284 TID:9304 FilerHelper.cpp@68 CFilerHelper::Static_system_get_version: get_filer_live_ip() caught exception...
09/04-02:04:37.258 PID:4284 TID:9304 filer_set.cpp@152 verify_ip_address: IP address: '<IP ADDRESS of SVM MGM LIF'  is invalid

 

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.