none
VS2017 print fails with error: PrintTicket provider failed to convert PrintTicket to DEVMODE ... RRS feed

  • Question

  • I cannot print from VS2017.

    Printing from VS2010 and VS2015 both work fine but when I try to print from VS2017 (File - Print...) a message box pops up with the error "PrintTicket provider failed to convert PrintTicket to DEVMODE. Win32 error: -2147221164"

    I'm pretty sure (not certain) that I've successfully printed from VS2017 before. I recently uninstalled OneDrive and also installed SSDT (SQL Server Development Tools) for VS2017, either of those changes could be the cause.  No new printers or printer drivers have been installed recently.

    The Windows Application event log points me to a .WER file with the following contents:

    Version=1
    EventType=PnPDriverImportError
    EventTime=131501180341559847
    Consent=1
    UploadTime=131505584224753577
    ReportIdentifier=b375a8b9-9b93-11e7-b2f4-989096a475f8
    WOW64=1
    Response.BucketId=10
    Response.BucketTable=5
    Response.type=4
    Sig[0].Name=Architecture
    Sig[0].Value=x86
    Sig[1].Name=Win32 error
    Sig[1].Value=E0000244
    Sig[2].Name=Inf name
    Sig[2].Value=prnms006.inf
    Sig[3].Name=Driver Package hash
    Sig[3].Value=7050f755c38ecac2f082f37a636e5d81310d5019
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.256.4
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    State[1].Key=DataRequest
    State[1].Value=Bucket=10/nBucketTable=5/nResponse=1/nEvent_Kinshu=2592000/nEvent_Throttle=2592000/n
    FriendlyEventName=Could not install driver software
    ConsentKey=PnPDriverImportError
    AppName=Driver software installation
    AppPath=C:\Program Files (x86)\Microsoft Office\root\Integration\Integrator.exe
    ReportDescription=Windows could not copy all of the files needed to install this device driver software. This sometimes happens when the driver software was not designed for this version of Windows.

    HOW DO I FIX THIS?!

    Friday, September 22, 2017 1:15 PM

Answers

  • This forum is worse than useless. Not only wasn't there any good advice, my post was moved to the wrong forum. Good grief, what a waste of time.

    For anyone else who encounters this error, I solved the problem by uninstalling and reinstalling VS2017, an hours-long process, by the way.

    Mike Z

    • Marked as answer by MikeZ2017 Wednesday, September 27, 2017 3:57 PM
    Wednesday, September 27, 2017 3:57 PM

All replies

  • Hi,

    Welcome to MSDN forum.

    Could you please provide us with more information on printing environment?

    Since this forum is to talk about Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor. You could contact the printer manufacturer for assistance in updating the printer driver.

    Best regards,

    Joyce


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    Monday, September 25, 2017 5:40 AM
  • Hi Joyce,

    How could this be a printer driver issue?

    Let me remind you that printing works fine from Visual Studio 2012 and Visual Studio 2015. It's only Visual Studio 2017 that fails with that error.

    And what "information on printing environment" would you like? Please be specific.

    Best regards,

    Mike Z

    Monday, September 25, 2017 12:13 PM
  • This forum is worse than useless. Not only wasn't there any good advice, my post was moved to the wrong forum. Good grief, what a waste of time.

    For anyone else who encounters this error, I solved the problem by uninstalling and reinstalling VS2017, an hours-long process, by the way.

    Mike Z

    • Marked as answer by MikeZ2017 Wednesday, September 27, 2017 3:57 PM
    Wednesday, September 27, 2017 3:57 PM
  • FWIW

    I just ran into this error for the first time today, in Visual Studio 2017. 
    I am not sure when I last printed out of VS 2017, most of my recent printouts have been from SSMS, but I am sure it has been no more than a week, and I have not changed any printer drivers or installed any major updates to VS in that time. 

    I am not looking forward to reinstalling all of VS 2017 + SSDT + the rest of the extensions that I use in order to get simple printing functionality. If there was printing in VS Code that would be a fine work around - all I want is color-coded intellisense and line numbers, but I don't use any tools other than VS2017 and VSC that provide that. 

    What a pisser.

    Wednesday, November 1, 2017 7:29 PM
  • Yes, I have the same issue with VS2017. Come on Microsoft, are you not supposed to provide answers to problems?
    Monday, November 13, 2017 10:15 AM