I have been using WC 5745 from a print server- Win server 08 R2, the WC printer was installed with PS drivers,and it has been working ok for the last one year. last week, the printer on the server sudenly went ofline, I tried to re install but the printer goes offline again a few minutes after re installation. nobody within the LAN can print. I reinstalled the printer with PCL6 drivers, and it works.
Can any one out there help, I dont want go to all client machines to reinstall the PCL6 drivers, if there is a way to make the thing work with PS.
Kindly help, Im currently routing all work to another network prnter (WC 5325) which runs on same server without problems.
Guided by local Xerox service representatives I've setup Xerox Global PS Printer driver for accounting. There was an additional issue with bi-directional communication, but accounting does work now.
So essentially, for 7120 with Basic Accounting the fix for me was to switch from the 7120 PS driver to Global PS driver. Maybe there would be a similar "solution" for the 7545?
I am having the same problem. I've deleted the driver and package as noted.
No change. I can install Global Printer Driver - that works to the extent that it does not crash with the error dialog, but it doesn't know about Xerox Basic Printer Accounting, so I can't actually print...
I am having the same problem with the PCL6 driver. Wow.
(The system config is Win7 64 bit (Czech), Xerox WorkCentre 7120.)
Those are troubleshooting tips you can follow to resolve a problem, whether you can replicate or not, whether is on a production or test environment. This is a forum to share ideas and experiences. There is limited information and the solutions you propose must apply to your problem and still suit several publics. The ultimate decision is yours on if you think this might work and the best way to apply. If your scenario is more complex, for whatever reasons, and you see that the solution somehow are reasonable but you are unsure how to apply it you can always contact Xerox support services for an technical personalized analysis.
I do not realize how many printers you would to take offline. There was no mention of the magnitude of the problem/scenario or if you were experiencing on a production/test environment. Simply a problem that as far as I am aware could be happening on single scale.
I tend to replicate and test every problem I have, even if its to learn a bit more from it, even if its resolved.
Even if more risky... I have experienced with large production environments that the hard work are on recreating print queues. Therefore you are alwsy presented with the option to just change the driver the print queue is using to another driver (even if this leaves you with basic functionalities only) in order to be able to delete drivers without deleting print queues.
I must advise that I have had situations where the problem is on the print queue and those also had to be removed. Unfortunately, in my opinion XML error can be associated with print queues and drivers.
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?
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.
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:
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 :-(
Outcome? I'm also experiencing the same issues with various printers.
can you try to uninstall and reinstall the xml package and start over?