Printer Error Event Id 6161
Contents |
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions TechNet Video TechNet Wiki win32 error code returned by the print processor 2250 Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter Security Virtualization Downloads Updates event id 372 Service Packs Security Bulletins Windows Update Trials Windows Server 2016 System Center 2016 Windows 10 Enterprise SQL Server 2016 See event id 842 all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses
Win32 Error Code Returned By The Print Processor 259 No More Data Is Available
Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online win32 error code returned by the print processor 2152796175 TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Print Server Print Spooler Service Print Spooler Status Print Spooler Status Event ID 6161 Event ID 6161 Event ID 6161 Event ID 15 Event ID 16 Event ID 23 Event ID 53 Event ID 58 Event ID 66 Event ID 67 Event ID 68 Event ID 71 Event ID 73 Event ID 74 Event ID 75 Event ID 6161 Event ID 6162 TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Event ID 6161 — Print Spooler Status Updated: November 30, 2007Applies To: Windows Server 2008 Print Server Status controls basic operations such as initializing the spooler, creating threads, and reading the registry. Event Details Product: Windows Operating System ID: 6161 Source: Microsoft-Windows-PrintSpooler Version: 6.0 Symbolic Name: MSG_PRINT_ON_PROC_FAILED_EX Message: The document %1, owned by %2, failed to pr
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common win32 error code returned by the print processor 6 to see an entire company using just one server, these days that's no longer the
Win32 Error Code Returned By The Print Processor 0x3f
case. New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an
Win32 Error Code Returned By The Print Processor 0 The Operation Completed Successfully
eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" https://technet.microsoft.com/en-us/library/cc773865(v=ws.10).aspx are blinking on any of the servers. read more... Event ID: 6161 Source: Print Source: Print Type: Error Description:The document
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 http://www.neuroncomputers.com/terminal-services-easy-print-access-is-denied-event-id-6161/ browsing, I was finally able to get Terminal Services Easy Print to print to my Dell printer. Here's my scenario: TS: Windows Server 2008 Standard, x64 with . NET Framework 3.0 SP1 installed (pre-reqs for Easy Print). Client: https://community.spiceworks.com/topic/163203-event-id-6161-no-printers-work-in-term-service 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 win32 error 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 pages seemed to work as far as clicking on "Print Test win32 error code 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 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.
Technical Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS Netwrix AD auditing to the rescue . . . Using Netwrix Adctive Directory Auditing to keep the SOX Auditors happy . . .And oh, a few small tips . . . New Client Install 2 x Servers, 27 x Desktops & Laptops. Replaced all WIFI repeaters with Ubiquiti UniFi equipment. HomeLab HomeLab 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 Ben8845 Oct 19, 2011 at 10:05 UTC well i deleted my profile on the TS server and logged back in. it created a new profile for me but the print problem is unchanged. 0 Sonora OP Best Answer Ben8845 Oct 19, 2011 at 1:46 UTC well we found the answer. http://www.windowsitpro.com/forums/aft/38563 the last comment on there gives the fix. While this may be late...the answer (once you find it) is simple. hklm\system\controlSet001\control\DeviceClasses\{28d78fad-5a1