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

Unable to Connect to Veeam ONE DB During Update Installation

Challenge

During upgrade to 9.5 or update installation, Veeam ONE installer is unable to locate the database

Cause

SQL Server Native Client (11.0) is not installed or there is an issue with the permissions assigned to the Veeam ONE service account

Solution

1. Install an updated SQL Server Native Client (11.0) on the Veeam ONE server machine.

2. Ensure the following permissions for the Veeam ONE database are assigned to the Veeam ONE service account:

Public role (default permissions)
  • CREATE ANY DATABASE permissions
  • db_owner role on the Veeam ONE database
  • db_datareader permissions on the master database
  • publicdb_datareaderSQLAgentUserRole permissions on the msdb database
  • [For Always-On Availability Groups] VIEW SERVER STATE permissions
The Named Pipes protocol must be enabled on the Microsoft SQL Server.
 

More information

If the issue persists, contact Veeam Support for further Technical assistance.
KB ID:
2265
Product:
Veeam ONE
Version:
9.5
Published:
2017-04-10
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