Something have a "reference" open on the job. This is typically a handle
reference and until the calling method returns and closes the handle the
spooler process cannot delete the file.
You can debug the spooler (this also requires admin rights on the print
server), but I have done this and once the method closes without releasing
the reference, it's gone.
If the print job is "Deleting - Printing" and scheduled to a Port then stop
and start spooler rather than reboot (which would also require admin
rights). If the job is deleting, this will not block other print jobs.
You can configure the queue such that Bidirectional is disabled (on the
Ports tab of printer properties) , this will eliminate pjlmon (inbox
language monitor).
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1
This posting is provided "AS IS" with no warranties, and confers no rights.
"John" <John@newsgroup> wrote in message
news

5F7090E-BA6F-49E2-919A-D7FDE5F8E883@newsgroup
> The only problem with that solution is you have to be a administror of the
> printer server.
>
> Is there a Microsoft KB article, on how to diagnose the cause on why the
> print server is stuck "Deleting" a print job.
>
> Thanks
>
> "Grant Taylor" wrote:
>
>> On 09/24/09 17:10, John wrote:
>> > How do we delete the job without a reboot? >>
>> Try stopping and re-starting the Spooler & LPR services. That usually
>> clears hung "Delete"s for me.
>>
>>
>>
>> Grant. . . .
>>