Printer Error Id 6161
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Printing error : win32 error code returned by the print processor 2250. this network connection does not exist Event ID 6161: Win32 error code returned by the print processor:
Event Id 372
0 Windows Server > Print/Fax Question 0 Sign in to vote Hi, Event Type: Error Event Source: event id 842 Print Event Category: None Event ID: 6161 Date: 2/1/2011 Time: 10:42:36 AM User: domain\XuserX Computer: \\server_name Description: The document R5548001A_LLM05D_920914.PDF owned by XuserX failed to print on printer DBFX3000-01.
Win32 Error Code Returned By The Print Processor 259 No More Data Is Available
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. 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 win32 error code returned by the print processor 2152796175 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 driver most likely a piece of the driver is not downloaded to the client. You can enable this again or attempt to get all the parts of the print driver installed on the client. I suggest just enabling GDI on the server for the drivers that show a problem with this configuration. Whe
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,
Win32 Error Code Returned By The Print Processor 6
Googling, and Microsoft Forum browsing, I was finally able to get Terminal Services Easy
Win32 Error Code Returned By The Print Processor 0x3f
Print to print to my Dell printer. Here's my scenario: TS: Windows Server 2008 Standard, x64 with . NET Framework 3.0 SP1 win32 error code returned by the print processor 0 the operation completed successfully 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 https://social.technet.microsoft.com/Forums/windows/en-US/027853aa-30d5-4e81-8793-015d72d374b9/printing-error-event-id-6161-win32-error-code-returned-by-the-print-processor-0?forum=winserverprint fine. I was even able to get into the Printer Preferences and have it show 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 http://www.neuroncomputers.com/terminal-services-easy-print-access-is-denied-event-id-6161/ pages seemed to work as far as clicking on "Print Test Page" and having it say "A test page has been 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
and http://www.chicagotech.net/troubleshooting/eventid6161.htm network print drivers to the Terminal Server session with Event https://community.spiceworks.com/topic/163203-event-id-6161-no-printers-work-in-term-service ID 6161. Source: Microsoft-Windows-PrintSpooler Event ID: 6161 Description: on printer PRINTERNAME on CLIENTName (redirected #). Try to print the document again, or restart the print spooler. Data type: RAW. Size of the spool file in bytes: 135564. Number of bytes printed: win32 error 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\ServerName. Win32 error code returned by the print processor: 5. Access is denied. You might notice that the XPS file is being sent back over to the client. You might see it spool on win32 error code the server then disappear or the job never gets back to the client. You could also be going thru a Terminal Services Web Gateway Server. Troubleshooting: the client installed Terminal Services on a Domain Controller, which is not recommended. For many small business, they don't have choice, the resolution is using cacls command to assign permission to spool by following these steps: 1. Click Start, search for cmd.exe 2. Right click on cmd.exe 3. Click on 'Run as Administrator' 4. Type "C:\" w/o the quotation marks and then Press Enter. 5. Type CD\Windows\System32\Spool and then Press Enter. 6. Type Cacls.exe PRINTERS /e /g users:C and then Press Enter. 7. Restart the computer Post your questions, comments, feedbacks and suggestions Contact a consultant Related Topics This web is provided "AS IS" with no warranties. Copyright 2002-2015 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.
Products Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS Windows 7 Migration Migrate workstations from Windows XP to Windows 7. Better Remote Access How to give Remote access to over 40 user, over a WAN, from unconnected Domains. Windows 7 Migration Upgrading approximately 150 workstations from Windows XP to Windows 7 Professional. TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now i have a windows 2003 server. it has all current updates installed. yester day we setup roaming profiles and since then we can not print in terminal services to any printer. as soon as you start a print job it errors and we get the following error in event viewer. The document Test Page owned by administrator failed to print on printer HP LaserJet 4 Plus (from *****) in session 3. Data type: NT EMF 1.008. Size of the spool file in bytes: 74852. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client machine: \\*******. Win32 error code returned by the print processor: 3. The system cannot find the path specified. i have been looking into this for 2 days now and have tried just about everything...... Reply Subscribe View Best Answer RELATED TOPICS: event id 3009 List of Event ID Standard Shutdown Event ID   4 Replies Thai Pepper OP Stephen5797 Oct 19, 2011 at 9:19 UTC Sounds like corrupt profiles(s). Try deleting one or a few user profiles from the Terminal Server, have them log back in, re-set up their printer and then see if you get the same error. 0 Sonora OP Ben8845 Oct 19, 2011 at 9:48 UTC i will give that a try. also i would like to add that its only the redirected printers that dont work. i did more checking and found that if i set the printer up directly on the server it works but the ones that have TS virtual ports dont. 0 Sonora OP