Azure DevOps Server could not connect to the database

Abdul Aziz Farooqi 0 Reputation points
2023-05-10T05:39:17.1233333+00:00
{"$id":"1","innerException":null,"message":"TF246017: Azure DevOps Server could not connect to the database. Verify that the instance is specified correctly, that the server that is hosting the database is operational, and that network problems are not blocking communication with the server.","typeName":"Microsoft.TeamFoundation.Framework.Server.DatabaseConnectionException, Microsoft.TeamFoundation.Framework.Server","typeKey":"DatabaseConnectionException","errorCode":0,"eventId":3008}
Azure DevTest Labs
Azure DevTest Labs
An Azure service that is used for provisioning development and test environments.
255 questions
Not Monitored
Not Monitored
Tag not monitored by Microsoft.
35,997 questions
{count} votes

2 answers

Sort by: Most helpful
  1. ShaktiSingh-MSFT 13,271 Reputation points Microsoft Employee
    2023-05-10T06:34:45.11+00:00

    Hi Abdul Aziz Farooqi •,

    Welcome to Microsoft Q&A forum for Azure.

    As I understand, you are facing issue in connection of Azure DevOps to Azure SQL Database.

    Please let me know if my understanding is correct.

    The error could be due to the following reasons if related to Database:

    1). Please check if the connection string used is correct.

    2). Check you have required permissions.

    3). Make sure the Database is online and Login credentials is correct.

    4). Check if the network settings(firewall) configuration is allowing connection establishment.

    If above pointers looks fine, and still connection has issue, I would recommend you to raise request in Azure DevOps forum as in Q&A we do not address Azure DevOps questions currently.

    Hope this information helps. Let me know the result.

    Thank you.

    0 comments No comments

  2. Rohit Vishwakarma 0 Reputation points
    2023-09-26T08:00:28.9033333+00:00

    Capture

    Hi Team,

    Please check SQL server configuration manager alias, I have shown the example on the image please remove that aliases and restart SQL Services and azure Services, I am sure it will work,

    0 comments No comments