Skip to main content
NetApp Knowledge Base

SnapCenter or SCV returns API Invoke failed when adding SVM with HTTPS Protocol

  1. Last updated
  2. Save as PDF
Views:
69
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • SnapCenter [SC]
  • SnapCenter Plug-in for VMware [SCV]
  • Storage Virtual Machine [SVM]
  • Secure Sockets Layer [SSL]

Issue

  • Can't add the storage host using port 443/HTTPS, but 80/HTTP may work.
  • After removing SVM from the Storage Systems menu, adding them back fails with API Invoke Failed
  • Node hosting the LIF for the SVM doesn't allow https://node_mgmt_IP/SPI and a ERR_CONNECTION_CLOSED is logged in the browser.
  • Discovery or Backup  job fails with: 

2025-04-09T15:12:18.4391491-04:00 Verbose SAL PID=[4744] TID=[6992] ZAPI flag enable ..
2025-04-09T15:12:18.4391491-04:00 Verbose SAL PID=[4744] TID=[6992] UserName: vsadmin
2025-04-09T15:12:18.4391491-04:00 Verbose SAL PID=[4744] TID=[6992] Invoking Connect-NcController ...
2025-04-09T15:12:18.4547833-04:00 Critical SAL PID=[4744] TID=[6992] The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: API invoke failed. at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
at SnapDrive.Nsf.Core.Storage.StorageConnection.InitializeONTAP(SDStorageSystemId storageSystemId)

2025-04-09T15:12:18.4547833-04:00 Verbose SAL PID=[4744] TID=[6992] ex.Message : The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: API invoke failed.

 

 

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.