• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question MSSQL TCP Problem

Paulo Leite

New Pleskian
Hi all,

I have problem it gives me the following error in MSSQL database server:

"Warning: Unable to determine the TCP port number used by Microsoft SQL server '.\MSSQLSERVER2017': 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."

The firewall rule "MS SQL over TCP protocol" is "Allow connections from Port 1433, profiles: domain, private, public"

I already read KB Article Microsoft SQL Server is shown as disconnected in Plesk: Unable to determine the TCP port number used by Microsoft SQL server, however don't worked. When I change the TCP Port to 1433 and restart SQL service via Plesk, the configuration return to Dynamic Port.

So, I understand that the MSSQL is only allowing dynamic port, but how to change this?


Thanks in advance
 
Back
Top