Installing Printer Driver - Failed Error Code 0x2
Contents |
in: Andy Barendregt Add comments Last week we had a print spooler problem on a XenApp 7.6/Server 2012R2 farm. The print spooler service grew to a whopping 16GB of Memory.
Error Code 0x3 Hresult 0x80070057
The problem was related to a mix of old Ricoh and Kyocera installing printer driver failed error code 0x3 drivers. After upgrading to new drivers the problem of the spooler was resolved. But on one machine the Ricoh
Spooler Operation Failed Event Id 215
Universal Print driver could not be installed. We received the following error: Installing printer driver - failed, error code 0x57, HRESULT 0x80070057. See the event user data for context information. Installing event id 215 installing a printer driver printer driver - failed, error code 0x57, HRESULT 0x80070057. See the event user data for context information. Deleting all drivers from the printer server properties did not resolve the problem. We also tried to fix it the old fashioned way, copying the folder "C:\Windows\System32\spool\drivers\x64\3" and the registry keys from a working server, but that worked neither. So next is to check up the isinfindriverstore failed Driverstore for old installations. - Open a command line window as an Administrator - Run the command: pnputil -e. This command will list all the .inf files listed in the DriverStore, take note of all the .inf files where the manufacturer name is that of the printer affected. For sure the Class must be Printers. For Example in this case: Published name : oem40.inf Driver package provider : Ricoh Class : Printers Driver date and version : 06/15/2015 4.7.0.0 Signer name : Microsoft Windows Hardware Compatibility Publisher Oem40.inf is the same as Oemsetup.inf of the Ricoh Universal Driver but renamed by the operating system. Although all drivers are deleted from the print server properties, the Ricoh driver was still in the Driverstore repository. Resolution in this case: - Delete all the Rico inf files using the command: pnputil -f -d oemxx.inf, xx should be replaced by the value displayed by the pnputil –e command. In this case: pnputil –f –d oem40.inf After that, the installation of the driver was working as it should be. Andy BarendregtMore Posts Comments are closed. Links PepperByte Crew Members Andy Barendregt (
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about
Pfnpsetupparseinfandcommitfilequeue Failed
hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question hresult 0x80070705 _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up
Configure The Point And Print Restrictions Policy To Disabled.
Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Server 2008 R2 - Unable to install any printer drivers up vote 5 down vote favorite 3 http://www.peppercrew.nl/index.php/2015/10/installing-printer-driver-failed-error-code-0x2-hresult-0x80070057/ My problem is exactly this same as described here: Server 2008 R2 - Unable to install any printer drivers Options - google groups I have few Windows 2008 R2 (no SP1) servers in remote offices, mostly in Domain Controller, and many of them have problems installing ANY printer drivers. following errors show up in Event Log when adding printer driver under Print and Document Services/Print Management/Print Services/ /Drivers OR trying any other way to install drivers: EventID 215: Installing http://serverfault.com/questions/272636/server-2008-r2-unable-to-install-any-printer-drivers printer driver - failed, error code 0x57, HRESULT 0x80070057. See the event user data for context information. EventID 215: Installing printer driver Canon iR C2380/2550 PCL6 failed, error code 0x0, HRESULT 0x80070057. See the event user data for context information. EventID 215: Installing printer driver Canon iR C2380/2550 PCL6 failed, error code 0x490, HRESULT 0x80070057. See the event user data for context information. in this particular server case this is problem with Canon iRC 2380i printer with Canon Generic PCL6 Driver, but it seems to apply to any driver and any printer (tried different drivers, different versions, PCL, postscript, etc) I'm using 64 bit drivers that should be working on this platform. Any help will be appreciated. windows-server-2008 windows-server-2008-r2 printing drivers shared-printers share|improve this question edited May 23 '11 at 8:20 Kev 5,324125894 asked May 23 '11 at 8:08 toffitomek 911212 Work still in progress, but I think I've found workaround - normally I've been using admin user, member of Domain Admin (created like 10 years ago). Then I've used another account (also member of DA) and all works fine! Checked GPO resolution for both users and is completely different, so I believe some old GPO settings are problem here. Still to investigate in details... –toffitomek Jun 1 '11 at 10:40 One more thing is happening, when finally managed to install driver with different user, then sharing is failing :/ –to
Services server in a farm running Windows Server 2008 R2 SP1. Suddenly some users reported that they didn't get their printer(s) mapped when they logged in to that http://www.eversity.nl/blog/page/2/ specific RDS server.While other users did not get all of their printers and some users logged in on the same server had no problem at all and could print to their preferred printer. While analyzing this problem, we found out that the printers which didn't got connected used the same printer drivers.Printers using the Xerox Global Printer Driver or HP Universal Printer Driver were not available on this printer driver RDS server, while printers using a Konica Minolta driver for example connected without a problem. When connecting to a network printer using the Xerox Global Printer Driver of HP UPD manually, the following error was shown: Windows cannot connect to the printer. Operation failed with error 0x00000002. At the same time, the following 2 events are logged installing printer driver in 2 different eventlogs: Log Name: Microsoft-Windows-PrintService/AdminSource: Microsoft-Windows-PrintServiceDate: 20-9-2012 13:43:40Event ID: 215Task Category: Installing a printer driverLevel: ErrorKeywords: Printer Setup,PrinterUser: SYSTEMComputer: