Windows Cannot Connect to the Printer Error 0x00000057

Windows Cannot Connect to the Printer Error 0x00000057

34 Replies

  • I have seen this with a 2003R2 (32bit) print server and a user with a Win 7 (x64).  The just workaround I accept found so far is to manually install the printer on the PC.


    Was this postal service helpful?
    thumb_up
    thumb_down

  • I tried to manually install the printer also. merely it fails at the step where it attempts to install the driver


    Was this post helpful?
    thumb_up
    thumb_down


  • Windows Cannot Connect to the Printer Error 0x00000057

  • I saw that, but when I look their is no directory on the problem car at all (at least not in the same location equally a working machine)


    Was this post helpful?
    thumb_up
    thumb_down

  • DNS resolving for the host name and IP?  Whatsoever IP conflicts for that accost?


    Was this mail helpful?
    thumb_up
    thumb_down

  • no IP conflict. and I don’t utilise DNS for the printers. the print server DNS is fine.

    I have l other machines working fine it only appears to be this one desktop at the moment


    Was this mail helpful?
    thumb_up
    thumb_down

  • Might exist a impress driver problem on the server vs. the computer.


    Was this postal service helpful?
    thumb_up
    thumb_down

  • Try to stop the spooler service on that desktop.  and then remove all traces of that driver on the printer server properties (and driver packet).  Then run a file and reg cleaner like glary or ccleaner (or both).  Reboot and attempt to manually add the driver from the impress server.


    Was this post helpful?
    thumb_up
    thumb_down

  • and so it should impact my other clients also and not only i client


    Was this post helpful?
    thumb_up
    thumb_down


  • Michael7953

  • Maybe the EventViewer could exist of some help


    Was this post helpful?
    thumb_up
    thumb_down

  • Maybe the EventViewer could be of some help

    tried that road. information technology isn’t logging anything into the event viewer. I even tried clearing out all the logs then adding a printer so I would only accept to sort a few events. simply nothing for this issue shows 🙁

    ccleaner is a good idea. I never thought to try that


    Was this post helpful?
    thumb_up
    thumb_down

  • I’m assuming that the printer and computer are on the aforementioned network/subnet?

    Other users can print to that printer?
    Tin you lot print a examination page from the print server?


    Was this post helpful?
    thumb_up
    thumb_down

  • RoyL wrote:

    have you seen this post on technet?

    http://social.technet.microsoft.com/Forums/en-US/itmanager/thread/a225d71c-be8b-4530-bf50-63001559a978

    So this ended up existence the solution later on all. thanks for this. I ended upwardly copying the directory from a working machine and placing it onto the busted machine and now I tin install the printer! I guess in my frustration I passed over this article to quickly.

    Thank you for the help


    Was this postal service helpful?
    thumb_up
    thumb_down

  • hither is a summary of the solution from the link in a higher place

    It’southward actually the print commuter failing to install, non the connectedness to the print server.  An initial attempt to install the commuter failed, then the driver directory is present on the workstation, only missing the files.

    1)  On a car with the aforementioned driver installed (and working properly), open Regedit, and browse to:
    HKLM\System\CurrentControlSet\Command\Print\Environments\Windows NT x86\Drivers\Version-3\
    two)  Locate the subkey for the printer driver you are dealing with and click the key for the printer driver.
    3)  Look for the “InfPath” on the right.  Note the path.
    5)  At present browse to C:\Windows\System32\DriverStore\FileRepository and locate the folder indicated in the InfPath reg value.
    half dozen)  Go to the users computer exhibiting this beliefs, and browse to C:\Windows\System32\DriverStore\FileRepository and see if the folder is nowadays.  In my case, the folder was present, but empty.  If it is here and it is empty, yous will have to modify security on the folder, outset taking over ownership, so granting yourself full control.
    seven)  One time security is granted, copy the contents of this binder from a skilful auto to the auto presenting the 0x00000057.

    At present try connecting to the print queue on the impress server.  The driver should now download and install properly.


    2 found this helpful
    thumb_up
    thumb_down

  • Glad yous got information technology working.. Printers/Drivers can be a pain 😉


    Was this post helpful?
    thumb_up
    thumb_down

  • Michael7953 wrote:

    Glad you got it working.. Printers/Drivers tin be a hurting 😉

    Tell me about it. 🙂 I would be happy to push all our printer out an airlock and phone call it a 24-hour interval…… now if only I had an airlock to push them out off


    Was this post helpful?
    thumb_up
    thumb_down

  • I know this is an sometime thread, but yous may as well want to open up Print Server Management in an MMC on the troubled computer and cheque to see if the printer drivers are already there. This worked out well for me.

    *And by check, I mean delete the entries that are at that place. This seemed to be what was causing my problems.


    Was this post helpful?
    thumb_up
    thumb_down

  • I’ve simply had this exact problem.

    The fix from Microsoft Technet (mentioned earlier) failed to work for me.

    I had to log onto the troubled computer as admin, open up Print Server Management in an MMC, go to All Drivers and remove the packages for the drivers that were causing the problem.

    And then, when adjacent trying to connect to a network printer, it downloaded the commuter and installed without fault.


    1 found this helpful
    thumb_up
    thumb_down

  • I have the same result witha driver installation to windows vii pro. The driver will not load. Can someone transport me the registry the registry referred to by Molan in 2013?


    Was this post helpful?
    thumb_up
    thumb_down

  • Great post! thank you!


    Was this post helpful?
    thumb_up
    thumb_down

  • RoyL wrote:

    have you lot seen this mail on technet?

    http://social.technet.microsoft.com/Forums/en-U.s./itmanager/thread/a225d71c-be8b-4530-bf50-63001559a9…

    I had the same issue today, and this post past Royl had the info i needed to resolve the upshot.

    Thank you!


    Was this post helpful?
    thumb_up
    thumb_down

  • Only ran into this problem this morn.  What worked for me was this:

    1. Navigate to C:\Windows\System32\DriverStore

    2. We are looking for iv files in this folder:

        INFCACHE.1

        infpub.dat

        infstor.dat

        infstrng.dat

        I was unable to change the names of these files even after taking ownership of them, but I WAS able to but delete them equally a local admin.

        Later on deleting these iv files, I was able to install the printers.  Hope this helps someone.


    ii constitute this helpful
    thumb_up
    thumb_down

  • Calculation my $.02 on this issue:

    On a generally Windows 2008 R2 domain, Windows 7 x64 workstations.

    The Technet article linked higher up was the solution (effectively). I installed the target printer on my own machine, then found the registry entry so I could find the desired print driver folder.

    So here’southward my input specifically: As molan stated above, the folder didn’t exist on the trouble machine, so I merely copied that entire folder from mine. I didn’t fifty-fifty truly accept to mess with permissions — I but copied that entire folder into C:\Windows\System32\DriverStore\FileRepository and information technology asked to drag to admin and … abroad we become.

    Printers added back in merely fine afterwards.

    To note: the printers had been installed previously; stopped working; were deleted past the user every bit function of troubleshooting, and so couldn’t exist reinstalled.


    Was this post helpful?
    thumb_up
    thumb_down

  • Oh thank you Jake156 ! That worked for me afterward attempting so many other things 🙂  FYI:

    User was unable to add a printer considering he was getting the 57 fault. I attempted to remove the driver from impress management and add it simply he was still getting the 57 error. I attempted to clear the registry of the printer merely it was already gone. I attempted to run a fix it app for the 57 mistake only I yet got information technology. I then went to c:\Windows\System32\DriverStore\FileRepository and made myself owner, gave myself permissions, and deleted the ii Lexmark drivers from there just he however got the 57 error. I and so went to the driverstore binder and deleted the INFCACHE.1, infpub.dat, infstor.dat and infstrng.dat later giving myself buying and that fixed information technology. He was able to get the printers added.


    Was this postal service helpful?
    thumb_up
    thumb_down

  • Jake156 wrote:

    Just ran into this problem this morning.  What worked for me was this:

    1. Navigate to C:\Windows\System32\DriverStore

    2. Nosotros are looking for 4 files in this folder:

        INFCACHE.1

        infpub.dat

        infstor.dat

        infstrng.dat

        I was unable to change the names of these files fifty-fifty later on taking ownership of them, simply I WAS able to just delete them as a local admin.

        After deleting these iv files, I was able to install the printers.  Hope this helps someone.

    cheers a lot @Jake156 – you saved my day!

    fix worked and all network printers are back


    Was this post helpful?
    thumb_up
    thumb_down

  • Dainty i Jake, Was shut to pulling my hair out!!


    Was this post helpful?
    thumb_up
    thumb_down

  • Jake156 wrote:

    Just ran into this problem this morning.  What worked for me was this:

    1. Navigate to C:\Windows\System32\DriverStore

    2. We are looking for 4 files in this folder:

        INFCACHE.i

        infpub.dat

        infstor.dat

        infstrng.dat

        I was unable to modify the names of these files fifty-fifty after taking ownership of them, but I WAS able to simply delete them every bit a local admin.

        Later on deleting these 4 files, I was able to install the printers.  Hope this helps someone.

    Give thanks YOU @Jake156! Your solution was exactly what I was looking for and fixed it for me! I was getting pretty frustrated over this and running out of options. So glad that I ran into this thread and your reply. Thanks!! You have some happy campers over here.


    Was this postal service helpful?
    thumb_up
    thumb_down


  • kam.salisbury

  • Jake156! OUTSTANDING Give thanks you lot!


    Was this post helpful?
    thumb_up
    thumb_down

  • I’d highly advise anyone having this problem to try this solution. I had the aforementioned problem with not being able to install printer drivers on 2 machines, and this fixed it right up on both. I think this works because the driver was attempted to be installed, but failed. This uses congenital in Windows functions to resolve the outcome, without deleting files, changing permissions, or whatsoever other sledgehammer stuff. 😉  It might not work in all cases, simply I believe in using the least intrusive method for fixing things when possible.

    Here’s the basic steps: (Make sure you do RunAs administrator command prompt)

    1. Run this command to list all installed drivers:
    pnputil -e.

    Yous’ll see output similar this, merely many more:

    Published proper noun : oem60.inf
    Driver package provider : Ricoh
    Course : Printers
    Driver date and version : eleven/07/2016 4.12.0.0
    Signer name : Microsoft Windows Hardware Compatibility Publisher

    ii. Observe the .INF file for the driver you’re trying to install.

    3. Run this control to delete the problematic driver:
    pnputil -f -d oemXXX.inf

    Once I did that, I was able to connect to the printer and download drivers normally.

    Michael7953 wrote:

    +1 for ccleaner

    Mayhap if you lot can: A reboot of the server

    Check out this link:

    http://thebraveadmin.wordpress.com/2011/06/07/operation-could-not-be-completed-error-0x00000057-when…


    Was this mail helpful?
    thumb_up
    thumb_down

  • This worked like a charm for my version of the trouble. Other recommendations didnt assistance unfortunately


    Was this postal service helpful?
    thumb_up
    thumb_down

  • I dearest Spiceworks!  This thread helped me solve the same problem with a domain joined Win8.ane laptop and a Xerox 6400.  Copying the driver folder from a working car to the ane having issues saved the solar day.


    Was this post helpful?
    thumb_up
    thumb_down

  • This worked like a charm.  Thanks.  Here is the total text from the TechNet article.

    It’due south actually the print driver failing to install, not the connection to the print server. An initial attempt to install the driver failed, so the driver directory is present on the workstation, but missing the files.

    1) On a machine with the aforementioned commuter installed (and working properly), open Regedit, and browse to:
        HKLM\System\CurrentControlSet\Command\Print\Environments\Windows NT x86\Drivers\Version-three\
    2) Locate the subkey for the printer commuter you are dealing with and click the key for the printer commuter.

    3) Await for the “InfPath” on the right. Notation the path.
    5) Now scan to C:\Windows\System32\DriverStore\FileRepository and locate the folder indicated in the InfPath reg value.
    half dozen) Get to the users estimator exhibiting this behavior, and scan to C:\Windows\System32\DriverStore\FileRepository and see if the folder is nowadays.  In my case, the binder was present, but empty. If it is here and it is empty, yous will have to change security on the folder, first taking over buying, then granting yourself total control.
    7) Once security is granted, copy the contents of this folder from a good car to the machine presenting the 0x00000057.

    Now attempt connecting to the print queue on the print server. The driver should now download and install properly.

    Expert luck. This isn’t the kickoff fourth dimension I’ve seen this happen, simply this is the kickoff time I decided a reimage was more than I wanted to take on, and I wanted to solve this so that I can correct it the next fourth dimension it happens. And I accept yet to observe a existent solution to the 0x00000057 error code.


    Was this post helpful?
    thumb_up
    thumb_down

Read these next…

Windows Cannot Connect to the Printer Error 0x00000057

Read:  How to Share Printer in Windows 10

Check Also

Always Connected to Hp Printer 415 Wireless

Always Connected to Hp Printer 415 Wireless

Always Connected to Hp Printer 415 Wireless Z7_3054ICK0KGTE30AQO5O3KA30N0 hp-concentra-wrapper-portlet Actions HP Printers – Troubleshoot a …