Windows cannot connect to the printer, Operation failed with error 0x00000057 after migrating to Windows 7 via SCCM
I am currently working with a IT team that is migrating users in our organization to Windows 7 Enterprise. We are currently experiencing an issue where after a machine is migrated to Windows 7 and the user attempts to install their printer instance, the user receives the error: Windows cannot connect to the printer, Operation failed with error 0x00000057. After researching the issue I learned that the error meant that the driver installation was failing. I was able to workaround the issue by coping a known good respository into C:\windows\system32\DriverStore\FileRepository, removing any failed driver installations in the spooler directory, and adding an exported registry key from a known good installation. So we are at a point where we have fix but I am trying to understand why this is happening. My working theory is the registry values as well as the file repositories associated to the printer are being migrated, but somehow are corrupted during the process. The people in charge of SCCM are a few States away, so my Manager has asked me to find some information to hand off to the SCCM team. If anyone has any insight to this or perhaps some links for me to check out I would greatly appriciate it.
- Changed type Niki HanModerator Wednesday, August 31, 2011 10:15 AM
Please understand the issue can be caused by many factors. Your theory could be one of them. Since you suspect the issue is related to migration via SCCM, please confirm with SCCM team.
In addition, please contact Microsoft SCCM forum to get more information.
Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
You may well check with adding the following policy
Computer Configuration | Administrative Templates | System | Driver Installation
and used the policy "Allow Non-Administrators to install drivers for these device setup classes".
Also in that Policy we have to specify the class (GUID) of the driver.
Set the policy at the domain controller.
This is the exact same issue, seems we should merge the threads?
Is there anyway to install pull printer drivers 1 by 1 rather in 1 go which could be causing the issue.
Solution, which helped me is described here:
Hope it helps you too.