SBS Office 2000 and Printer Lock-Up

Hi. We've got a LAN with 8 workstations plus server
running SBS2000. We have 3 printers on network and up
until yesterday, all worked fine.
Yesterday a user at a workstation sent a print job to the
newest networked printer (HP Laserjet 4100). The job does
not appear to have ever reached the printer itself (i.e.
the printer is not acknowledging receiving any data and
has no job to cancel). The job is, however, clogging up
the print que.
We have tried to cancel/delete the job, from both the user
who created it's workstation and the server. Both
attempts appear to be successful (i.e. no error message),
and the job's status changes to "deleting", but it doesn't
ever delete (over 24 hours now). We have tried
uninstalling that printer from that workstation and
reinstalling, which works, but when reinstalling, the
subject bad job is still in que (under
status "deleting"). We have tried deleting and/or
uninstalling the subject printer from the server, which
again appears to work (status of printer changes
to "Deleting") but the printer never gets deleted.
We're at wits end! Have searched net but could not find
any information. Any help would be greatly appreciated.
If you could cc: any responses to mcpineny[nospam]
@netscape.net (without the text: "[nospam]") it would be
doubly appreciated.
Best regards.

Dave
Thu Oct 23 13:09:08 CDT 2003

You could try stopping and restarting the print spooler service on the
server and workstation. I'm assuming the workstation has been restarted
since yesterday - the reason I ask is that the spooler or an app could be
waiting for a confirmation that the job printed, which of course it didn't.
I've had situations where I'd delete a job, but the spooler would keep
resubmitting it until it printed, or until I killed the job in whatever was
doing the resubmitting.

The queued jobs are probably in C:\WINNT\SYSTEM32\SPOOL\PRINTERS - if
restarting the spooler service doesn't help, you could try moving any
likely-looking files out of there to see if that gets rid of the job. With
no jobs queued, that directory is probably empty, so chances are that any
files in there are the offenders.


"PDM" <anonymous@discussions.microsoft.com> wrote in message
news:0aad01c3996c$3b4437b0$a401280a@phx.gbl...
> Hi. We've got a LAN with 8 workstations plus server
> running SBS2000. We have 3 printers on network and up
> until yesterday, all worked fine.
> Yesterday a user at a workstation sent a print job to the
> newest networked printer (HP Laserjet 4100). The job does
> not appear to have ever reached the printer itself (i.e.
> the printer is not acknowledging receiving any data and
> has no job to cancel). The job is, however, clogging up
> the print que.
> We have tried to cancel/delete the job, from both the user
> who created it's workstation and the server. Both
> attempts appear to be successful (i.e. no error message),
> and the job's status changes to "deleting", but it doesn't
> ever delete (over 24 hours now). We have tried
> uninstalling that printer from that workstation and
> reinstalling, which works, but when reinstalling, the
> subject bad job is still in que (under
> status "deleting"). We have tried deleting and/or
> uninstalling the subject printer from the server, which
> again appears to work (status of printer changes
> to "Deleting") but the printer never gets deleted.
> We're at wits end! Have searched net but could not find
> any information. Any help would be greatly appreciated.
> If you could cc: any responses to mcpineny[nospam]
> @netscape.net (without the text: "[nospam]") it would be
> doubly appreciated.
> Best regards.