Home Dashboard Directory Help
Search

PrintQueue.GetPrintCapabilities throws when incorrect driver is configured for printer on print server by Vadim Doroginin


Status: 

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


1
0
Sign in
to vote
Type: Bug
ID: 690455
Opened: 9/23/2011 7:11:29 AM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
3
Workaround(s)
view
1
User(s) can reproduce this bug

Description

PrintQueue.GetPrintCapabilities throws under several conditions.

System.Printing.PrintQueueException was unhandled
Message=PrintTicket provider failed to retrieve PrintCapabilities. Win32 error: -2147467259
PrinterName=\\PRINT\Программисты
Source=ReachFramework
StackTrace:
     at MS.Internal.Printing.Configuration.PTProvider.GetPrintCapabilities(MemoryStream printTicket)
     at System.Printing.PrintTicketManager.GetPrintCapabilitiesAsXml(PrintTicket printTicket)
     at System.Printing.PrintTicketManager.GetPrintCapabilities(PrintTicket printTicket)
     at System.Printing.PrintQueue.GetPrintCapabilities(PrintTicket printTicket)
     at ConsoleApplication1.Module1.Main()
InnerException:

Here is the condition: in printer properties under Advanced tab you have to select incorrect driver. For example: you have Samsung 4228FN and in printer properties you select Samsung ML-3550 driver.

I don't really know how bad it is to change driver to incorrect one, however, in our company there are about 40 printers, almost 80% of them is configured incorrectly (incorrect driver) and this configuration works for years now - every single program prints correctly in all modes possible. So, obviously, the problem is in .NET.

When you fire queue.GetPrintCapabilities(queue.UserPrintTicket) it throws mentioned exception.
When you create a new ticket, copy each field from UserPrintTicket to a new one - everything works great.
When you use UserPrintTicket.Clone - method GetPrintCapabilities with cloned ticket throws.

This behavior is tested on WinXP and Win7, both with latest updates. Dudes from DevExpress also reproduced the bug and helped to isolate the issue from calls to their libraries.


The background behind this problem is that XPS writer uses UserPrintTicket to print WPF visual and it fails in scenarios with incorrect driver. There is a workaround - you can assign newly created ticket to the queue.UserPrintTicket property.
Details
Sign in to post a comment.
Posted by Microsoft on 9/28/2011 at 3:24 PM
Thank you for your feedback. We will not be able to get around to this area of the product in this release of WPF. Since you do have a workaround, you are not blocked and can continue to work.

WPF Team
Posted by MS-Moderator10 [Feedback Moderator] on 9/26/2011 at 11:26 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by MS-Moderator01 on 9/23/2011 at 7:46 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)
Posted by Vadim Doroginin on 9/23/2011 at 7:22 AM
I've attached sample project which demonstrates the problem and the workaround.

        'queue.UserPrintTicket = ticket ' Uncomment this line to get Write method working


Remark: attached file didn't appear in file attachments, I believe there is some security check by Microsoft dudes which may take several days.
Sign in to post a workaround.
Posted by Vadim Doroginin on 9/23/2011 at 7:16 AM
UPDATE to the second workaround.

queue.UserPrintTicket = ticket

Also, you can do the same for DefaultPrintTicket.
This helps to enable printing through XpsDocumentWriter which uses UserPrintTicket to get capabilities no matter what ticket you pass to Write or WriteAsync methods.
Posted by Vadim Doroginin on 9/23/2011 at 7:13 AM
        Dim queue = LocalPrintServer.GetDefaultPrintQueue()

        Dim refTicket = queue.UserPrintTicket
        Dim ticket = New PrintTicket()
        ticket.Collation = refTicket.Collation
        ticket.CopyCount = refTicket.CopyCount
        ticket.DeviceFontSubstitution = refTicket.DeviceFontSubstitution
        ticket.Duplexing = refTicket.Duplexing
        ticket.InputBin = refTicket.InputBin
        ticket.OutputColor = refTicket.OutputColor
        ticket.OutputQuality = refTicket.OutputQuality
        ticket.PageBorderless = refTicket.PageBorderless
        ticket.PageMediaSize = refTicket.PageMediaSize
        ticket.PageMediaType = refTicket.CopyCount
        ticket.PageOrder = refTicket.PageOrder
        ticket.PageOrientation = refTicket.PageOrientation
        ticket.PageResolution = refTicket.PageResolution
        ticket.PageScalingFactor = refTicket.PageScalingFactor
        ticket.PagesPerSheet = refTicket.PagesPerSheet
        ticket.PagesPerSheetDirection = refTicket.PagesPerSheetDirection
        ticket.PhotoPrintingIntent = refTicket.PhotoPrintingIntent
        ticket.Stapling = refTicket.Stapling
        ticket.TrueTypeFontMode = refTicket.TrueTypeFontMode


        Dim capabilities1 = queue.GetPrintCapabilities(ticket) ' OK
        Dim capabilities2 = queue.GetPrintCapabilities(refTicket) ' Throws
Posted by Vadim Doroginin on 9/23/2011 at 7:12 AM
Most obvious one: setup a correct driver in printer properties.
If the printer is shared, do it on the print server.
File Name Submitted By Submitted On File Size  
WpfApplication2.zip 9/23/2011 10 KB