Report does not print from IE

[Former Member]

Hello....

We've developed an ASP application with several reports that access SQL Server data using

Crystal Reports bundled with Microsoft Visual Studio .Net. 2005.

The report renders just find and is ready to print. However, when you click the pinter icon in the BusinessObjects menu bar the dialogue box for Internet Explore appears. You click OK to print and it just hangs..... the report never prints. None of the other options work either ie export to pdf etc.

The report prints out fine in the development environment and was working in production until just a few days ago???

Any thoughts? Thank you in advance for your response!

Sandra

[ted_ueda · Accepted solution]

Try [Fiddler|http://www.fiddlertool.com/fiddler/] to see if you can detect any error messages in the communication channel between the client and server.

Sincerely,

Ted Ueda

[Former Member · Accepted solution]

Fiddler is not reporting any errors....

any other ideas?

[ted_ueda · Accepted solution]

So you're seeing the ActiveX Print control being streamed to the browser?

You're seeing the ActiveX Print control requesting report pages?

You're seeing the server send each page of the report to the ActiveXI Print control?

Since you've stated that it working in development, I'm assuming you've compared Fiddler with the working and non-working deployments, and they're the same?

Sincerely,

Ted Ueda

[Former Member · Accepted solution]

No I'm not seeing any reporting through this tool but what listed below:

# Result Protocol Host URL Body Caching Content-Type Process Comments Custom

4 200 HTTP CONNECT amci44:443 0 tmproxy:3376

5 200 HTTP CONNECT amci44:443 588 tmproxy:3376

6 200 HTTP CONNECT amci44:443 588 tmproxy:3376

7 200 HTTP CONNECT amci44:443 588 tmproxy:3376

8 200 HTTP CONNECT amci44:443 588 tmproxy:3376

9 200 HTTP CONNECT amci44:443 588 tmproxy:3376

[daniel_paulsen · Accepted solution]

if this was working and then suddenly stopped working (ie both printing and exporting), then it is most likely that something changed server-side. When printing and exporting, The viewer control needs to use files found in the Crystalreportwebformviewer3 folder (folder used for the version of CR bundled with VS2005).

Check the root of your website and make sure the following directory structure exists:

\aspnet_client\system_web\2_0_50727\crystalreportwebformviewer3\

if the directory structure has been deleted, copy it over from your development machine.

Dan

[Former Member · Accepted solution]

Dan,

Thanks so much! I did find crwebformveiwer files to be missing on the WebServer and did copy them over from my developement machine...

Still no printing!!! I did restart IIS and even rebooted the WebServer... bummer, any ideas?

thanks

Sandra

[daniel_paulsen · Accepted solution]

Hopefully that solved your exporting issues at the very least,

To find out what is going on with printing, open a report in the viewer, click print (this will cause a postback to the web page) and then cancel the print dialog. right-click in the web page and select "View source". search for the word "printcontrol.cab". This will show you where the application is trying to download the printcontrol from. Paste the URL into a browser to see if you get prompted to "open or save to disk". If so, the url is correct and there is a browser setting or possibly even a system policy preventing the download. If you get a "404 page not found" or something similar, then where is the URL looking? If its on your local web server, can you browse to the URL in IIS manager? (ie maybe another directory is missing on your server).

Compare the results with those on your working development machine.

If you still cannot figure it out, please post the URL to the cab file that you are seeing in the web pages source and we'll dig deeper from there.

Dan

Edited by: Daniel Paulsen on Mar 9, 2009 11:10 PM

[Former Member]

Hi,

You have ASP.Net web app using Crystal Reports bundled with Microsoft Visual Studio .Net. 2005 (CR 10.2) and not classic ASP right?

Thanks,

Prasad Kanchan

Edited by: Prasad Kanchan on Feb 23, 2009 8:39 PM