on ‎2023 Mar 14 8:35 AM
We've recently added an SSL to our front facing client site. The rest of the site works and is able to make database calls through ASP.NET.
While accessing the site through HTTP the reports generate fine. If the protocol is changed to HTTPS, all reports are now returning the below image

The database connection is setup as an ODBC 32-bit connection so as I do not have to go through hundreds of reports to manually update the credentials (migrated from an older system). I've tried setting up the ODBC using the SQL Server Native Client 11.0 Version 2011.110.6540.00 and CR SQL Server Native Wire Protocol ODBC 7.1.5 Version 7.10.106.324. Either of these ODBC connections work within reports and while running the website locally in Visual Studio or in HTTP on IIS.
Crystal Reports 2016 Support Pack 5
Version 14.2.5.2618
Windows Server 2016 Standard
IIS 10.0
Microsoft SQL Server Standard (64 bit) Version 14.0.2047.8
As per this answer thread I've tried changing the application pool for the site to run in classic mode rather than integrated with no difference. The linked resource in the best answer returns a not found error.
Any help would be greatly appreciated!
Request clarification before answering.
Use Google and search for how to...
Capture all IIS traffic, on the Web server in Fiddler | Telerik F
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 3 | |
| 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.