Export Hangs Entire Browser

[Former Member]

I am using VS2010.  When I deploy to my web server (Win 2008 R2, IIS7.0) I can open a report in the Crystal Reports Viewer but when I click the export button the window opens to select file type and the entire browser hangs.

In the status bar it says "waiting for http://<servername>/<appname>/crystalreportsviewers13/js/dhtmllib/empty.html".  In task manager the iexplore.exe is chewing up 50% of my processor but still appears to be working.  I have to end the process to get control back.

The strange thing is I can log into server, pull up a browser and go to http://localhost/<appname>/<report> and it works fine.  As soon as I change "localhost" to "<servername>" it fails!

When I run it through fiddler I get 304: Not Modified on all the crystalreportsviewers13 requests.

I have tried everything I find online that might be close (which is why I am running the crystalreportsviewers13 folder in my app folder, was a suggestion).  Has anyone here ever seen this behavior?

[Former Member · Accepted solution]

Turns out is is because it was loading into a Telerik Radwindow.  I thought that was one of the first things I checked but I guess I missed something.

Still doesn't explain why it works on localhost but not when deployed to the web server but I am not going to lose any sleep over it.  I am just going to take them out of the rad window.

[former_member183750]

Hitting the export button causes a post back. It sounds like that the post back is not executing correctly. Perhaps putting the report in session will help. See KBA 1985571 - How to use sessions in web applications using the Crystal Reports viewer (the complete cod...

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

  Follow us on

Twitter

[Former Member]

It already is in session.  Besides, as I said, it works fine as http://localhost, just not when I change localhost to the server name.

[former_member183750]

Doing a bit of reading on 304, I don't think that is of any consequence in this case:

Understanding HTTP/304 Responses

Are yo able to do any other actions on the viewer; zoom, drill, print?

If yo page to the end of the report, can you export then?

How was the CR runtime deployed?

What SP did you use?

- Ludek

[Former Member]

print, zoom, and find all work fine.

it is only a one page report (at this time).

CR was installed on server from .msi.  I also moved the folder into my app directory and directed the web.config to look for it there (just trying to fix this issue).

I am not sure which SP it is, I can't find the msi that was used anywhere.

[former_member183750]

Hmm. Maybe we should start with removing the runtime that is installed on that computer. You should be able to find it under Add / Remove.

Then download SP 9 MSI from here:

Another test;

Create a new test app - one line of code:

CrystalReportViewer1.ReportSource = <path to a saved data report>

See how that works.

- Ludek

[Former Member]

reloaded CR, problem persists.

created new project as you suggested, deployed to web server just loading a saved data report and that works.

I will start adding my code in to load the real report in the test app and see if the problem appears then.  I will report back my findings.

[former_member183750]

Yeah - it will be very interesting to find out what is stopping the export.

Have a great weekend

- Ludek