Unrecoverable system error from PrintWithWpf()

[LukasT]

Hello,
some of our custommers has problem, that our application failed due unrecoverable error .... see next StackTrace:

Code: Select all

Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unrecoverable system error.
Stack:
   at System.Environment.FailFast(System.String)
   at MS.Internal.Invariant.FailFast(System.String, System.String)
   at MS.Internal.Printing.Configuration.WinSpoolPrinterCapabilities.GetArrayCapability[[System.UInt32, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](MS.Internal.Printing.Configuration.DeviceCapability, ReadArray`1<UInt32>, Int32)
   at MS.Internal.Printing.Configuration.WinSpoolPrinterCapabilities.GetArrayCapability[[System.UInt32, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](MS.Internal.Printing.Configuration.DeviceCapability, ReadArray`1<UInt32>)
   at MS.Internal.Printing.Configuration.WinSpoolPrinterCapabilities.get_NUp()
   at MS.Internal.Printing.Configuration.FallbackPTProvider.GetPrintCapabilities(System.IO.MemoryStream)
   at System.Printing.PrintTicketManager.GetPrintCapabilitiesAsXml(System.Printing.PrintTicket)
   at System.Printing.PrintTicketManager.GetPrintCapabilities(System.Printing.PrintTicket)
   at System.Printing.PrintQueue.GetPrintCapabilities(System.Printing.PrintTicket)
   at System.Windows.Controls.PrintDialog.UpdatePrintableAreaSize()
   at System.Windows.Controls.PrintDialog.get_PrintableAreaWidth()
   at Stimulsoft.Report.Print.StiWpfPrintProvider.SetPrintTicketFromPage(System.Windows.Controls.PrintDialog, Stimulsoft.Report.Components.StiPage, Double ByRef, Double ByRef)
   at Stimulsoft.Report.Print.StiWpfPrintProvider.Print(System.Object, Boolean, Int32, Int32, Int32, System.String)
   at Stimulsoft.Report.StiReport.PrintWithWpfInternal(System.Object, Boolean, Int32, Int32, Int32, System.String)
   at Stimulsoft.Report.StiReport.PrintWithWpf(System.Object, Boolean, Int32, Int32, Int32, System.String)
...

.... this is system issue and exists some hotfix, which solving this ( http://www.microsoft.com/en-us/download ... n&id=11816 ), but will be great to you to somehow catch this exception, if it is possible....

Thank you.

[Alex K.]

Hello,

Sorry for the delay with response.

Can you please send the following information:
• Product name and its version;
• Detailed description of the problem and how to reproduce it;
• Your operational system (98, ME, 2000, XP, Vista or NT), its version and localization, installed service-packs;
• Version the of Microsoft .Net Framework package installed and its localization;
• Name of your development framework and its version;
• Additional information that can help us to solve your problem.

Thank you.

[LukasT]

Hello,
this error occured on our custommer PCs with win XP .... configuration was:

Microsoft Windows NT 5.1.2600 (XP) Service Pack 3|32bit OS|32bit Process|1 core
Framework .NET 4.0.30319.296

Using WPF Stimulsoft and it fails on all versions....

Here are some informations about this bug http://social.technet.microsoft.com/For ... easy-print

And you can see in StackTrace (top post) where is the place to put try/catch in your code and throw some better exception, if it is possible...

[HighAley]

Hello, Lukas.

There is already a try..catch statement.
Please, try to set next option:

Code: Select all

StiOptions.Engine.HideExceptions = true;

This will hide all exceptions that where caught.
But there still could be some critical errors which couldn't be caught by .Net Framework.
If this exception will still occur then this is such critical error.

Thank you.

[LukasT]

I see.... in fact it failed due kill of process (FailFast) .... in system library is some exception which is solved by kill of process... so only one solution is to install the hotfix.
Thank you for help with investigation

[LukasT]

The same problem has been discussed even here http://forumru.stimulsoft.com/viewtopic.php?f=12&t=1933 ....

[HighAley]

Hello.

Thank you for last note. We have added the link on the fix to that forum topic.

Thank you.