How to identify an application sending improperly generated EMF files to a Windows 2003 print server?
Windows XP users who are utilizing our Windows 2003 print server will lose printing functionality until the print spooler is restarted on the print server. I know you say then this question should be in a forum for Windows 2003 server, but this appears to be related to a GDI leak from an application running on Windows XP. How can I identify the offending application easily? We receive numerous 6161 and 6162 events in the event viewer. When researching this problem, I found this post by Alan Morris (from Microsoft): http://www.pcreview.co.uk/forums/thread-1886764-1.php wherein he references opening task manager and printing from each of your common applications and watching the GDI count to see if it goes up after printing from each application. However, I'm in an environment with too many applications to test so it would be very difficult to identify which application is sending the improperly generated EMF file to the print server. Also, even if I could identify the application, what information should be given to the owner/programmer of the application to help them resolve their problem? I'm guessing if I just tell them their application is sending improperly generated EMF files to our print server, they're going to look at me with a blank stare. I guess I'd like further information from Alan Morris who I see frequents this site. Alan, are you there? 1 person needs an answerI do too
March 24th, 2010 7:10pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics