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

Cannot open database requested by login. The login failed

KB ID: 1635
Product: Veeam ONE 11, Veeam ONE 10, Veeam ONE 9.5, Veeam ONE 9.0, Veeam ONE 8.0, Veeam ONE 7.0, Veeam ONE 6.5, Veeam ONE 6.0
Published: 2012-10-01
Last Modified: 2021-03-29

Challenge

When you try to access Veeam ONE Web UI, the following error occurs:

Cannot open database requested by login. The login failed.
User-added image

Cause

Veeam ONE Web UI configuration is missing information on the account used for SQL authentication.

Solution

To modify configuration settings, follow the next steps:
  1. Launch the Veeam ONE Settings utility available in the following location:

    C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe

  2. Open the Web Identity tab, re-enter credentials and click Save.

    User-added image

 

More information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support
KB ID: 1635
Product: Veeam ONE 11, Veeam ONE 10, Veeam ONE 9.5, Veeam ONE 9.0, Veeam ONE 8.0, Veeam ONE 7.0, Veeam ONE 6.5, Veeam ONE 6.0
Published: 2012-10-01
Last Modified: 2021-03-29

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.

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 go back try again later.