I have seen this as well on a Citrix server of mine. Orignally I thought the IMS was corrupt but it turned out to be garbage in the spool file. You might try stopping the print spooler from another DC and then deleting the stuff in the spool file.
I had this to--MS site is wrong LOL--here is the correct thing to do from THEELDERGEEK.COM--found it in a google search on the problem:
Task Scheduler Object Already Exists
Problem: When trying to run a scheduled task it returns an error that states: Error (0000XXXXXXX) Object Already Exists...
I was getting a similar message about an odbc database in Access 97. The solution was to right click in the grey area of the query design, go to properties, and make sure unique records or unique values was set to "Yes".
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.