Skip to main content
NetApp Knowledge Base

'Transport Protocol is not set to connect the storage system %1' when SME verification runs in Metrocluster switchover mode

Views:
447
Visibility:
Public
Votes:
1
Category:
snapmanager-for-microsoft-exchange-server
Specialty:
legacy
Last Updated:

Applies to

  • SnapManager for Exchange
  • SnapDrive
  • OnTAP Metrocluster

Issue


When there is a Metrocluster Switchover, SnapDrive looks for the credentials for the surviving SVM, typycally if svm is called svm1, the surviving svm will be svm-mc.
Since credentials are set by user for svm1 and not for svm1-mc, snapdrive logs an error and reports it back to SnapManager.
Somehow this only happens during SME (SnapManager for Exchange) verification process: we have observed the issue so far only when performing remote backup and verification, not local, but you can't exclude that we may see the issue in other circusmtances.

SME will log a similar error in the backup report:
[Server1] Error Code: 0xc0040457
Transport Protocol is not set to connect the storage system %1.


SnapDrive will log an error similar to the one below,  around the time SME logs its error:
11/04-20:04:19.472    PID:2120    TID:1404    FilerHelper.cpp@124        Transport Protocol is not set to connect the storage system SVM1-mc.
 HRESULT 0xc0040457.

 

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.