Error on server - printing stopped - Very First request to print any report

[Former Member]

vs2010 sp2

CR13 sp1

CR12 developed reports requested in app with no mods

I'm getting there but I can't get the very first print request honored regardless of

size to print on the very first request but will print when re-requested.

A very large detailed report (+300 pages) errors as well. The running time is

over 1 hour from rendering to print. The printing starts to spool but errors.

I've caching, sessions to keep the large report alive.

I have also increased timeout on the server.

Thanks,

Isaac

[former_member11696 · Accepted solution]

Same question as:

[Former Member · Accepted solution]

I fixed the problem with a bind on the report viewer

Thanks,

Isaac

[former_member11696]

Hi Issac,

Moved to .NET forum.

How Does the report when printing from the Report Designer?

Could be either a printer drvier issue or a permission issue with IIS. I assume it's a WEB app because you are keeping the Session open.

Some OLD printers use the OS as the memory buffer, could be one cause. Could be your Printer doesn't have enough memory to cache the print job.

Don

[Former Member]

Is is a website/web app

I found the following which makes sense in relation to initial prints etc.

Can you or someone tell me where to make this change in II6

which we are using on the sql server 2000 box (initially I was was told it was 2003)

ActiveX printing fails in the .NET web form viewer when IIS GZip Compression is in use. As a result, the following error message appears:

"A Communication Error Occurred. Printing will be stopped".

Cause

This is a known issue with Crystal Reports .NET. This issue has been assigned Track ID ADAPT00459349. At time of writing, there are no file updates to resolve this issue.

Resolution

To work around this issue, do one of the two suggestions offered below:

Disable compression for the following mime types:

application/x-eor (end of report)

application/x-ack (acknowledgement of printing finishing)

application/x-epf (encapsulated page format)

-OR-

Use HTTPZip instead of GZip for compression.

Thanks,

Isaac

[former_member11696]

According to the Adapts' step to replicate the issue here's how to create the error:

- In IIS 6, right-click on the "Web Sites" node of the IIS Management console and select "Properties".

- In the "Web Sites Properties" window, go to the "Service" tab and select both "Compress application files" and "Compress static files"

- stop and start IIS by clicking on Start --> Run and enter "iisreset". View a report in the version 10 .NET webform viewer using the ActiveX printmode. Once the report displays, try printing the report using the print button of the viewer. The error comes up after clicking "Print" on the Print dialog.

Don

[Former Member]

How can I make this problem go away?

II6 sql 2000 CR10/12 reports under vs2010, CR13 vb.net web site app,

I have been trying and tried all suggestions for the that 2 weeks.

Please point me in the right direction or solution. My time to complete

this task has ended.

Isaac

[former_member11696]

Hi Isaac,

I don' tthink this is a CR problem but either a print driver or IIS permission issue.

Try this link: http://support.microsoft.com/default.aspx?scid=kb;en-us;184291

And also update your print driver.

If all else fails then catch the exception then ignore it and print again.

Look in the IIS logs as well as the Event logs in the OS to see if it gives you more info.

Don

[Former Member]

I've noticed that the print hangs in the print spooler.

In some cases over 3-7 pages on reports over 15 pages.

The spooler stops outputting the print job

My test station is win xp sp3.

Are there any know problems.

The printers are not defind under iis 6.0 but have unique ip addresses

that appear in my printer selection list. On selection it's debatable if

the print session will work using the cr print button

Isaac

[former_member11696]

I don't believe this is a CR problem then, something in the Printer Driver is causing the delay or the Printer itself. If it doesn't have enough on board memory and then pushes the caching down to the OS, it can take time for this to happen. Once the cache is created on the OS then it stays their until a restart or something triggers it to be deleted. Then next printing will be delayed again.

Some Printers do this by default. Check the Printer Spec's on how it handles large print job's and how much memory is on board the printer.

As a test create a new printer and use the same driver as the original one but set the port to File, it will prompt for a location. Once the print job is complete then you can use a command line to push the file to PRN. Search MSDN for command line option to do this.

You could try pinging the makers of the Printer and driver and ask them to explain it also. CR is sending a "picture" of each page to be printed which does require a large amount of memory on the printer.

Don