Skip to main content

TLS renegotiation error

  • June 9, 2020
  • 4 replies
  • 4 views
serban

Hi folks,
I'm getting the TLS renegotiation error in SSIS, both when using the ODBC and the OLEDB connections (v10.0.0):

Source: "Vertica OLE DB Provider" Hresult: 0x80004005 Description: "[Vertica][VerticaDSII] (20) An error occurred during query execution: Renegotiate requested by the server. Schannel does not support renegotiation. For vertica server versions above 9.2.1, consider setting the configuration parameter 'TLSRenegotiationLimit' to zero. The connection will be closed. server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.".

I have absolutely no idea how to proceed.

Any help appreciated.

Best regards,
Serban

    4 replies

    Jim_Knicely
    Forum|alt.badge.img+2
    • Jim_Knicely
    • Participating Frequently
    • June 9, 2020

    See: https://forum.vertica.com/discussion/comment/244912

    serban
    • serban
    • Author
    • New Participant
    • June 10, 2020

    Hey, Jim, thanks for that - was already aware of that post. Was already aware of the issue fix description in the release notes but not much I can do with that.
    No idea which server version we're running and no way to make any configuration changes.
    Lastly, in ODBC data source I can't see any TLS configuration parameters.
    Odd thing is I'm running the ODBC connection from Visual Studio 2013 on Windows server 2008 and it works with no issue on Vertica drivers v9. But on Windows Server 2019 and Visual Studio 2019 and Vertica drivers v10 both ODBC and OLEDB fail.

    Thank you!
    Serban

    SergeB
    Forum|alt.badge.img
    • SergeB
    • Participating Frequently
    • June 12, 2020

    Really hard to say without knowing the version of your Vertica cluster. But wanted to clarify that TLSRenegotiationLimit is set at the Cluster level; e.g. select set_config_parameter ('TLSRenegotiationLimit',0);

    serban
    • serban
    • Author
    • New Participant
    • June 16, 2020

    Hi folks,

    Reverting to 9.0.x drivers fixes it. Should have reviewed the compatibility matrix.

    Thank you!

    Still scrolling?
    Ask a question
    Terms & ConditionsAccessibility statement