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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyNjk5IiwiaGFzaCI6ImQ3NzdkMTU2LWUzZGQtNDhlNC05NTA0LTUzZmM2N2E5YjAzOCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Setup Wizard ended prematurely because of an error

Challenge

When upgrading to Veeam Backup for Microsoft Office 365 v2 from an earlier version the following error is received:

setup error
Additionally, the latest Veeam.Archiver.Service log file found under C:\ProgramData\Veeam\Backup365\Logs contains the following:
25.7.2018 10:14:12    6 (5940)   Upgrading backup jobs...
25.7.2018 10:14:12    4 (4588) Error: Job with the specified name already exists.
25.7.2018 10:14:12    4 (4588) Type: System.Exception
25.7.2018 10:14:12    4 (4588) Stack:
25.7.2018 10:14:12    4 (4588)    at Veeam.Archiver.Controller.JobConfigVerifier.VerifyCreatedJob(JobConfig config, BackupScopeConfig

Cause

Under rare circumstances records on backup jobs might be duplicated in a configuration database. This does not affect an already existing installation, yet fails a duplicates check during the upgrade.
 

Solution

Please contact Veeam Technical support for the fix.
KB ID:
2699
Product:
Veeam Backup for Microsoft Office 365
Version:
2.0.0.567
Published:
2018-08-01
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