on 2025 Feb 04 10:23 AM
We have ASP .NET web application which uses Crystal report services to generate the report. We have .rpt file for each type of our report and it generates the PDF report. We are using Crystal report 2016 on Windows server 2016 and .NET 4.8. The Crystal report works fine with TLS 1.0 and but its not working with TLS 1.2. When tried to generate the report with TLS 1.2 then we are getting 'SSL Security error SQL state 08001. Native error 18. [Database vendor code: 18]' error message.
Here is code snippet of VB .NET code file where the database details are passed to .rpt file to generate the report.
This is the error message we are getting -
Do we need to upgrade to Crystal report 2020 to resolve this issue? Let us know any solution for this issue.
Request clarification before answering.
See this KBA I wrote years ago on how to:
https://userapps.support.sap.com/sap/support/knowledge/en/2269180
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for reply. As mentioned in the above post, its not an crystal report issue its about the database driver we are using, correct? So, can we resolve the issue with Crystal report 2016 version itself and no need to upgrade it to 2020 to resolve this issue? There are multiple crystal report files we are using (.rpt files) in our application, do we need to update all .rpt the files with ODBC latest driver and update data source location if we have to resolve this or it can resolved at one place. Please let me know your thoughts?
| User | Count |
|---|---|
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.