Control Compliance Suite

 View Only
Expand all | Collapse all

A connection was successfully established,but then an error occured during the pre-login handshake, (provider: SSL Provider,error: 0-The certificate chain was issued by an authority that is not trusted.)

  • 1.  A connection was successfully established,but then an error occured during the pre-login handshake, (provider: SSL Provider,error: 0-The certificate chain was issued by an authority that is not trusted.)

    Posted Feb 26, 2014 12:24 AM
      |   view attached

    Hi,

    While installing Control compliance suite 11.0 in windows server 2003 for first time.i am facing below error while specifying Sql server IP address and instance details.

    Error:

    A connection was successfully established,but then an error occured during the pre-login handshake, (provider: SSL Provider,error: 0-The certificate chain was issued by an authority that is not trusted.)

     

    Please find the attached screen shot for your reference.Please suggest to install the CCS 11.0 in windows server 2003 Entreprise edition sp2 64 bit server.

    With Regards,

    Mahesh

     



  • 2.  RE: A connection was successfully established,but then an error occured during the pre-login handshake, (provider: SSL Provider,error: 0-The certificate chain was issued by an authority that is not trusted.)

    Posted Mar 18, 2014 02:43 PM

    When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

    Solution
    Case 1

    If the issue occurs when trying to connect to a Remote SQL Server 2005, try the following steps:

    1. Go to Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager.
    2. Under SQL Server 2005 Network Configuration, make sure that TCP/IP or Named Pipes are listed as 'Enabled' (in order to enable them, right-click and choose Enable). If you had to enable them, you will need to restart the SQL Server service in order to take effect.
    3. Under SQL Native Client Configuration, make sure that TCP/IP or Named Pipes are listed as "Enabled" as well.
    4. Try to open the Notification Server Console (if you had Notification Server already running previously). Otherwise, run NSSetup one more time.

    Case 2

    If the issue occurs when trying to connect a local SQL Server 2005 using localhost as server name, please try the following (from the Notification Server 6.0 SP3 Release Notes):

    6.1.9 Install Wizard failing to automatically detect locally installed SQL Server 2005

    The Notification Server Install Wizard will fail to detect a locally installed SQL Server 2005 when "localhost" is entered as the SQL Server name and the following error is returned: Failed to get the list of available databases, check your database credentials.