Covenant Eyes Interfering with SQL Server / SSL Provider connections

  • 1
  • Problem
  • Updated 11 months ago
  • (Edited)
(Note: I'm a Web  software developer who would also like to not get addicted to porn, but Covenant Eyes is currently not letting me get work done...help)

- CE Version 6.0.16
- Windows 7
- Microsoft SQL Server 2014 (any version)
- PHP and Microsoft PHP drivers for PHP5.6

When Covenant Eyes is installed, it creates entries in the LSP (Layered Service Providers) catalog (see example at the bottom of this post).  But Microsoft says LSP services that do not have the Service Flags value "0x20000" bit set will not properly handle Winsock communication and will cause this issue (see additional links below).  As you can see below, the Service Flags entry indicates that Covenant Eyes is not compatible (flag: "0x66", not "0x20000").  This is causing me to get the following error when trying to write software that accesses a remote SQL Server:

SQLSTATE[08001]: [Microsoft][ODBC Driver 11 for SQL Server]SSL Provider: The message received was unexpected or badly formatted.

Uninstalling Covenant eyes immediately removes the error, so I am sure this is the reason.  Please also see these links for further detail:
https://support.microsoft.com/en-us/kb/2915689
https://support.microsoft.com/en-us/kb/2568167
http://www.sqlservercentral.com/Forums/Topic1529609-2799-1.aspx
http://stackoverflow.com/questions/21681762/how-do-i-fix-an-error-connecting-to-sql-server-ssl-provi...
http://serverfault.com/questions/423013/sql-an-error-occurred-during-the-pre-login-handshake/487139
and similar post here:
https://helpforum.covenanteyes.com/covenanteyes/topics/sql_server_error_with_ce_filter


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Layered Chain Entry (32)
Description: Covenant Eyes over [MSAFD Tcpip [TCP/IPv6]]
Provider ID: {5AFDDD17-9680-4D36-94D3-2DB40C905546}
Provider Path: C:\Windows\system32\CovenantEyesProxy.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 23 Max Address Length: 28 Min Address Length: 28 Socket Type: 1 Protocol: 6 Service Flags: 0x66 Protocol Chain Length: 2 Protocol Chain: 1016 : 1001
Photo of Jon

Jon

  • 1 Post
  • 0 Reply Likes
  • disappointed... I want this to work...I need it to work...

Posted 3 years ago

  • 1
Photo of Annelise

Annelise, Official Rep

  • 255 Posts
  • 13 Reply Likes
Hello Jon,

Thank you for contacting us and apologies for the difficulties you've been experiencing. I've forwarded your issue on to one of developers and will contact as soon as I hear back from them! Thank you for your patience.

Best regards,
Annelise
Photo of Jared Burkeen

Jared Burkeen, Software Engineer

  • 23 Posts
  • 4 Reply Likes
Hi Jon,


I'm sorry for the delay in getting in touch with you and also that you've run into an issue that's impacting your job as a Web developer.
Which version of the .NET Framework are you using? There was an issue with LSPs and .NET Framework, so just make you have 4.5.2 or higher.
Also, we only install the LSP on Windows 7 and lower, so if you can upgrade to Windows 8 or 10 that also may resolve the issue.

Thanks,
Jared
Photo of aggieben

aggieben

  • 58 Posts
  • 8 Reply Likes
I'm having a problem that appears to be similar to this.  I need to connect to a server that is on a corporate VPN, to which I am connected via OpenVPN.  Sometimes the SQL Server connection works, but often it doesn't, with connections timing out more often than not.  When CE is not present I do not experience this problem, as far as I can tell.

I'm on Windows 10.  This has an ongoing cost to my productivity, and it's not small.
(Edited)
Photo of Robert B

Robert B, Official Rep

  • 324 Posts
  • 22 Reply Likes
aggieben,

Thank you for reaching out. I apologize for the inconvenience.

I have seen some cases where this type of issue disappeared when both programs (CE and the VPN) were removed, and CE was re-installed before the VPN was re-installed. I'd suggest trying that. If it doesn't appear to make a difference, please call us at 877-479-1119 so we can take a closer look at the situation.

Robert
(Edited)