problem with cancel requests

[Dunja]

Hi,

I have a strange problem. I have a printer with the following status:
printer queue for ptr157

Windows NT LPD Server
Printer ptr157 (Paused)

In the queue I see a lot of requests. I want to delete these, but that doesn't work.

When I do lpstat, I see:
printer queue for ptr157

Windows NT LPD Server
Printer ptr157 (Paused)

Owner Status Jobname Job-Id Size Pages Priority
----------------------------------------------------------------------------
cals (10.13 Waiting /opt/..... 58 522 0 1
cals (10.13 Waiting /opt/..... 60 522 0 1

in total 349 requests. But /var/spool/lp/request/ptr157 is empty. I tried cancel the printjob with cancel ptr157-58. But when I do lpstat again I still see the job.
I restarted the scheduler, I also removed the printerqueue and created again.
But all the requests still exists.

What do I wrong or what is the problem?

[Victor BERRIDGE]

Hi,
Normally only the owner of what is in the pool can cancel...
Have you tried cancel -e as root?


All the best
Victor

[Dunja]

Yes, I did all of that as root

[OldSchool]

it appears that the problem is on the "Windows" side.

Enable the printer in the windows server (where it is currently "paused") and then you can remove jobs as necessary from the prt157.

You didn't say which release of NT, so I'm assuming 4.0. I have seen cases where the print services become so confused that a reboot of the server is required.

[Patrick Wallek · Accepted solution]

I agree with the previous person that these print jobs are on the Windows Printer Server.

The lines:

Windows NT LPD Server
Printer ptr157 (Paused)

are the keys.

Doing a cancel from teh Unix side would have no effect on print jobs after they have been transferred to the Windows machine.

You need to go to the Windows server to take any actions for those print jobs.

[Dunja]

I think is NT 4.0. I ask the helpdesk to check the status of this printer again. I ask this before and the printer was enabled.
But now they wil disable/enable the printer again.

So I have to wait.

Thanks for so far.

Dunja

[Dunja]

The problem was on the NT server. The queue was full and the status was Paused. So they empty the queue and enabled the queue again.

Thanks for the assistence.

Dunja