Skip to main content
NetApp Knowledge Base

Can't access recently created CIFS shares because SnapMirror relationship is quiesced

Views:
2,516
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SnapMirror
  • CIFS/SMB

Issue

Unable to access any recently created CIFS shares, but able to access older CIFS shares.

EMS error: [cluster-01: kernel: Nblade_cifsShrConnectFailed_1:error]: params: {'errorDescription': 'No such object', 'vserverName': 'netapp-cifs-1', 'serverIp': '10.168.223.233', 'vserverId': '9', 'errorCode': '2', 'shareName': 'NetApp_Share', 'clientIp': '192.168.223.233'}

SnapMirror.gz error: 
[kern_snapmirror:info:1761] 0x8321b6200:Daemon:117425 action=End status=Failure message=Transfer did not start because the relationship is quiesced. source=netapp://netapp-cifs-1/netappcifs1_root destination=netapp://netapp-cifs-1/lsmir_netappc...pcifs1_root_10
 
Windows error:
Network Error: Windows cannot access \\netapp-cifs-1\netapp_share
Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.
Details: Error code: 0x80070043 The network name cannot be found.
 
Packet Trace:
clipboard_e50274b92e259db7ada7ed989ae572f85.png

 

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.