Loading...
Loading...
After a consecutive upgrade of Veeam Backup & Replication and Enterprise Manager to a newer version, VeeamCatalogSvc fails to start if the EM database is located on a remote server.
The account that is used to start VeeamCatalogSVC might not have access to the Veeam Enterprise Manager Database (default name is “VeeamBackupReporting”) located on the remote SQL server. The following error message can be seen in the Svc.VeeamCatalog.log: [DD.MM.YYYY HH:MM:SS] < <04> Info Connecting to the enterprise DB. [DD.MM.YYYY HH:MM:SS] < <04> Error Login failed for user 'DOMAIN\Account'. (System.Data.SqlClient.SqlException) [DD.MM.YYYY HH:MM:SS] < <04> Info Connection state: [Closed].
Change Logon account used for VeeamCatalogSVC under Windows Services > Properties of the service> Log On. Typically, this should be the same account that is used by VeeamEnterpriseManagerSvc (Veeam Backup Enterprise Manager).
During the upgrade process (for example, from version 9.5 to version 10) VeeamCatalogSVC can be upgraded twice if both Veeam Enterprise Manager and Veeam Backup and Replication are installed on the same server. That is because the VeeamCatalogSVC installation package is handled by both Veeam Enterprise Manager and Veeam Backup and Replication installation wizards. Please keep this in mind when you reach the step Specify Service Account Settings of the installation wizard. https://helpcenter.veeam.com/docs/backup/vsphere/install_vbr_account.html?ver=100
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.