Warning on the "Database Servers" page in Plesk: Unable to determine the TCP port number used by Microsoft SQL server

Follow

Comments

9 comments

  • Avatar
    Cutytongy

    I configured the TCP/IP on the SQL Server, configured same on Plesk Onyx, but still giving errors. find attached screenshot



    0
    Comment actions Permalink
  • Avatar
    Robert Asilbekov

    Make sure that MS SQL server was restarted and you there is no spaces in the "Hostname or IP address" field.

    0
    Comment actions Permalink
  • Avatar
    Nabil Al-Kilany

    but the option to change he host name or ip in plesk onyx is greyed out!

    0
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    @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-

    0
    Comment actions Permalink
  • Avatar
    Nabil Al-Kilany

    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.

    0
    Comment actions Permalink
  • Avatar
    Daria Gavrilova

    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?

    0
    Comment actions Permalink
  • Avatar
    Acharyamanjil (Edited )

    It doesn't work in my case, are there any other solution for this problem.

    1
    Comment actions Permalink
  • Avatar
    Rupert Tildesley

    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?

    0
    Comment actions Permalink
  • Avatar
    Konstantinos Katoudis

    I followed the steps, but the warning message still exists

    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.

    Also I add firewall TCP rules to allow connections to MSSQL port 1433.

     Any thoughts?

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request