Crystal Reports - Report Failing over HTTPS

[dstolldorf]

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!

[moshenaveh]

Welcome to the SAP Community! Thank you for visiting us to get answers to your questions.

I recommend that you include a profile picture. By personalizing your profile, you encourage readers to respond: https://developers.sap.com/tutorials/community-profile.html.

I hope you find this advice useful, and we're happy to have you as part of SAP Community!

[DellSC]

Which version of the Crystal .NET SDK are you using and which version of Visual Studio?

-Dell

[dstolldorf]

Visual Studio Professional 2017 Version 15.9.7

.NET Framework 4.6.1

All of the references within the project for CrystalDecisions has v2.0.50727

Referenced path: C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dotnet\

Installed Apps

Crystal Reports runtime engine for .NET Framework (64-bit) Version: 13.0.25.3158

Crystal Reports, version for Microsoft Visual Studio Version: 13.0.25.3158

[moshenaveh]

dstolldorf

I'm glad to see you got an answer to your question! If it helps you, please make sure to accept (you'll see the "accept" option beneath the question) -- so members with similar issues will be able to find a solution to their problems too.

If it doesn't help, you can always leave a comment providing more details that can guide members who wish to assist you.

I hope that this guidance is useful -- and we look forward to your next question for the community!

[DonWilliams · Accepted solution]

Hi Daniel,

CR shouldn't care how you log into your web site, this I believe is a IIS configuration issue, likely permissions for the AppPool or possibly the IIS Temp Folder, CR require full read/write permissions.

I also suggest upgrading to SP 22, SP 25 is quite old:

https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads

And see my blog on upgrading:

https://blogs.sap.com/2020/10/30/upgrading-a-visual-studio-2008-2019-.net-project-with-the-latest-cr...

Fiddler may show you where it's failing or Possibly ProcessMonitor.

Does your app have the Viewer Embedded in it? IF so what happens when you export from the Viewer?

If you don't write a simple test program and remove CR from the picture and simply try to log onto the DB using ADO.NET and see if that works.

Don

[dstolldorf · Accepted solution]

Hello Don,

Thank you so much for your assistance, unfortunately after updating to SP 33, publishing, and restarting we still have the same issue.

This client has the same project being deployed to two locations, an internal only site with read/write to the database and an external reporting site with read only access. The internal site, which is HTTP only, does not have any issues with generating CR reports. The external site successfully generates reports when connected to via the HTTP protocol. When the user is connected via the HTTPS protocol is when the Database logon error occurs.

Using ProcessMonitor I did see one ACCESS DENIED for an AppData/Local folder, but adding the Full Access permission to the IIS_IUSR group did not fix the issue.

In order to access the reporting section clients must first login. This login process does use the ADO.Net System.Data.SqlClient namespace for DB queries. On the HTTPS version clients are able to login and dropdowns populated from the database also work.

I don't believe the Viewer is embedded in the app, at least no reference to it that I can find.