Query Engine Error after Forced Protocol Encryption on Crystal Report

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

    Query Engine Error after Forced Protocol Encryption on Crystal Report

    After enabling forced protocol encryption on SQL server there are a handful of crystal reports that have the following error when you try to run them

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

    Turn the forced protocol encryption off on SQL Server and they work again just fine. I have tried re-choosing the data source of the .rpt files, and tried turning on Integrated Security before loading the reports with no luck

    Has anyone had this problem? Is there something that can be done to let these reports run with forced protocol encryption?
Working...