1-800-691-1991 | 9am - 8pm ET
EN

Component state mismatch has been detected.

KB ID: 2030
Product: Veeam Backup & Replication
Version: 8.x
Published: 2015-04-28
Last Modified: 2020-08-13

Challenge

When attempting install or upgrade Veeam Backup & Replication you receive the warning:

“<uuid> component state mismatch has been detected. Please contact Veeam technical support team directly.”

User-added image

Cause

This is due to the fact that the server you are install/upgrading Veeam Backup & Replication on was added as a managed server to another instance of Veeam Backup & Replication that has already been upgraded.

Solution

Complete the install as usual and apply the same update to all Veeam servers that are interconnected.
 
KB ID: 2030
Product: Veeam Backup & Replication
Version: 8.x
Published: 2015-04-28
Last Modified: 2020-08-13

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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please try again later.