Crystal Reports 13: Intermittent printing errors

[Former Member]

Hi,

We are using Crystal Reports 13 in a web application, running under a 32-bit app pool in IIS, on Windows Server 2012 (64 bit). For two separate customers (different locations ad printer types), there will be seemingly random errors when printing: either "Access denied" or "Invalid printer specified". These errors do not have a clear reproduction path, and we cannot reproduce them locally: sometimes a user will not be able to print a report, but after retrying a few times, it will work (so access denied is out). While this is happening, other users are able to print, without issues, using the same printer (so invalid printer is also out). Sometimes, a user will be able to print reports, and after a few successful prints, a print will not work. The printers are correctly set up, drivers installed, and not hitting printing limit, hence why most of the time printing goes alright. However, this is something that happens every once in a while for at least a few months, if not for a few years.

The code is using PrintToPrinter. The report document objects are being disposed of after printing.

I found several threads in the archive here, describing similar issues, but there was no clear resolution on any of them. Did anyone who encountered this issue find a solution?

Thank you.

[ido_millet · Accepted solution]

Any chance this is due to an uncaught exception due to hitting the Crystal runtime maximum print jobs limit?

Just to clarify: "Print Jobs" limit is related to the runtime processing reports and subreports -- it's not "print" in the usual sense. So if the problem occurs when the server is busy handling many report requests, this may explain it.

[former_member11696]

Hi Diana,

You can try the latest SP 22, it uses updated Framework and Windows updates so it may fix this issue.

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

PLEASE Read the info on SP 21 update and how to update your project.

I believe it has something to do with the Framework used but like you I can't repro the issue either.

There is one outstanding issue when using the help file that is Framework specific and R&D can find the cause either.

Possibly look in the Event logs to see if it captures anything.

I don't think it's permissions either but resources, print Spooler is busy and rejecting the stream from the engine to print a report. Then CR gets the reply and it can fail to submit the next job, something attached to that user. Possibly their c:\users\local\temp folder may be full... you can try clearing it.

Without any logging or something capturing the error it's hard to say what the problem is...

I suggest updating to SP 22 and setting your projects Framework to the most current 4.6.x. That may resolve the problem.

Customers will also need to make sure they are updated with all of the Windows patches as well.

Don