Your situation might be caused by a "ghost AD printer object". i.e. the AD
printer object is incorrectly invalid as a result of the print spooler
failing to properly update/publish the AD printer object.
More: The printer AD object is a child object of the server object. To see
child printer objects, run dsa.msc, enable the view, "User, Groups and
Computers as containers", click down to open the relevant server object.
Suggested solution: Delete the printer object using dsa.msc. Re-publish the
printer object at the printer queue tab page by unclicking, apply, clicking,
apply the "List in the directory" option. Restarting the spooler service also
causes a republish ... but for all printer queues set up in this way on the
spooler.
|