vCenter Server's Management Interface (VAMI) shows "Server error at target URL" when attempting to stage an upgrade.

Products

• VMware vCenter Server

Issue/Introduction

• When viewing the VAMI web UI at <IP>:5480, new vCenter update packages may not be downloadable.
  
  
• When attempting to stage an upgrade, it fails and an error message states that there is a server error at the target URL
  
  
  
• A site administrator for the account has already generated a download token and the VAMI's Update tab > Settings has been configured with a Specified URL at the broadcom.com site similar to:
  https://dl.broadcom.com/<downloadToken>/PROD/COMP/VCENTER/vmw/8d167796-34d5-4899-be0a-6daade4005a3/<current_version>/
  • If not, refer to article: vCenter update fails with "The vCenter Server is not able to reach the specified URL. Ensure that the vCenter Server is connected to the internet, the specified URL is correct, and the latest version(s) is available on the VMware online repository." 
• When the URL is entered directly into a web browser, an otherwise blank screen with the words "Invalid file path provided" is seen.

• Users may also experience issues with the Lifecycle Manager within the vSphere UI such as described at Host remediation fails with error: "Cannot download VIB: This might be because of network issues or the specified VIB does NOT exist or does NOT have a proper 'read' privilege set."  or "A general system error occurred: Cannot download VIB" error while staging the ESXi patch using lifecycle manager with Token based URL - Token Not Entitled 

Cause

The Site ID from which the download token was generated either does not have the proper license associated with it or there is a permissions issue resulting in the download site rejecting the request. 

Resolution

1. Refer to the VCF Authenticated Downloads Token Troubleshooting Guide which has instructions for how to validate vSphere download URLs and states:
   "Note: It is important to test all 4 URL's when troubleshooting. In rare cases, a siteID may only have a license for either vCenter or ESXi. Testing all four can help isolate which license version or product may be missing in the siteID."
   
   
2. Follow the steps in that article to validate the Token, site ID, license(s), and URL are correct or to fix them through the customer portal.
   
   
3. If there is an issue with entitlements or updates need to be made on the account, follow the steps at How to open / create Non Technical case for Support Portal / License / Contract related issues