I have 6 terminal servers all in the same domain. All of them are 2008 R2. Recently 3 of the servers are no longer redirecting local LAN and USB printers if they are using Brother drivers. If I change the driver for that printer to something like Kyocera or Xerox it will show up just fine. I've tried to stop/start the printer spool, remove the drivers and add them back. When I try adding the drivers back I get the 0x00000002 error.

I've also tried the Microsoft fix that restores the print spooler back to when the OS was first installed. No drivers or printers... No luck. I get the same 0x00000002 error when I try to add the drivers back.

If anyone knows how to fix this please let me know! It's been driving me crazy.

Hi,

The 0x00000002 error means Windows cannot connect to the printer.  Operation could not be completed .

Did you have tried the following KB article to fix the issue?

https://support.microsoft.com/en-us/kb/2793718

Please feel free to let us know if you have any update about the issue.

Regards.

I have tried that KB article. Running the full version took a very long time to complete. When it finally finished I was still receiving the 0x00000002 error when I tried to reinstall the drivers.

Hi Brodellis,

sometimes it happen when driver stuck on installing stage.

check C:\Windows\System32\spool\prtprocs\x64\ for a folders like 1,2,3...499. If they are exists, delete them then try to install driver.

KR,

Sergey.

The only folder in C:\Windows\System32\spool\prtprocs\x64\ is en-US.

 0x00000002 usually means some file is missing..

Just to doublecheck: are you sure you installing driver for the same (x64) architecture?

Is it signed and packaged?

Also: In some cases it can also mean a driver dll is in use. Have you restarted the spooler service and installing the driver shortly afterwards?

• Edited by Sergey Shaleniy 18 hours 19 minutes ago

Yes. I've also tried different versions of the driver. I've tried over a network share and saving it on the desktop of the server.

I've restarted the spool many many times.

 0x00000002 usually means some file is missing..

Just to doublecheck: are you sure you installing driver for the same (x64) architecture?

Is it signed and packaged?

Also: In some cases it can also mean a driver dll is in use. Have you restarted the spooler service and installing the driver shortly afterwards?

• Edited by Sergey Shaleniy Thursday, June 18, 2015 12:42 PM

Check the Operational and Admin PrintService event logs for any other errors that may help track this down.

Have you verified that the print driver was removed from the system32\driverstore\filerepository directory prior to the reinstall?

You will most likely need to look in any folder that starts with BR and Brother.  There is an inf file that will contain the model name information.

If you find a directory with the driver files, use the pnputil tool to remove the files from the driverstore.

Then try the install again.

In the printservice -> Admin logs I'm getting a lot of 215 EventIDs, Installing printer driver - failed, error code 0x2, HRESULT 0x80070002.

I'll try to remove the printers from the drivestore using the pnputil tool ASAP.

This is starting to be very frustrating. When I try to remove the INF files in the driverstore/filerepository I receive the error...

Deleting the driver package failed: The system cannot find the file specified.

try to delete infcache.1 file, reboot and try again

The file C:\Windows\Inf\setupapi.dev.log should have additional information regarding which file is missing although that seems odd that removing the drivers would fail when a file is missing.

Look for !!! entries in the log.