Home Dashboard Directory Help
Search

Cancel Printing cause "A StartDocPrinter call was not issued" error in .NET x86 app by Myexp


Status: 

Closed
 as Won't Fix Help for as Won't Fix


1
0
Sign in
to vote
Type: Bug
ID: 745157
Opened: 5/31/2012 2:02:56 AM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I use PrintDocument and PrintDialog classes to do the print task. If the printing is under processing and I press ESC key to cancel the print, there is an error popup shows "A StartDocPrinter call was not issued". This happen on latest .NET 4.0 with x86 build application. The x64 build app works fine.
Details
Sign in to post a comment.
Posted by Microsoft on 6/6/2012 at 3:44 PM
Thank you for reporting this issue. Customer feedback is a critical part of a successful, impactful software product. Unfortunately another part is the reality of schedules and the need to prioritize investments according to the objectives of the product. We have evaluated the issue that you have reported and at this point in the product's lifecycle, it does not meet the criteria to be addressed. This evaluation is carefully done and considers many aspects including the cost of the fix, implications of the change, and the number of reported instances of the issue.


Many customers have found it useful to discuss issues like this in the forums (http://www.microsoft.com/communities/forums/default.mspx) where Microsoft and other members of the community can recommend ways of achieving the behavior you are interested in.

Thank you,
The Windows Forms Product Team
Posted by Myexp on 6/3/2012 at 3:18 AM
Thank you for your response. I have already think of putting a try-catch block for the code piece. But in doing this will swallow all Win32 exception which is useful for us for a printing failure.
Posted by Microsoft on 6/1/2012 at 1:07 PM
Hello Myexp,

Thank you for reporting this issue. Customer feedback is a critical part of a successful, impactful software product. Unfortunately another part is the reality of schedules and the need to prioritize investments according to the objectives of the product. We have evaluated the issue that you have reported and at this point in the product's lifecycle, it does not meet the criteria to be addressed. This evaluation is carefully done and considers many aspects including the cost of the fix, implications of the change, and the number of reported instances of the issue.

This exception is raised when native API "AbortDoc" fails:
http://msdn.microsoft.com/en-us/library/windows/desktop/dd162456(v=vs.85).aspx
and indicates that print job can't be canceled cleanly. You might want to ignore this exception:

            try {
                    pdoc.Print();
                }
                catch (Win32Exception) {
                }

Many customers have found it useful to discuss issues like this in the forums (http://www.microsoft.com/communities/forums/default.mspx) where Microsoft and other members of the community can recommend ways of achieving the behavior you are interested in.

Thank you,
The Windows Forms Product Team

Posted by MS-Moderator10 [Feedback Moderator] on 5/31/2012 at 7:42 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by MS-Moderator01 on 5/31/2012 at 2:43 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
CSWinFormPrintError.zip 5/31/2012 11 KB