We found those too but didn't help
0x00000002I just found a MS forum about this topic, where they restarted the spooler, which you might have done and at some stage the reboot helped... Now I am aware of what this implies if this is a production server...
The 2nd link actually mentioned the print processor folders and files I mentioned earlier.
not sure if this helps much more...
If you open a ticket with Xerox can tested, attempt to replicate and remote support if agreed.
We've done all that sort of stuff, we used the microsoft tool that removes every driver on the server as well. nothing seems to fix it....
No not really..
its because for me the next steps would be a full clean up for the GPD print environment, and due to responsability and accountability, as Xerox employee, this should be done using the support process, where one of your guys can login to your environment and troubleshoot the issue, and if no luck can escalate to an higher level.. just that.
You have done the basic troubleshooting... even the step on my last post of cleaning printprocessors is a good go, but will have to be done at your own risk if following the forum community.
yeh, thats why we're stuck because the error says that it cant find something??
I'll see if I can get a ticket opened
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.
yes, thats it.
Its strange because the same driver is installed on both yet when a network printer is added on the application server you get this error.
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?
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.
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.