Problems with crystal after sql server protocol encryption

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jeffstl
    Recognized Expert Contributor
    • Feb 2008
    • 432

    Problems with crystal after sql server protocol encryption

    After checking the box "Force Protocol Encryption" on SQL Server Network Utility there are several Crystal reports that begin to throw the following error when run

    Query Engine Error: '08S01:[Microsoft][ODBC SQL Server Driver]Communication link failure'

    Go back into the Server Network Utility and uncheck the Force Protocol Encryption and they work fine again.

    Is there anyone that has encountered this before? Used the protocol encryption before? Any ideas about what to do?

    FYI - I have re-selected the data sources on the .rpt files and it made no difference. I also tried to check around for ODBC type of properties that might need to be changed. The only thing I ended up trying was the below in the app to see if it made any difference (.NET)
    Where tLogin is CrystalDecision s.Shared.TableL ogOnInfo
    Code:
                        'Trying the below settings to get crystal reports to run with forced protocol encryption on sql server
                        tLogin.ConnectionInfo.IntegratedSecurity = True
                        tLogin.ConnectionInfo.AllowCustomConnection = True
Working...