Operational Defect Database

BugZero found this defect 123 days ago.

Veeam | kb4530

Rescan of Cloud Native Machines in Azure Fails After Credentials Change

Last update date:

12/15/2023

Affected products:

Veeam Backup & Replication

Affected releases:

12.1

Fixed releases:

No fixed releases provided.

Description:

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.

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Solved

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...