cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Crystal Reports - Report Failing over HTTPS

dstolldorf
Explorer
0 Likes
2,244

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!

View Entire Topic
DonWilliams
Active Contributor
0 Likes

Hi Daniel,

Fiddle may show you it's trying to load a dll from the wrong place or could show a security issue.

CR runtime is platform specific so if your AppPool is 64 bit CR requires a 64 bit DSN, I don't see you mention that.

Set the Project to X64, not anyCPU, set up a 64 bit DSN

See if that helps.

CR does care if you use HTTP or HTTPS, security is all in the backend.

Don

dstolldorf
Explorer
0 Likes

Hello Don,

Our server admin created a domain user and added that user to the server's IIS_IUSR group. We then changed the app pool to run using this new user. The rest of the website still works, ADO.Net commands are able to run and view compiling has access to the necessary temp folders. Still unable to generate reports with CR.

I then updated the project to run using the x64 platform. Given all the changes I had to make to the project to get that to build, I think it's safe to say it was building as a x86 app. I then made a 64-bit DSN and add web.config transformations so if deployed on the x64 platform it'll use the new DSN name. Deploying the app in strict 64-bit and strict 32-bit modes did not make any difference other than I saw w3p3.exe running under their respective deployed platforms. I also confirmed after deployment that the deployed web.config had the correct DSN.

I apologize, I am unfamiliar with the usage of Fiddler. What would I setup to get the web app to display access denied or incorrect dll loading in Fiddler?