Search Engine: Elastic

Article ID: 131467, created on Sep 16, 2017, last review on Sep 16, 2017

  • Applies to:
  • Operations Automation 7.1


When customer tries to add MS SQL database node, Unable to connect to the database server error appears. However, if one runs the same command, but explicitly specifying the default MS SQL port (1433), no connection errors appear.

In /var/log/shm-dispatcher/dispatcher.log on Plesk node the following errors could be seen:

 whp_requests.INFO: Execution context [POST (ID: 9f66cdfd63e8b8799cb56fa50fd5f62187219106)]

HTTP/1.1 500 Internal Server Error
"errorMessage": "mssqlmng failed: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.\r\n   at (VADOConnection::open line 48)\r\n   at Unable to ADO conect with connection string: Provider=SQLOLEDB.1;Initial Catalog=master;Data 
"error": "PmShm.Sdk.Exception_DbServerConnectionFailed",


Due to software-related issue WHM-10260, OA passes incorrect commandline to Plesk.


Issue could be workarounded in the following way:

  1. After system shows error 'Unable to connect to the database server. Continue anyway?' press OK.
  2. Go to PCP
  3. Services > WebHosting Plesk
  4. Switch to tab Service Nodes
  5. Click "Tools and Settings" of Windows Service Node
  6. Database Servers -> Add Database Server
  7. Add database with the following parameters:

    Database server type: MS SQL
    Host name or IP address: <IP address of node with MS SQL Server>
    Administrator's username: <user name (usualy "sa")
    Administrator's password: <password>
    Confirm password: <password>

After this steps it is possible to provision Websites with on Windows Plans with shared MS SQL Servers and manage databases on these sites as usual.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 8c199f0ee4305da1a577740620df4a51 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF