We run some print servers that frequently crash. The cause of the problem is specific print jobs sent from a 3rd party that are directed to print queues on our network. These queues occasionally have no printers on them or the printer is not compatible with the jobs, the result is that the retrying print jobs eventually (after a few days) use up all the CPU and Memory and either render the server inoperable or simply crashes. The way we normally deal with this is reboot and delete the print jobs. This cause obvious problems to the service. Is there a way to automatically cancel a job that is floating around the network after a pre-determined time?

The only automatic way I know of unless you want to spend cash on it is to write a vbscript that monitors your printqueues for old documents and deleting them. This could be done either by wmi or checking the spooler folder.Otherwise since you know the root of the problem I'd make sure that these automated print jobs are sent to a correctly configured queue with a printer attached to it since you won't have to do anything else once that's setup. My 2 cents ;)Best regards Joachim Nsslander IT-Expert, Knowledge Factory (http://www.knowledgefactory.se) MVP Cluster Member of Microsoft Extended Experts Team (MEET) Blog: http://www.nullsession.com