locked
Windows 2008 TS Printing - Event 6161, Print Spooler - Win32 error code returned by the print processor: 122. The data area passed to a system call is too small. RRS feed

  • Question

  • We were getting the above  error messages usually mid-afternoon. General “web” consensus seems to be these errors are caused by the following: 

    •  The printer is not reachable on the network
      Windows cannot allocate sufficient memory
      There was invalid or incomplete data received by the print spooler
      A driver upgrade failed
      There is a bad printer device driver

    Our "old" Terminal Server had 3rd party print drivers, 3rd party print monitors, was undersized (4gb memory) and did not have SP2.  So we built new Windows Terminal Server 2008 Enterprise, by the book (note, not R2):

    • Memory now 20 gb
      One print driver, TS Easy Print,
      One print processor, winprint
      Up to date with all Service Packs and updates

    Error 6161 still happens on the new server.  The only way we have around this error message is for clients to log out and log back into the Terminal Server.

    Note, we started with the print spooler team but they direct us to the RDP group.  More details can be found here: http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/32d52132-2087-4e03-869f-74a7f485743a/

    Thx!



    • Edited by Dilutiano Tuesday, February 14, 2012 4:54 PM
    Tuesday, February 14, 2012 4:41 PM

Answers

  • In our case, TS Easy Print was the problem.
    • Marked as answer by Dilutiano Friday, February 24, 2012 9:27 PM
    Wednesday, February 15, 2012 8:02 PM

All replies

  • In our case, TS Easy Print was the problem.
    • Marked as answer by Dilutiano Friday, February 24, 2012 9:27 PM
    Wednesday, February 15, 2012 8:02 PM
  •  

    Follow-up configuration question, now that EZ Print is disabled in GPO is there a way to control the amount of drivers created on the TS?

    Scenario: We have about 100 machines and each needs two printers, one for reports and one for labels.  To support the label printers we need 3 different drivers to be on the server and we would like all the report printers to use the EZ Print.

    As it stands now, every printer and driver combo out there is being auto-created on the server along with the suspect 3rd party print monitoring software.

    Default GPO Settings:

    Enabled or Not configured: If this policy setting is enabled or not configured, the terminal server will first try to use the Terminal Services Easy Print driver to install all client printers. If for any reason the Terminal Services Easy Print driver cannot be used, a printer driver on the terminal server that matches the client printer will be used. If the terminal server does not have a printer driver that matches the client printer, the client printer will not be available for the Terminal Services session. By default, this policy setting is not configured.

    Disabled: If you disable this policy setting, the terminal server will try to find a suitable printer driver to install the client printer. If the terminal server does not have a printer driver that matches the client printer, the server will try to use the Terminal Services Easy Print driver to install the client printer. If for any reason the Terminal Services Easy Print driver cannot be used, the client printer will not be available for the Terminal Services session


    • Edited by Dilutiano Thursday, February 16, 2012 1:26 PM
    Thursday, February 16, 2012 1:24 PM
  • Hi,

    Many reasons for this issue. In my experience, probably because there is a bad printer device driver.

    Please install the latest version of the HP printer driver to see whether the issue still exists.

    You can also refer to the following article to troubleshooting step by step:
    Windows Server: Troubleshoot Event ID 6161 — Print Spooler Status
    http://social.technet.microsoft.com/wiki/contents/articles/windows-server-troubleshoot-event-id-6161-print-spooler-status.aspx

    Windows Server 2008 terminal server first tries to use the TS Easy Print driver. If the client computer does not support this driver, the terminal server looks for a matching printer driver installed on the terminal server.

    Using Printer Redirection.
    If you want using Printer Redirection, you must install a matching printer driver on the terminal server and client computer. Then disable the "Use easy print driver first" setting in Terminal server local Group Policy and using printer redirection to test whether the same issue still exists.

    Regards,
    Dollar Wang
    Forum Support
    TechNet Subscriber Support
    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


     

     


    Technology changes life……

    Monday, February 20, 2012 3:04 AM
  • Hi,

    Looking forward to your feedback.


    Technology changes life……

    Wednesday, February 22, 2012 4:11 PM