Skip to main content
NetApp Knowledge Base

SCW fails to create/connect disk by "No storage connection is set for StorageSystem"

Views:
747
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter Plug-in for Microsoft Windows (SCW)

Issue

  • SCW fails to create or connect disk by the following error even though SVM is added to Storage Systems.

Example:

Failed - Failed to connect disk Error: No storage connection is set for StorageSystem : <SVN>

2bcccbaa-ca3d-481a-913f-065b97c5f010.png

  • SCWDebug.log shows that access to the SCW host is denied or timeout.

Example:

Verbose SDW PID=[<PID>] TID=[<TID>] ++SDProvisioningServiceProvider::SDProvisionConnectStorage
Verbose SDW PID=[<PID>] TID=[<TID>] no matching task for SDW SmTaskCode: ConnectStorage
Verbose SDW PID=[<PID>] TID=[<TID>] ++DiskProvisioningManager::SDProvisionConnectStorage
Verbose SDW PID=[<PID>] TID=[<TID>] ++DiskProvisioningHelper::ValidateConnectRequest
Verbose SDW PID=[<PID>] TID=[<TID>] --DiskProvisioningHelper::ValidateConnectRequest
Verbose SDW PID=[<PID>] TID=[<TID>] ++DiskProvisioningManager::SDProvisionCreateStorage
Verbose SDW PID=[<PID>] TID=[<TID>] Validating request 
Verbose SDW PID=[<PID>] TID=[<TID>] ++DiskProvisioningHelper::PreProcessandValidateCreateRequest
Verbose SDW PID=[<PID>] TID=[<TID>] ++StorageSystemManager::GetStorageSystemId
Verbose SDW PID=[<PID>] TID=[<TID>] SVM: <SVM>
Verbose SDW PID=[<PID>] TID=[<TID>] ++StorageSystemManager::GetStorageSystemIdFromCache
Verbose SDW PID=[<PID>] TID=[<TID>] SVM: <SVM>
Verbose SDW PID=[<PID>] TID=[<TID>] The storage is not in the storage systemId cache: Available cached storage are...
Verbose SDW PID=[<PID>] TID=[<TID>] --StorageSystemManager::GetStorageSystemIdFromCache
Verbose SDW PID=[<PID>] TID=[<TID>] <SVM> is missing from storage cache. Starting update from server. Thread ID: 7
Verbose SDW PID=[<PID>] TID=[<TID>] Update storage system '<SVM>' from SnapCenter. updateFromServer flag = False
Verbose SDW PID=[<PID>] TID=[<TID>] ++StorageSystemManager::UpdateStorageSystemIDFromServerCache
Verbose SDW PID=[<PID>] TID=[<TID>] Making a rest call to https://localhost:8145//SMCoreCacheService//GetStorageCache
Verbose SDW PID=[<PID>] TID=[<TID>] Call remote Rest API  https://localhost:8145//SMCoreCacheService//GetStorageCache
Verbose SDW PID=[<PID>] TID=[<TID>] Entering ValidateSmCertificate
Verbose SDW PID=[<PID>] TID=[<TID>] Accepting certificates
Verbose SDW PID=[<PID>] TID=[<TID>] Finished ValidateSmCertificate
Error SDW PID=[<PID>] TID=[<TID>] Cannot retrieve storage connection setting from SMS server.
Error SDW PID=[<PID>] TID=[<TID>] Response error: Access denied for server: <SCW host> or timeout expired.
Verbose SDW PID=[<PID>] TID=[<TID>] --StorageSystemManager::UpdateStorageSystemIDFromServerCache
Verbose SDW PID=[<PID>] TID=[<TID>] --StorageSystemManager::GetStorageSystemId
Error SDW PID=[<PID>] TID=[<TID>] Error: No storage connection is set for StorageSystem : <SVM>
Verbose SDW PID=[<PID>] TID=[<TID>] --DiskProvisioningHelper::PreProcessandValidateCreateRequest
Error SDW PID=[<PID>] TID=[<TID>] Failed to provision disk
Error SDW PID=[<PID>] TID=[<TID>] Error: No storage connection is set for StorageSystem : <SVM>   at SnapDrive.Nsf.Core.DiskProvisioningHelper.PreProcessandValidateCreateRequest(SDProvisionCreateStorageRequest request, DiskOperationContext context, HostDetails& host)
   at SnapDrive.Nsf.Core.DiskProvisioningManager.SDProvisionCreateStorage(SDProvisionCreateStorageRequest request, DiskOperationContext context, Boolean provisioning)

Verbose SDW PID=[<PID>] TID=[<TID>] --DiskProvisioningManager::SDProvisionCreateStorage
Verbose SDW PID=[<PID>] TID=[<TID>] --DiskProvisioningManager::SDProvisionConnectStorage
Verbose SDW PID=[<PID>] TID=[<TID>] no matching task for SDW SmTaskCode: ConnectStorage
Verbose SDW PID=[<PID>] TID=[<TID>] --SDProvisioningServiceProvider::SDProvisionConnectStorage

 

  • SMCoreService.log shows that name resolution fails for own host by using FQDN.

Example:

ERROR SMCore PID=[<PID>] TID=[<TID>] Exception in method: InvokeXML.
System.Net.WebException: The remote name could not be resolved: '<SCW FQDN>'
   at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
   at System.Net.WebClient.UploadString(Uri address, String method, String data)

 

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.