Event ID 6161 and 6162

[Guest]

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

I am having a problem with one of our Xerox network printers. None of our
users can print to it. I do not see anything show up in the print queue.

These are the events we are seeing in our Event Viewer.

Event Type: Error
Event Source: Print
Event Category: None
Event ID: 6161
Date: 6/22/2005
Time: 8:24:05 AM
User: DIRECTCORP\PaulKeefer
Computer: DATADEVA
Description:
The document Microsoft Office Outlook - Memo Style owned by PaulKeefer
failed to print on printer Xerox Document Centre 332. Data type: NT EMF
1.008. Size of the spool file in bytes: 65536. Number of bytes printed: 0.
Total number of pages in the document: 1. Number of pages printed: 0. Client
machine: \\192.168.0.152. Win32 error code returned by the print processor:
0. The operation completed successfully.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Print
Event Category: None
Event ID: 6162
Date: 6/22/2005
Time: 8:17:02 AM
User: NT AUTHORITY\SYSTEM
Computer: DATADEVA
Description:
The spooler has detected that a component has an unusually large number of
open GDI objects. As a result some EMF print jobs might not print until the
spooler is restarted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

 

[Byte]

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Are you using the latest Xerox drivers compatible with XP?
--
Some days you're the windshield,
some days you're the bug.


"-Nick" wrote:

> I am having a problem with one of our Xerox network printers. None of our
> users can print to it. I do not see anything show up in the print queue.
>
> These are the events we are seeing in our Event Viewer.
>
> Event Type: Error
> Event Source: Print
> Event Category: None
> Event ID: 6161
> Date: 6/22/2005
> Time: 8:24:05 AM
> User: DIRECTCORP\PaulKeefer
> Computer: DATADEVA
> Description:
> The document Microsoft Office Outlook - Memo Style owned by PaulKeefer
> failed to print on printer Xerox Document Centre 332. Data type: NT EMF
> 1.008. Size of the spool file in bytes: 65536. Number of bytes printed: 0.
> Total number of pages in the document: 1. Number of pages printed: 0. Client
> machine: \\192.168.0.152. Win32 error code returned by the print processor:
> 0. The operation completed successfully.
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> Event Type: Error
> Event Source: Print
> Event Category: None
> Event ID: 6162
> Date: 6/22/2005
> Time: 8:17:02 AM
> User: NT AUTHORITY\SYSTEM
> Computer: DATADEVA
> Description:
> The spooler has detected that a component has an unusually large number of
> open GDI objects. As a result some EMF print jobs might not print until the
> spooler is restarted.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Yes I am.. I fixed the problem anyway. I restarted the print spooler
service and it solved the issue.

"Byte" wrote:

> Are you using the latest Xerox drivers compatible with XP?
> --
> Some days you're the windshield,
> some days you're the bug.
>
>
> "-Nick" wrote:
>
> > I am having a problem with one of our Xerox network printers. None of our
> > users can print to it. I do not see anything show up in the print queue.
> >
> > These are the events we are seeing in our Event Viewer.
> >
> > Event Type: Error
> > Event Source: Print
> > Event Category: None
> > Event ID: 6161
> > Date: 6/22/2005
> > Time: 8:24:05 AM
> > User: DIRECTCORP\PaulKeefer
> > Computer: DATADEVA
> > Description:
> > The document Microsoft Office Outlook - Memo Style owned by PaulKeefer
> > failed to print on printer Xerox Document Centre 332. Data type: NT EMF
> > 1.008. Size of the spool file in bytes: 65536. Number of bytes printed: 0.
> > Total number of pages in the document: 1. Number of pages printed: 0. Client
> > machine: \\192.168.0.152. Win32 error code returned by the print processor:
> > 0. The operation completed successfully.
> >
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > Event Type: Error
> > Event Source: Print
> > Event Category: None
> > Event ID: 6162
> > Date: 6/22/2005
> > Time: 8:17:02 AM
> > User: NT AUTHORITY\SYSTEM
> > Computer: DATADEVA
> > Description:
> > The spooler has detected that a component has an unusually large number of
> > open GDI objects. As a result some EMF print jobs might not print until the
> > spooler is restarted.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >

 

[Byte]

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Simple.......wasn't it?
--
Some days you're the windshield,
some days you're the bug.


"-Nick" wrote:

> Yes I am.. I fixed the problem anyway. I restarted the print spooler
> service and it solved the issue.
>
> "Byte" wrote:
>
> > Are you using the latest Xerox drivers compatible with XP?
> > --
> > Some days you're the windshield,
> > some days you're the bug.
> >
> >
> > "-Nick" wrote:
> >
> > > I am having a problem with one of our Xerox network printers. None of our
> > > users can print to it. I do not see anything show up in the print queue.
> > >
> > > These are the events we are seeing in our Event Viewer.
> > >
> > > Event Type: Error
> > > Event Source: Print
> > > Event Category: None
> > > Event ID: 6161
> > > Date: 6/22/2005
> > > Time: 8:24:05 AM
> > > User: DIRECTCORP\PaulKeefer
> > > Computer: DATADEVA
> > > Description:
> > > The document Microsoft Office Outlook - Memo Style owned by PaulKeefer
> > > failed to print on printer Xerox Document Centre 332. Data type: NT EMF
> > > 1.008. Size of the spool file in bytes: 65536. Number of bytes printed: 0.
> > > Total number of pages in the document: 1. Number of pages printed: 0. Client
> > > machine: \\192.168.0.152. Win32 error code returned by the print processor:
> > > 0. The operation completed successfully.
> > >
> > >
> > > For more information, see Help and Support Center at
> > > http://go.microsoft.com/fwlink/events.asp.
> > >
> > >
> > > Event Type: Error
> > > Event Source: Print
> > > Event Category: None
> > > Event ID: 6162
> > > Date: 6/22/2005
> > > Time: 8:17:02 AM
> > > User: NT AUTHORITY\SYSTEM
> > > Computer: DATADEVA
> > > Description:
> > > The spooler has detected that a component has an unusually large number of
> > > open GDI objects. As a result some EMF print jobs might not print until the
> > > spooler is restarted.
> > >
> > > For more information, see Help and Support Center at
> > > http://go.microsoft.com/fwlink/events.asp.
> > >

 

[Guest]

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Not that simple as this problem will return. We added the 6162 error in
Server 2003 SP1 to detect when applications improperly generate EMF files
and leak GDI handles as a result.

Log in to the console session and launch task manager. Processes Tab, View
Select Columns..., enable GDI Objects. Find the spoolsv.exe process and
note the number of GDI objects. Monitor this value over several days. The
system defaults to 10000 in any one process. When this limit is reached GDI
can no longer allocate resources to render the print job and generates a
bogus success error 0. When GDI does this, the spooler will now check if
the objects that GDI owns has reached the defined limit and generates event
6162.



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

"Byte" <Byte@discussions.microsoft.com> wrote in message
news:1677F35D-04E2-46DB-AB70-591065E4F961@microsoft.com...
> Simple.......wasn't it?
> --
> Some days you're the windshield,
> some days you're the bug.
>
>
> "-Nick" wrote:
>
> > Yes I am.. I fixed the problem anyway. I restarted the print spooler
> > service and it solved the issue.
> >
> > "Byte" wrote:
> >
> > > Are you using the latest Xerox drivers compatible with XP?
> > > --
> > > Some days you're the windshield,
> > > some days you're the bug.
> > >
> > >
> > > "-Nick" wrote:
> > >
> > > > I am having a problem with one of our Xerox network printers. None
of our
> > > > users can print to it. I do not see anything show up in the print
queue.
> > > >
> > > > These are the events we are seeing in our Event Viewer.
> > > >
> > > > Event Type: Error
> > > > Event Source: Print
> > > > Event Category: None
> > > > Event ID: 6161
> > > > Date: 6/22/2005
> > > > Time: 8:24:05 AM
> > > > User: DIRECTCORP\PaulKeefer
> > > > Computer: DATADEVA
> > > > Description:
> > > > The document Microsoft Office Outlook - Memo Style owned by
PaulKeefer
> > > > failed to print on printer Xerox Document Centre 332. Data type: NT
EMF
> > > > 1.008. Size of the spool file in bytes: 65536. Number of bytes
printed: 0.
> > > > Total number of pages in the document: 1. Number of pages printed:
0. Client
> > > > machine: \\192.168.0.152. Win32 error code returned by the print
processor:
> > > > 0. The operation completed successfully.
> > > >
> > > >
> > > > For more information, see Help and Support Center at
> > > > http://go.microsoft.com/fwlink/events.asp.
> > > >
> > > >
> > > > Event Type: Error
> > > > Event Source: Print
> > > > Event Category: None
> > > > Event ID: 6162
> > > > Date: 6/22/2005
> > > > Time: 8:17:02 AM
> > > > User: NT AUTHORITY\SYSTEM
> > > > Computer: DATADEVA
> > > > Description:
> > > > The spooler has detected that a component has an unusually large
number of
> > > > open GDI objects. As a result some EMF print jobs might not print
until the
> > > > spooler is restarted.
> > > >
> > > > For more information, see Help and Support Center at
> > > > http://go.microsoft.com/fwlink/events.asp.
> > > >