Hi humc,
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.
Please select Accept as Solution if you feel this post has helped you.
