Error 6161 Windows 2003
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove win32 error code returned by the print processor 2250 From My Forums Answered by: Event ID 6161 Windows Server
Win32 Error Code Returned By The Print Processor: 259. No More Data Is Available.
> Print/Fax Question 0 Sign in to vote I have three print servers running Windows
Win32 Error Code Returned By The Print Processor 0x3f
2003 SP2 and have all the latest patches. Each print server has approximately 650 print queues, a couple of GB of RAM and a
Win32 Error Code Returned By The Print Processor 2152796175
dual core Opteron and 15k drives. All third party monitors and print processors are removed. We only use the monitors recommended by Microsoft and the only print processor we use is WINPRINT. Printer drivers are examined before they are installed. We only use drivers from HP and Xerox that use PSCRIPT5.DLL win32 error code returned by the print processor 6 or UNIDRV.DLL.As a result our Windows printing is fairly stable with the exception of the occasional storm of Event ID 6161.As an example: Event Type: ErrorEvent Source: PrintEvent Category: NoneEvent ID: 6161Date: 1/6/2009Time: 11:57:02 AMUser: Domain\usernameComputer: NT008ADescription:The document Microsoft Word - Nurse staff meeting January 2009.doc owned by username failed to print on printer AC6-0241. Data type: NT EMF 1.008. Size of the spool file in bytes: 43368. Number of bytes printed: 36796. Total number of pages in the document: 1. Number of pages printed: 1. Client machine: file://sbezekxp/. Win32 error code returned by the print processor: 0. The operation completed successfully.These are not one or two events but hundreds to thousands that take place all from the same client machine when they happen but not always the same client machine, driver or print queue is involved. After about an hour of one of these events the spooler memory is about 350 to 500MB and there appear to be n
Followers - Follow 5147 Mentions744 Products Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS Windows XP to Windows 7 Windows XP support is coming to an end early in 2014 win32 error code returned by the print processor: 0x0. and we needed to upgrade 13 PC's that currently run Windows XP to run Windows win32 error code returned by the print processor: 122 7 pro on new hardware. Server Migration Upgrading from Server 2003 to Server 2012 and going virtual. Dental Practice - Carrier Dental, PLLC win32 error code returned by the print processor: 2. the system cannot find the file specified. Design, construct, and implement network to support a completely digital Dental practice. TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now I've been getting this Event ID for multiple printers in https://social.technet.microsoft.com/Forums/windows/en-US/ceeb0160-4091-44c2-b2dc-5dadb1117614/event-id-6161?forum=winserverprint 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 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 https://community.spiceworks.com/topic/540499-event-id-6161-on-print-server-running-windows-server-2003 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 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
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to https://www.experts-exchange.com/questions/24964785/Windows-2003-print-server-Getting-Event-ID-6161-for-some-users.html Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live http://www.tomshardware.com/forum/122751-45-event-6161-6162 Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Windows 2003 print server - Getting Event ID 6161 for some users Want to Advertise Here? Solved Windows 2003 print server - Getting Event ID 6161 for some users Posted on 2009-12-09 Printers and Scanners Windows Server 2003 1 Verified Solution 4 Comments 2,782 win32 error Views Last Modified: 2013-12-15 I have a Windows 2003 Standard SP2 print server with 10 HP printers and 2 Ricoh copier/printers. Of the 10 HP printers on this server, 3 are HP Color LaserJet 2600n printers. About 5 users from the office are having problems sending print jobs to these 3 2600n printers. Everybody else is printing fine to them. I am getting 2 different version of the Event ID win32 error code 6161 error messages on the server: Event ID 6161 message 1: The document Microsoft Office Outlook - Memo Style owned by user failed to print on printer Color Office 2. Data type: RAW. Size of the spool file in bytes: 0. Number of bytes printed: 0. Total number of pages in the document: 2. Number of pages printed: 0. Client machine: \\xx.xx.xx.xx. Win32 error code returned by the print processor: 5. Access is denied. Event ID error message #2: The document Microsoft Word - Document1 owned by user2 failed to print on printer Color Office 1. Data type: RAW. Size of the spool file in bytes: 0. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client machine: \\xx.xx.xx.xx. Win32 error code returned by the print processor: 0. The operation completed successfully. Strange thing is that Print Test page prints fine on these printers. However, any other printing fails with one of the above error messages. The other strange thing is that if I log in as the same user on a different computer, the print jobs goes through fine. These are some of the things that I have already tried: Restart the spooler service (print server and local computer) Chan
Gaming Smartphones Tablets Windows 8 PSUs Android Your question Get the answer Tom's Hardware>Forum>Windows XP>Event ID 6161 and 6162> Event ID 6161 and 6162 Tags: Event Id Windows XP Last response: 30 June 2005 00:54 in Windows XP Share Anonymous 22 June 2005 21:08:03 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. More about : event 6161 6162 Byte 22 June 2005 23:05:03 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