Event Viewer Error 6161
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads
Event Viewer Error 4201
Remove From My Forums Answered by: Printing error : Event event viewer error 10016 ID 6161: Win32 error code returned by the print processor: 0 Windows Server >
Event Viewer Error 10
Print/Fax Question 0 Sign in to vote Hi, Event Type: Error Event Source: Print Event Category: None Event ID: 6161 Date: 2/1/2011 Time: 10:42:36 event viewer error 55 AM User: domain\XuserX Computer: \\server_name Description: The document R5548001A_LLM05D_920914.PDF owned by XuserX failed to print on printer DBFX3000-01. Data type: NT EMF 1.008. Size of the spool file in bytes: 132788. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. event viewer error 7001 Client machine: \\machine_name. Win32 error code returned by the print processor: 0. The operation completed successfully. I keep receiving above error for the past couple of weeks. It gets resolved once i restarted the print spooler. I tried all suggestions from http://social.technet.microsoft.com/wiki/contents/articles/windows-server-troubleshoot-event-id-6161-print-spooler-status.aspx, none is working, except 'installing new printer driver,,.' because i'd like to understand why restarting print spooler resolve it temporarily if it's indeed because of bad drivers? Adding on, it keeps occuring everytime users trying to print PDF files. Is this related GDI objects limitation? FYI, the print server is running on W2K3 SP2 and printers are FX ApeosPort-II 3000/5010 -amir- Tuesday, February 01, 2011 5:43 AM Reply | Quote Answers 0 Sign in to vote Normally all the tasks that GDI handles on the server will be handled by the client. If you experience failures for a specific drive
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view for all
Event Viewer Error Codes List
logs Free for subscribers Event ID: 6161 Source: Print Source: Print Type: Error event viewer error 36888 Description:The document
Event Viewer Error 10010
file in bytes: 0. Number of bytes printed: 0. Total number of pages in the document: 0. Number of pages printed: 0. Client machine:
Online Backup Virus and Spyware Removal About Our Mission & Our Promise Our History Kevin's Journal IT Consultant Scorecard Clients Contact Article Terminal Services Easy Print "Access is Denied" Event ID 6161 Well, well, well. After about 2.5 hours of hardcore troubleshooting, Googling, and Microsoft Forum browsing, I was http://www.neuroncomputers.com/terminal-services-easy-print-access-is-denied-event-id-6161/ finally able to get Terminal Services Easy Print to print to my Dell printer. Here's my http://www.pcreview.co.uk/threads/event-id-6161-and-6162.1886764/ scenario: TS: Windows Server 2008 Standard, x64 with . NET Framework 3.0 SP1 installed (pre-reqs for Easy Print). Client: Windows Vista Ultimate x64 SP1 with .NET Framework 3.5 and TS Client 6.1 installed (also pre-reqs for Easy Print). Connecting to the Terminal Server showed the redirected printers just fine. I was even able to get into the Printer Preferences and have it show event viewer settings. This part gave me an error message of "Printer settings could not be saved. This operation is not supported", however. Even after doing the fix, it still does it so I'm stuck on having defaults when printing stuff out (NOT GOOD when it comes to QuickBooks check printing). Hopefully I can fix that issue. Print test pages seemed to work as far as clicking on "Print Test Page" and having it say "A test page has been event viewer error sent to the printer…" However, nothing came out of my local printer. Further investigation revealed the following Event Log error ID 6161: "The document Test Page, owned by Administrator, failed to print on printer Dell 3110cn (redirected 2). Try to print the document again, or restart the print spooler. Data type: RAW. Size of the spool file in bytes: 133576. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\SOMA. Win32 error code returned by the print processor: 5. Access is denied." As you can see, it says "Access is denied". I drilled into this issue further and discovered that by going to the Security tab of the redirected printer in question revealed that the user did not even have any permission whatsoever to print to the printer. All the boxes were grayed out and unchecked. So I figured out that it was definitely some kind of permissions issue. Either the TS server was blocking access or my local Vista machine was. Googling upon this turned up an ExpertsExchange discussion on this same issue. The fix? Give write/modify permissions to the Domain Users group on c:\windows\system32\spool folder on the TS server. This got it working and things print out no problem now. Now all I have to do is figure out why I can't edit the printer preferences. "Easy Print"? Yeah right. Leav
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, Jun 22, 2005 #1 Advertisements Guest Guest 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.m