https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxOTM2IiwiaGFzaCI6ImM0NjMyMGFiLWY4ODUtNGYyZS05N2RkLTdhNTZiOTk3YmZiNiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Veeam Explorer for Exchange (VEX) Restore Failure - HTTP Error 501 – Load Balancer

Challenge

The following KB is only relevant if a Load Balancer is being used.
 
When attempting to use the “Restore to <email>” function the restore fails with “HTTP Error 501”.
 
The following will be found in the logs:

 
Item restore failed: The request failed with HTTP status 501: Invalid Request.
Error: ExplorerManagementService: Failed to handle OnFinishItemRestore event (sessionId = ‘Unique_Identifier’)
Restored item with the specified identifier does not exist
Error: Restored item with the specified identifier does not exist

Cause

This happens because when VEX detects the CAS server it sees the load balancer instead of the actual CAS.

Solution

Instead of restoring to the original location, select “Restore to” and then manually change the CAS server to the FQDN of the Exchange CAS server.
 
Alternatively, you can point the load balancer hostname/FQDN to the IP of the exchange with a hosts entry. 


 
KB ID:
1936
Product:
Veeam Backup & Replication
Version:
7.x, 8.x, 9.x
Published:
2014-10-14
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later