Rescan of Cloud Native Machines in Azure Fails After Credentials Change
| KB ID: | 4530 |
| Product: | Veeam Backup & Replication | 12.1 |
| Published: | 2023-12-15 |
| Last Modified: | 2023-12-15 |
Get weekly article updates
Oops! Something went wrong.
Please, try again later.
Challenge
After the Azure Storage account is changed, rescan of Cloud Native Agents (e.g., Veeam Agent for Microsoft Windows, Veeam Agent for Linux) fails with the error:
Warning Failed to connect to <machine_name> Details: Azure REST API error. HTTP code: [403]. Azure error: [AuthenticationFailed]. Full error: [Code: [AuthenticationFailed], message: [Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
Cause
Invalid credentials are cached in the Cloud Messaging Service on the machines.
Solution
- Ensure no jobs or restores are active.
- Restart the Veeam Backup Service on the Veeam Backup Server.
Stopping the Veeam Backup Service may take some time while it attempts to stop all running tasks. - Rescan the machines again.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
