Event ID 6161 & 6162

[Jeff]

Can somone please tell me how to fix this? Restarting the print spooler
works temporarily but I need a fix. Thanks!

 

[Alan Morris [MSFT]]

when you hit 6162 you have an application that is sending improperly
generated EMF files to the print server which leaks GDI handles in the
process. The GDI handle limit is 10000. When the spooler hits this limit
all calls to GDI for rendering the print jobs will fail (happily you will
notice in 6161 events GDI returns success for these failures).

You need to track down the application. It's easiest to do this on the
client side since the application will leak the same GDI handles when
creating the print job.

On the print server open task manager. One has to do this at the machine or
in a TS console session. Go to processes, change the view to include GDI
handles. Find spoolsv.exe and keep track of the GDI handles. When it
approaches the 10000 limit you will need to restart the spooler.

On the client start loading common applications for your work place.

Task manager will help on the client side as well. Include GDI handles.
Launch the application, find the process in task manager, print a ten page
doc. If the GDI handle count goes up 10, you have the culprit. So the
application you are looking for is one that will corporate wide send 10000
pages (not jobs) in your failure time window.




--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Alan Morris [MSFT]]

By the way, be patient on this since it can drive you nuts. Get back to me
and let me know how this is going. I would also like the application name
just for reference. If you work for a Vet hospital or print a lot of faxes,
I know the applications.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

when you hit 6162 you have an application that is sending improperly
generated EMF files to the print server which leaks GDI handles in the
process. The GDI handle limit is 10000. When the spooler hits this limit
all calls to GDI for rendering the print jobs will fail (happily you will
notice in 6161 events GDI returns success for these failures).

You need to track down the application. It's easiest to do this on the
client side since the application will leak the same GDI handles when
creating the print job.

On the print server open task manager. One has to do this at the machine
or
in a TS console session. Go to processes, change the view to include GDI
handles. Find spoolsv.exe and keep track of the GDI handles. When it
approaches the 10000 limit you will need to restart the spooler.

On the client start loading common applications for your work place.

Task manager will help on the client side as well. Include GDI handles.
Launch the application, find the process in task manager, print a ten page
doc. If the GDI handle count goes up 10, you have the culprit. So the
application you are looking for is one that will corporate wide send 10000
pages (not jobs) in your failure time window.




--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no
rights.

Can somone please tell me how to fix this? Restarting the print spooler
works temporarily but I need a fix. Thanks!

 

[Alan Morris [MSFT]]

Any progress on this? I'd love to know the application name.

thanks

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.