Error Event Id 6161 Source Print
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 : Event ID 6161: Win32 error code returned by the print
Win32 Error Code Returned By The Print Processor: 259. No More Data Is Available.
processor: 0 Windows Server > Print/Fax Question 0 Sign in to vote Hi, Event Type: Error Event
Event Id 372
Source: 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
Event Id 842
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. Client machine: \\machine_name. Win32 error code returned by the print processor: 0. The operation completed successfully. I keep receiving above error for the win32 error code returned by the print processor 0x3f 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 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 sho
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 win32 error code returned by the print processor 2152796175 years ago it was still common to see an entire company using just one win32 error code returned by the print processor 6 server, these days that's no longer the case. New computers are added to the network with the understanding that they will win32 error code returned by the print processor: 122 be taken care of by the admins. Keeping an 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 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 hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 6161 Source: Print Source: Print Type: Error Description:The document
Follow 5147 Mentions744 Products Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating https://community.spiceworks.com/topic/540499-event-id-6161-on-print-server-running-windows-server-2003 your account only takes a few minutes. Join Now I've been getting this Event ID for multiple printers in our office. I am not sure what to do as there is no definitive answer since there are so many variables. Was curious if anyone has dealt with this? If so, how do I go about fixing it? I am running Windows Server 2003 x64 win32 error Event Type: Error Event Source: Print Event Category: None Event ID: 6161 Date: 7/14/2014 Time: 5:33:31 PM Description: The document %1 owned by %2 failed to print on printer %3. Data type: IMF. Size of the spool file in bytes: 640348. Number of bytes printed: 131076. Total number of pages in the document: 3. Number of pages printed: 0. Client machine: \\192.168.1.39. Win32 error code win32 error code returned by the print processor: 5. Access is denied. Reply Subscribe RELATED TOPICS: gettin event id 40960 only on windows server 2003. Windows Server 2003 Event ID 333 There will be stragglers after the Windows Server 2003 end of life – here's why   5 Replies Pure Capsaicin OP Rob Dunn Jul 16, 2014 at 3:54 UTC Could be a permissions issue - possibly to this folder: system32/spools/printers on the print server. 1 Poblano OP Todd5015 Jul 16, 2014 at 4:41 UTC This almost looks like your server is getting low on storage. Your spooler is by default stored on drive C on your server. You can move the spooler to a different drive on your 2003 server by doing this: On the drive with lots of room, make a folder and sub-folders that looks like d:\Windows\system32\spools\printers Click on START, and PRINTERS AND FAXES. In the PRINTERS AND FAXES window, right click anywhere in the white space (not on an icon) and choose SERVER PROPERTIES. In SERVER PROPERTIES, click on the ADVANCED tab. The first field is Spool Folder. Change this to