Microsoft-windows-printservice Error 372
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 event id 372 printservice access denied TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and
Event Id 372 Access Is Denied
Datacenter Security Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2016 System Center 2016 Windows
Win32 Error Code Returned By The Print Processor: 2147500037. Unspecified Error
10 Enterprise SQL Server 2016 See 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
Win32 Error Code Returned By The Print Processor: 1726. The Remote Procedure Call Failed.
Microsoft Virtual Academy Free Windows Server 2012 courses 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 win32 error code returned by the print processor 122 IT professionals For technical support Support offerings More support Microsoft Premier Online 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. Printing Infrastructure Print Spooler Service Print Spooler Status Print Spooler Status Event ID 372 Event ID 372 Event ID 372 Event ID 99 Event ID 312 Event ID 313 Event ID 319 Event ID 349 Event ID 354 Event ID 361 Event ID 362 Event ID 363 Event ID 366 Event ID 368 Event ID 369 Event ID 370 Event ID 372 Event ID 373 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 372 — Print Spooler Status Updated: January 8, 2008Applies To: Windows Server 2008 R2 This is preliminary documentation and subject to change. Print Server Status controls basic op
can print from my laptop over wireless without needing to turn on the desktop PC that the printer was originally connected to. It didn’t work: win32 error code returned by the print processor: 2152796175. Windows correctly installed the printer drivers, and added the printer as the default event id 372 terminal server device, but whenever I attempted to print anything (even locally), nothing came out, but no error messages were displayed. win32 error code returned by the print processor: 2. the system cannot find the file specified. In order to track down the problem, I tried printing using the XPS driver. That didn’t work either: the print job was reported as successful, but I ended up with zero-byte .OXPS files. https://technet.microsoft.com/en-us/library/dd393167(v=ws.10).aspx Eventually, I looked in Event Viewer and found this: Log Name: Microsoft-Windows-PrintService/Admin Source: Microsoft-Windows-PrintService Date: 15/04/2013 19:06:39 Event ID: 372 Task Category: Printing a document Level: Error Keywords: Classic Spooler Event,Document Print Job User: HOME\Administrator Computer: SERVER.home.differentpla.net Description: The document Print Document, owned by Administrator, failed to print on printer Microsoft XPS Document Writer. Try to print the document again or restart the print spooler. Data http://blog.differentpla.net/blog/2013/04/27/the-case-of-the-missing-print-jobs type: RAW. Size of the spool file in bytes: 67709. Number of bytes printed: 0. Total number of pages in the document: 2. Number of pages printed: 0. Client computer: \\SERVER. Win32 error code returned by the print processor: 5. Access is denied. I searched the Internet for this particular Event ID, and for the error message. Almost everything was talking about printing from Terminal Services, which was not my problem, because I was trying to print locally. In the end, I found a KB article, which suggests giving Everyone permission on the PRINTERS folder. There’s no way that I’m doing that, so I looked around some more, and found something that mentioned using Process Monitor and looking at the spoolsv.exe process. That didn’t show anything interesting, but it did lead me to filtering on the PRINTERS folder. Instead of spoolsv.exe, I found a process named printfilterpipelinesvc.exe, which was getting ACCESS DENIED while attempting to create a .TMP file in the PRINTERS folder. Looking at the properties for that entry, we find that printfilterpipelinesvc.exe is running as LOCAL SERVICE. So, I just gave LOCAL SERVICE full control over the PRINTERS folder, and everything started working.
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 https://www.experts-exchange.com/questions/25994644/Print-Spooler-Hangs-on-Windows-7-with-Event-ID-372-RPC-error.html to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs https://community.spiceworks.com/topic/593568-event-id-372-and-printing Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Print Spooler Hangs on Windows 7 with Event ID 372 - RPC error Want to Advertise Here? Solved Print Spooler Hangs on Windows 7 with Event ID 372 - RPC error Posted on 2010-04-21 Windows 7 Windows Server 2003 1 Verified win32 error Solution 38 Comments 7,778 Views Last Modified: 2012-05-09 The network configuration is: Windows SBS 2003 server with Windows 7 32-bit clients. There are other servers on the network, but the SBS server is acting as the print server. Periodically various workstations will be unable to print to any printer. The print spooler service appears to be running normally, but the event log shows the following error message: Log Name: win32 error code Microsoft-Windows-PrintService/Admin Source: Microsoft-Windows-PrintService Date: 4/21/2010 12:09:57 PM Event ID: 372 Task Category: Printing a document Level: Error Keywords: Classic Spooler Event,Document Print Job User: WSPLAW\JStartz Computer: WSP53.WallerSmithPalmer.local Description: The document Local Downlevel Document, owned by jstartz, failed to print on printer {88F50B3B-808D-4015-9C4B-F
SPONSORED BY MICROSOFT See more RELATED PROJECTS SCCM 2012 R2 Upgrade Flawless upgrade was completed after many hours of planning Corporate Infrastructure Redesign Upgrade existing Active Directory domain from 2003 to 2008R2, install larger storage servers, utilize virtualization w/ SAN, install backup system, implement network security, ASA firewalls and VLANs. P2V Conversion of all Servers Move physical servers: RedHat EL5, 2x Windows Servers (1 MSSQL, 1 Pervasive SQL), 2x Windows workstations running proprietary Scheduling Software, 1x Unbuntu Server for Calendar Server. TECHNOLOGY IN THIS DISCUSSION Microsoft Windows Server 2012 Join the Community! Creating your account only takes a few minutes. Join Now I have been troubleshooting printer this week and while one would think print servers is a fairly easy concept, this has been a thorn in my side over the past week. I recently upgraded my domain from 2003 to 2012 and moved all of my printers over to the 2012 DC. Most of my printers are HP and by default when I loaded them on the print server they defaulted to using the user mode 4 drivers. I started experiencing various issues on client machines so I installed the universal pcl6 print driver and it now defaults to the user mode 3 driver. I have a mix of clients that print fine now and others that everything appears to print but it never makes it the print server. After further investigation, I am receiving event id 372 on these client machines basically stating that access is denied. This pointed me to a technet article, http://technet.microsoft.com/en-us/library/dd393167(v=ws.10).aspx, which suggests it could be a bad driver load. I followed the section on moving the drivers under the spool folder to a new location and then restarting the print spool service. This in fact resolves my issue but it requires me to move all of the drivers on the problematic clients and then manually i