I have a Xerox 5875 here, deployed with group policy. I have one user out of 40 that can't print to this machine. She can print to our C60 fine but not to this one; it never prompts her for an accounting code, just straight to print which produces a page with an error notice that invalid accounting codes were entered or missing... but the prompt never came up.
I logged into this machine and was able to print with no issues, it prompted me for the code and printed fine when a valid code was entered. I also logged this user in at another machine and was able to print, it did prompt me for the code.
I deleted her profile from her PC and let her log back in to recreate, which remapped the printers, but still the same issue. The prompt never comes up. Only on this machine and only under her account which is strange. Under Properties, configuration, the Accounting says Xerox Standard Accounting, Print-Time Prompt: Always prompt.
I am not sure what is going on. Has anyone seen this before? Any ideas what could cause this?
Thank you for using the Support Forum. Please take a look at the solution for Job deleted due to Invalid account ID and make sure that you have everything set properly of the users PC. If this does not help please consider contacting your support centre for further assistance.
I have the same problem with a WorkCenter 7545. It affects users seemingly at random. If I delete the printer object on the client and then re-add it from the printer server, it starts working, but after a few days the problem often recurs: suddenly it stops prompting for accounting IDs and jobs are rejected. Restarting the print spooler service has no effect.
We are using the v3 PCL6 driver, version 188.8.131.52, which appears to be the latest version for Windows 7. The printer server is 2008R2. We have the accounting options set to "only prompt for color" and "remember last entered codes"
I did not try the global driver as I don't think it would make a difference. It is working on every other computer on the network other than this one, and it does work on this PC under a different account (and that account printe fine on other computers) which makes no sense.
For now, we have been using another printer for this user but soon I will be reimaging this PC to see if it works. I have already deleted the user account and recreated with the same results so not sure if it will work or not. Very strange issue.
Before you do the reimage, give the following a go, see if it is the answer.
The following info is cut and paste from a completely unrelated post, but may apply here as well.
Happens to all the GPD and resident drivers of the last few years by Xerox.
Server driver shared to clients, occasionally clients show generic driver, so instead of this:
They see this:
Driver on server and other clients are unaffected, driver needs to be totally and manually removed and reinstalled to fix at client PC.
Issue is randomized. But does happen more often on cross architecture, i.e., Win 2008 x64 shared to Win7 x86.
If you dug deeper you probably got to this screenshot showing only 3 files of what should be 30 plus.
Registry keys for the print drivers are missing. Check the registry in the following locations: (Model number obviously will be different per Xerox device)
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Environments\Windows x64\Drivers\Version-3\Xerox WorkCentre 5755 PCL6
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Print\Environments\Windows x64\Drivers\Version-3\Xerox WorkCentre 5755 PCL6
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\Xerox WorkCentre 5755 PCL6
The registry values in these locations compared with a working computer, the data has been cleared for Dependent Files, and Help File.
You can correct the problem by exporting the selected branches listed above from a working computer, and importing them into the affected one, then reboot the system. After the reboot the driver will function normally
MS has released the fix, and since you made it this far down the email here it is:
Even though the hotfix refers to a Windows Server 2008 R2 issue, the hotfix can also be applied to Windows 7-based computers that encounter this issue.