Get the following error message when trying to view properties on a networked Xerox Workcentre 7545:
Xerox Printer Driver
The Xerox print driver encountered an error while trying to convert to/from the Xerox XML Format.
There may be illegal data present or the required DTD file may be missing. You may have to reinstall the Xerox print driver.
Troubleshooting steps taken on the workstation:
1. Deleted network printer and Xerox driver
2. Installed the Xerox printer using IP instead
3. Deleted Printer Port and Xerox driver
The workstation is running Windows XP x86 SP3
Any ideas will be much appreciated.
Any updates on this issue will be much appreciated.
I have searched for this issue on the Internet with no really results, except for the Xerox Global Print Driver issue on this Forum (http://forum.support.xerox.com/t5/Printing/Xerox-Global-Print-Driver-issue/td-p/4518).
I have exactly the same problem. Deleted the printer, removed the driver, restarted the spooler and reinstalled the printer - nothing changed.
While testing I added the printer as network printer via a printserver (\\server\printer) as well as directly via tcp/ip. PS driver, PCL driver, no way...
I can print on every other printer in our network (same printserver, different printers) without any problems only the xerox machine doesn't work. Maybe xerox hates me :-(
Please make sure to read this tip upfront before performing any changes..
if this happens both on the workstation and on the print server, my suggestion is that we focus on one of them at the moment.
Whichever you wich to install the driver locally... make sure you delete the print queue (or change the driver attached to it to another driver).
Make sure you do not have any other driver (even of different PDLs < PCL/PS> for the same model)
After this is done, restart the spooler.
No changes to the registry should be required...
Now proceed with driver instalation:
this part is extremely unreasonable "Make sure you do not have any other driver (even of different PDLs < PCL/PS> for the same model)"
do you realize how many printers would be taken offline if i was forced to do this in a production environment...that's all great and dandy for a dev environment but as soon as the same thing happens in production forget it.
BTW i have the same exact issue. for us it only happens with PS driver. The others are fine.
It doesnt matter if its unreasonable or not, if you cant fix it any other way, you'll have no choice.
Of course everyone realizes that it could take a very long time to set it up again, but what can you do if nothing else works?