Applicable to:
- Plesk for Windows
Symptoms
-
The following warning message is shown in Plesk at Tools & Settings > Database Servers:
PLESK_WARN: Warning: Unable to determine the TCP port number used by Microsoft SQL server '.\MSSQLSERVER2019': TCP/IP protocol is not enabled in the server network configuration or the server is configured to use dynamic TCP ports.
To allow your customers to automatically configure firewall for remote database access, manually configure the SQL server to listen on a specific fixed TCP port. -
It is not possible to connect to a Microsoft SQL Server remotely using Microsoft SQL Server Management Studio with the error:
PLESK_INFO: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (Microsoft SQL Server, Error: -1)
Cause
Microsoft SQL Server is not configured to use a static port.
Resolution
-
Connect to the Plesk server via RDP.
-
Go to Start > All Programs > Microsoft SQL Server XXXX > SQL Server XXXX Configuration Manager.
Note: XXXX is a version of MS SQL Server from the error message.
-
Expand SQL Server Network Configuration and click Protocols for MSSQLSERVERXXXX.
-
Double-click on TCP/IP:
4.1. On the Protocol tab, make sure that the TCP/IP protocol is Enabled.
4.2. Switch to the IP Addresses tab and scroll down to the IPAll section.
4.3. Specify default MS SQL port number 1433 (or a custom port number if 1433 is already used by another MS SQL Server instance) in the TCP Port field
Note: The specified MS SQL port must be opened in firewall.
4.4. Click OK.
-
Go to SQL Server Configuration Manager (Local) > SQL Server Services,
-
Right-click on SQL Server (MSSQLSERVERXXXX) and click Restart to apply the changes.
-
Go to Tools & Settings > Database Servers > .\MSSQLSERVERXXXX > Settings and click OK to sync new settings with Plesk.
Video Instructions
Additional Information
If you use Microsoft SQL Server Management Studio to connect to SQL Server with a custom port, use a comma with port for connection address: 203.0.113.2,1433.
Comments
8 comments
I configured the TCP/IP on the SQL Server, configured same on Plesk Onyx, but still giving errors. find attached screenshot
Make sure that MS SQL server was restarted and you there is no spaces in the "Hostname or IP address" field.
but the option to change he host name or ip in plesk onyx is greyed out!
@Nabil, I was unable to find a similar scenario documented on our knowledge base. Please open a support ticket so we can help you with this issue: https://support.plesk.com/hc/en-us/articles/213953025-How-to-get-support-directly-from-Plesk-
Its Ok, I came around it, but the problem still persists due to DNS, as I have the site published on another server and where the DNS is protected by microsoftservices. I wanted to test the site on m plesk server before I change the DNS, however that is preventing little admin from connecting to the DB on the plesk server and pointing somewhere else. I tried to create a subdomain and created a cname dns record to point to the subdomain for testing but still it didn't work. So the only option is to create the site into a completely different domain name test, it then migrate it to the right domain and then change the dns records, unless you have another option to overcome this issue. Thanks.
Hello @Nabil Al-Kilany,
Thank you for your question.
There is no other way to workaround this issue.
If any further issues are encountered, please create the request to Technical Support: How to get support directly from Plesk?
It doesn't work in my case, are there any other solution for this problem.
I followed the steps, but the SQL Server Service would not restart in the final step due to not responding in a timely manner. I tried it several times. Reverting back to the dynamic ports meant I could restart the service so database was back online, but I still have the same problem. Any thoughts?
Please sign in to leave a comment.