Skip to main content
NetApp Knowledge Base

vCenter compliance check fails

  1. Last updated
    Jun 5, 2025
  2. Save as PDF
Views:
10
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:
6/5/2025, 9:55:31 AM

Applies to

BlueXP Disaster Recovery

Issue

  • vCenter compliance check fails with the error:

Agent sub-workflow response failed, error <source_IP> --> <destination_IP> Credential API invocation did not return a valid response. Error: '404 The requested resource could not be found but may be available again in the future.'. .
Compliance failed for source vcenter. Please check source vcenter '<source_IP>' is up and running. Compliance failed for target vcenter. Please check target vcenter '<destination_IP>' is up and running.

  • A discovery of the vCenters comes is successful.
  • The IP addresses of the source and destination vCenters are reachable and the necessary ports are open.

 

 

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.