Peport-engine give exception or sometimes completelly hangs up!

[_Alex_74_]

Hello,

sometimes we have very rare strange exception as shown here:

----------------------------
[Customer Explanation]


----------------------------
[General Info]

Application: Stimulsoft Reports.Net
Framework: v2.0.50727
Version: Version: 2009.1.362 from 8 April 2009
MachineName: FC-330-04-M11
OSVersion: Microsoft Windows NT 5.2.3790 Service Pack 2
UserName: MARI-D

----------------------------
[Exception Info]
Message: Aufruf "StartDocPrinter" wurde nicht ausgeführt

Source: System.Drawing

StackTrace:
at System.Drawing.Printing.StandardPrintController.OnEndPrint(PrintDocument document, PrintEventArgs e)
at System.Drawing.Printing.PrintController.Print(PrintDocument document)
at System.Drawing.Printing.PrintDocument.Print()
at Stimulsoft.Report.Print.StiPrintProvider.Print(StiReport report, Boolean showPrintDialog, Int32 fromPage, Int32 toPage, Int16 copies, PrinterSettings printerSettings)

----------------------------
[Assemblies]
mscorlib, Version = 2.0.0.0
Stimulsoft.Base, Version = 2009.1.362.0
Stimulsoft.Report, Version = 2009.1.362.0
Stimulsoft.Report.Design, Version = 2009.1.362.0
System.Windows.Forms, Version = 2.0.0.0
----------------------------

The printer modell is : HP LaserJet 4050 Series PCL6.

We have noticed, that this can be reproduced if the printer is gone in power-safe mode.
The other programms put the job in the printer queue without throw an exception.
In this situation we can sometimes see on windows printer the status of the printer: 'access denied, connection refused'.
But as sad, other programms has no problemos.

In the rare cases, the stimulsoft engine hangs up and does not give feedback.

Sorry, but I can't attach the printer hardware here :sure:

Thanks in advice.
Alex

[Andrew]

Hello,

Report printing in our report goes by means of .Net (via the GDI+ system library). Printing is done via calling one PrintDocument.Print() command, and then all operations, inluding data exchange with a printer, are done by .Net. We cannot control this process. It is even impossible to get the error code, when printing, by means of .Net.

We found some information in the internet and found the following information.
If by some reasons a printer stops responding to queries (for example, goes to the power-safing mode), when calling it, a printer port throws the error. When printing using Win32 (GDI), the printer driver correctly defines the error and outputs a printer from the power-saving mode or remains task in printer's pool. When printing from .Net, this error of the printer port works incorrectly and .NET simply stops and throws error.

Thank you.