Error during operations with database: "Get database server version failed"


2016-11-16 12:45:49 UTC


2017-08-16 16:47:51 UTC


Was this article helpful?

Have more questions?

Submit a request

Error during operations with database: "Get database server version failed"

Applicable to:

  • Plesk 10.x for Windows
  • Plesk 11.x for Windows
  • Plesk 12.0 for Windows
  • Plesk 12.5 for Windows


During an operation with MS SQL database\user, or with a subscription\customer that holds a MS SQL database, an error occurs:

Get database server version failed: Login failed for user "sa"


Get database server version failed: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. (Error code )


  1. The MS SQL Server is only configured for Windows authentication. The 'sa' login can only connect to the server using SQL Server Authentication.

  2. The admin password for an MS SQL server instance stored in the Plesk database does not match the actual administrative account passwod.

  3. An incorrect hostname/instance name is used for MS SQL server.


  1. To enable "SQL Server and Windows Authentication mode", refer to this Microsoft article .

  2. Make sure that the passwords are the same. To do this, set up the same password both in Plesk and in the database server instance:

  3. Set the password for the corresponding MS SQL server instance in Plesk using "settings - set password - OK" in the database servers menu.

  4. Set the same password for the corresponding server by logging in under Windows authentication:

    cd C:\\Program Files\\Microsoft SQL Server\\100\\Tools\\Binn

    osql -S .\\MSSQLSERVER2008 -E -Q "EXEC sp_password @new='1qazXSW@', @loginame = 'sa'"


    • The 'OSQL.exe' utility path may differ from the following example, so check all directories under 'C:\\Program Files\\Microsoft SQL Server\\' or 'C:\\Program Files (x86)\\Microsoft SQL Server\\' .

    • All broken MS SQL services (marked with grey circle on the database servers page) should be fixed as above. If only one MS SQL instance is running on the server, '-S' should be ommited. Otherwise, the service name should be provided.

  5. If the issue is not resolved, check the Windows Event logs -> Application where Source is 'MSSQLSERVER' and the Task Category is 'Logon' .

Have more questions? Submit a request
Please sign in to leave a comment.