Post reply

DBNETLIB] [ConnectionOpen (SECDoClientHandshake()).] SSL Security Error

  • March 6, 2023 at 3:10 pm

    #4157320

    Hi

    New server with SQL version 2019 has been created to host a DB for a Legacy App to use.  This is working fine. The App has not changed. I need to get this working on a test Server.

    Test Server with 3 instances on it

    1. Version 2014, Development edition uses port 1433

    2. .\SQLEXpress2017

    3. .\SQLExpress2019

    The App connects to version 2014 on this Test server ok.

    Change Test environment to host 2019 version DB.

    There is a firewall rule which only allows access via 1433 and 1434 UDP.

    So I Switched off the default 2014 version and changed the port of .\SQLExpress2019 to 1433.

    With Management Studio remotely I need to put the port number in the connection string e.g. .\SQLExpress2019,1433. Why is the port needed with SQL Browser working?

    I run the App remotely using SQLOLEDB I get "DBNETLIB] [ConnectionOpen (SECDoClientHandshake()).] SSL Security Error" connecting to .\SQLExpress2019,1433.

    The same App will connect to the Live server running 2019.

    I've read this is to do with TLS version support. But on the same server allows the app to connect 2014 instance

     

    Error log on 2019 instance has these errors.

    The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/TESTSERVER:1433 ] for the SQL Server service. Windows return code: 0x200b, state: 15.

    The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/TESTSERVER:SQLEXPRESS2019 ] for the SQL Server service. Windows return code: 0x200b, state: 15.

    I try using an SQL Authenticated user and still get the same SSL Security Error

     

     

  • March 7, 2023 at 4:10 pm

    #4157821

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • May 16, 2024 at 2:36 pm

    #4421739

    Change OLEDB driver to MSOLEDBSQL

  • May 16, 2024 at 5:26 pm

    #4421767

    terry999 wrote:

    There is a firewall rule which only allows access via 1433 and 1434 UDP.

    [\quote]

    can this not be modified\updated to allow the named instance port

     

    terry999 wrote:

    So I Switched off the default 2014 version[\quote]

    you stopped and disabled the services for this instance?

     

    terry999 wrote:

    and changed the port of .\SQLExpress2019 to 1433.

    [\quote]

    where and how did you set the port number

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply