Applicable to:
- Plesk for Windows
Symptoms
- Microsoft SQL server is shown as disconnected in Tools & Settings > Database Servers (there is no green checkmark next to the server name)
-
PLESK_WARN: Warning: Unable to determine the TCP port number used by Microsoft SQL server '.\\MSSQLSERVER2014': 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. -
Error in Event Viewer > Plesk:
CONFIG_TEXT: SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. Login timeout expired
at (VADOConnection::open line 48) -
Cannot change the password for
sauser in Tools & Settings > Database Servers:PLESK_ERROR: Error: The test connection to the database server has failed because of network problems:
Try to establish connection failed
Cause
MS SQL Server is not configured to use static ports.
Resolution
Note: if Microsoft SQL server is shown as connected, the warning can be ignored. However, it is still better to define exact port, to avoid connection issues in future.
Connect to the server using RDP and follow video tutorial:
Text instructions
-
Go to Start > SQL Server XXXX Configuration Manager (where XXXX is a version of MS SQL Server).
-
Follow the steps from the Microsoft documentation article Configure a Server to Listen on a Specific TCP Port to configure MS SQL Server instance to use static ports:
- remove the values (including zeroes) from the TCP Dynamic Ports of IPv4 address and "IPv4"
- remove the value (including zeroe) from the TCP Dynamic Ports of IPAll section
- set specific port for the TCP Dynamic Ports of IPAll section:
- Open SQL Server Services > SQL server and restart the service
-
Go to Tools & Settings > Database Servers > MS_SQL_Server_name > Settings and click OK to re-apply them.
Note: in case the warning persists, additionally specify database server port 1433 in Tools & Settings > Database Servers > MS_SQL_Server_name > Settings > Host name or IP address field and press the OK button
- Before
CONFIG_TEXT: 203.0.13.2
-
After
CONFIG_TEXT: 203.0.13.2 ,1443
- Before
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.