Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
Event 17835 (Error) MSSQL ISARS

Unanswered Event 17835 (Error) MSSQL ISARS

  • Friday, February 08, 2013 4:19 AM
     
     
    Sign In to Vote
    0
    Hi,
    Self is using Forefront TMG 2010 (Ver-7.0.9193.500) on Win-2008 R2 platform  , it is currently reflecting error "Event 17835 (Error) MSSQL ISARS".
    The log details are below ; 
    Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgrade your client library. [CLIENT: 101.226.1.176].
    Please help.

    Regards, Kumar Lokesh Singh, Assistant Manager Systems, Larsen & Toubro Ltd.-ECC Division.

     

All Replies

  • Saturday, February 16, 2013 9:50 PM
     
     
    Sign In to Vote
    0

    Hi

    I have the exact same issue with TMG 2010 (7.0.9193.515) on Win 2008 R2. just a different IP

    do you have any progress?

    I went to the SQL Server configuration Manager > SQL Server Network Configuration > Protocols for ISARS

    then I change the force encryption from "YES" to "NO" but it didn't help.

    I guess I need a certificate for that. the question is - for what is in necessary and if so do I have to buy a cert or use a self sign one?

    thanks

    Tamir Levy

     
  • Monday, February 18, 2013 6:48 PM
     
     
    Sign In to Vote
    0

    Hello,

    the error message could be because of:

    1. SQL Server is configured to SSL encryption is used in connection to a SQL Server from a client is error indicating that because the client does not support it, the connection request has failed.

    2. SQL Server on Forefront UAG is configured such that the use of encryption SSL.

    So you can try:

    1. In the start menu, [Microsoft SQL Server] - Select [SQL Server Configuration Manager] - [Configuration Tools].
     Select the [Properties] Right-click the protocol for the instance     ISARS

    2) Expand the [SQL Server Network Configuration], [Flags] tab, check the configuration of the database engine [Force Encryption] option. If that is a "Yes", it is configured to encrypt. Check if you can disable force encryption if it is set to True.

    3) restart the SQl instance and check the connectivity from the application.

    If the above steps mentioned above doesnt help, please revert the changes.

     
  • Monday, February 18, 2013 9:55 PM
     
     
    Sign In to Vote
    0

    Could you post the messages from SQL errorlog. If SSL encryption is enabled you should see a message in SQL errorlog something like below. SSL encryption can be enabled Service side or client side. If it is server side then all connection will be encrypted and if it is client side then only the specific clients connections will be encrypted where the force encryption is enabled

    The certificate [Cert Hash(sha1) "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"] was successfully loaded for encryption.