When using the Protect Multiple Machines Wizard to protect machines agentlessly on an ESXi host, after completing the Connection section and clicking Next, the wizard fails with:
In this case the original vCenter build was 6.0.0 Build 3617395. As soon as vCenter was updated to the most recent build of vCenter the issue was resolved. Due to this being the only reported case with this error we were not able to determine the exact root cause before vCenter was updated.
Current possible root causes include a damaged database on vCenter which may have cause the v1 parameter value to not be passed to the core. The v1 parameter may be the vCenter build, username, or password. Additional diagnostics could not be applied to determine the actual root cause and parameter value.
Please Note: If time permits, please open a SR so we can gather additional information to determine exact root cause having to do with vCenter or Rapid Recovery.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책 Cookie Preference Center