none
Troubleshooting Windows Server 2012 printing error, Custom Print driver code RRS feed

  • Question

  • We are getting this error intermittently for a custom print driver. The customer upgraded from windows 7 to 10. The issue is intermittent with some documents and workstations. Driver is installed on windows 2012 R2 server and the driver is shared among workstations. Could it be a usergroup policy issue. IT says that its only for production workstations. They made a clone of this workstation and printing has no problem!. I don't know the difference between a workstation and a clone of the workstation. This is a Type 3 print driver

    We have an application written by a developer more than 7years back. The application has a print driver, print port, broker, print publisher, client. I am able to compile all the parts of the application and connect each one to talk to another except print driver. This print driver is written in c++. I don't know how to compile and troubleshoot this legacy black box driver code. I am afraid because of the legacy nature of the driver, it might have to be debugged and rebuilt. But any suggestions on where to start to rebuild/debug/troubleshoot this print driver. These are the files available in the print driver folder in source control. The output of this print driver is PCL. Please suggest. I have never done windows driver development. My experience with c++ is minimal. 

    1) How I do build this to be able to generate a print driver, .ini file. This is legacy code and still being used. Its upto me now to figure out how to actually make this code generate an output. 

    2) All I know is the output of this black box code is a PCl which is then later on in the application converted to a TIFF. This TiFF is written to the drive

    3) We have a customer who TIFF is not being written. I intercepted the input to the applicatoin and tried to see if the PCL is being received. It looks like the PCL file only the header is generated and there is no other data. Now I am leaning towards PCL not being generated by the print driver because of some font issues or registry

    4) Happens on some documents after a windows 7 to 10 upgrade. How do I troubleshoot this print driver. Please suggest. What am I looking for in a process monitor log. 

    5) Could this be the problem see the good procmon and bad

    Good

    Bad: SetAllocationInformationFile is missing in the bad file proc mon

    I appreciate reading this post

    


    sunDisplay





    • Edited by SunDisplay Monday, August 26, 2019 3:17 AM
    Friday, August 23, 2019 3:58 AM

All replies

  • The code was written to be build with the Windows 7 WDK.  The "sources" file is the clue to that.  Within one of the WDK build environments, you use the "build" command to build the driver.

    Tim Roberts | Driver MVP Emeritus | Providenza & Boekelheide, Inc.

    Sunday, August 25, 2019 4:59 AM
  • @Tim Roberts:

    Thank you for the reply. Is it possible to run it on a windows 10 or windows 8 build environment? Currently I have a windows 8 computer and windows 10 surface. On the windows 8 laptop I have VS 2010, 2012,  On surface VS 2019

    If I were to develop on windows 8 which one should I use VS 2010 or 2012. Sorry for such generic questions. 

    Also, any help troubleshooting why it wont work on a windows 10 machine sometimes. What tools do you recommend to troubleshoot the print driver? I have a process monitor log for both working and non working files. There are many spool.exe things in the working file. 

    The output of the driver is a PCL file. In a working file the PCL is good and i can view it. But in a non working file I cannot view the PCL or it doesn't have any PCL. I cannot reproduce the problem except on the customers PC. Please suggest.

    This is the error being recorded in event viewer on the server. The printer is shared. It is installed on the server and shared on the workstations. In Proc Monitor should  be looking for spooler.exe issues or 'PRINT TEST' issues? Please suggest

    The document Print Document, owned by TST, failed to print on printer "PRINT TEST'. Try to print the document again, or restart the print spooler.

    Data type: NT EMF 1.008. Size of the spool file in bytes: 628788. Number of bytes printed: 12900. Total number of pages in the document: 6. Number of pages printed: 0.

    Client computer: LAP05. Win32 error code returned by the print processor: 2147500037. Unspecified error

    Thank you


    sunDisplay




    • Edited by SunDisplay Monday, August 26, 2019 4:17 AM
    Sunday, August 25, 2019 7:24 PM