Is there a removal tool for the GPD. We have been having problems with this driver and want to strip it out.
When we try to add a network printer an error appears "windows cannot connect to the printer. operation could not be completed error (0x00000002)"
I have removed the drivers and packages using the pnputil commands, stripped out everything from the registry that mentions xerox, but even if I try to install the GPD manually I get this message. It only happens with the GPD and any version of it? other Xerox drivers are ok and also hp?
So this is why I want a removal tool, just incase I'm missing something.
After a bit of investigation with process monitor we've found that when you add a printer it creates a temp folder in "c:\windows\system32\spool\drivers\x64\" and its this folder that it says cannot be found even though you see it being created then its deleted??
Checked this on a working server and again you see the folder get created then deleted but with no errors.
Where does it get thie data to put in this folder?
As a work around I have created a local printer using the GPD and this works fine, only when I try to add the network printer or install the driver manually I get this message.
let me see if I completely understood problem. You trying to install a driver on a Printserver which will be used than to deploy printer to clients.
If so, what you described to unistall the print driver is correct. Make sure to clean the driver and package. Clean the %systemroot%\system32\spool\drivers. If you feel confortable to work the reg its even better.
Next step is to install the driver. If you follow the classic process using the Add printer wizard, than you want to select Local Printer. This is the correct open to use. Afterwards on the client side you if you need to create the printer manualy than you will use add printer > Network printer... because it will already exist on the network AND shared.
The problem happens on an application server. Other application servers are ok, we have removed the driver plus any registry files but it does not let you install any version of the GPD, it doesn't matter if you install the driver manually or by adding a network printer from the print server, the error is allways the same.
HP and other xerox drivers install ok.
Any chance you get error on event viewer when installing the driver?
Some sort of error needs to comeup... keep in mind to use Local Printer instead of Network printer on the printer wizard.
something has happened to the existing driver as I can install a local printer using the driver but if I try to connect to a network printer that uses the same driver you get this error, thats when the problem was first discovered. As its an application server the users connect to what ever printer they need but at the moment does't work with any printer that uses the GPD. We don't install local printers on the application servers as every user would see this.
There are no messages in event viewer.
Ok.. this is a bit different... so let me see if I get it..
You have somewhere a print server witht the driver installed localy (local printer), Than from the "Application Server" you install the point and print printer, Add printer > Network printer> point to the print server and the driver gets installed automaticaly because its downloaded from the print server...
is this it?
What I find strange is that this error would normally mean that the system is not able to find the specified file, therefore my question about the point and print process.
Are you able to check the contents of %systemroot%\System32\spool\prtprocs\x64. You will find all print processors for your printers. It could be the case the driver is not able to instal it becaus of exising files, naming conflit. If you need to temporarely change the files you will need to stop the spooler. You would be looking at a series of folders names 1-4xx.
And from here the next step would be a full cleanup.. but to be honest this is where the community support stops. If you are able to open a ticket with us would be the best. If you are in Europe, you will go through software support and maybe a remote session could help.
I know this is not the expected anwser.. but to be honest I think the problem could be around this area.