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.
How about using Fiddler to see if it catches the permission issue.
If you run IIS under a specific user does that work?
CR must have full read/write permission to the IIS \Temp folder, when exporting we first attempt to write a file and the try to delete it to check permissions, if we can't the export will fail.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess I'm missing how Fiddler is supposed to help me diagnose the issue when all it does is capture web request traffic. It's not telling me anything new the browser wasn't already telling me. I have the error logs and stack trace already.
I'll have to talk with the server admin about setting up a new user for the app pool.
As it is, IIS_IUSR group has read/write permissions to the following:
C:\inetpub\temp
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files
The reports generate fine when using the HTTP binding under the same app and app_pool, so that would lead me to believe it has all the file permissions it needs.
| 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.