Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

A virtual printer already exists!!!

394 views
Skip to first unread message

Dale

unread,
Sep 12, 2006, 2:55:06 PM9/12/06
to
I am running AIX 5.1.

I added a new print queue using SMIT.

I realized that I used the wrong driver.

I removed the print queue using SMIT.

I attempted to add the print queue again and received this message:

0782-652 A virtual printer already exists for the queue name
NAMEWITHELD and
the queue device name hp@NAMEWITHELD!

I'm sure I am supposed to go look around and remove a file somewhere
using the command line.

Either that, or I have to wait a certain amount of time for the system
to refresh something.

Any ideas?

Thanks,
Dale

Ian Northeast

unread,
Sep 12, 2006, 3:39:06 PM9/12/06
to
On Tue, 12 Sep 2006 11:55:06 -0700, Dale wrote:

> I am running AIX 5.1.
>
> I added a new print queue using SMIT.
>
> I realized that I used the wrong driver.
>
> I removed the print queue using SMIT.
>
> I attempted to add the print queue again and received this message:
>
> 0782-652 A virtual printer already exists for the queue name NAMEWITHELD
> and
> the queue device name hp@NAMEWITHELD!
>
> I'm sure I am supposed to go look around and remove a file somewhere using
> the command line.

This shouldn't happen if you did as you describe, but try using rmvirprt
to remove the virtual printer. It won't let you do it via smitty as the
queue doesn't exist.

I've only seen this happen when someone has manually deleted a queue from
/etc/qconfig.

Regards, Ian

steven_nospam at Yahoo! Canada

unread,
Sep 12, 2006, 4:45:54 PM9/12/06
to

Ian Northeast wrote:
> This shouldn't happen if you did as you describe, but try using rmvirprt
> to remove the virtual printer. It won't let you do it via smitty as the
> queue doesn't exist.
>
> I've only seen this happen when someone has manually deleted a queue from
> /etc/qconfig.
>
> Regards, Ian

I saw this once or twice, usually it was when someone added a virtual
printer, but then cancelled it during queue creation stage with CTRL-C
or some other SIGKILL.

Steve

Ian Northeast

unread,
Sep 12, 2006, 6:25:15 PM9/12/06
to
On Tue, 12 Sep 2006 13:45:54 -0700, steven_nospam at Yahoo! Canada wrote:

> Ian Northeast wrote:

(original issue with being unable to define a print queue because a
virtual printer associated with its name still existed was snipped)

I hadn't thought of that one. Usually I have seen it when a machine has
been cloned using a mksysb and someone has decided to "clean" the old
queues by editing qconfig, ignoring the entries in /var. This is effective
enough until you need to redefine a queue which existed on the machine the
mksysb came from, whereopon you hit this error.

Neither explains why it happened to the OP though, he appears to have
followed correct procedures. But hopefully rmvirprt will resolve his
problem, it always has for me.

Regards, Ian

laix...@laixsoft.com

unread,
Sep 12, 2006, 9:59:01 PM9/12/06
to
>> I saw this once or twice, usually it was when someone added a virtual
>> printer, but then cancelled it during queue creation stage with CTRL-C
>> or some other SIGKILL.
>
> I hadn't thought of that one. Usually I have seen it when a machine has
> been cloned using a mksysb and someone has decided to "clean" the old
> queues by editing qconfig, ignoring the entries in /var. This is effective
> enough until you need to redefine a queue which existed on the machine the
> mksysb came from, whereopon you hit this error.
>

Start looking in /var/spool/lpd/pio/@local/custom where the virtual printer
colon files reside. If you've got a virtual printer for a queue which no
longer exists, this is where you would find it.

Best regards,
Paul


Dale

unread,
Sep 15, 2006, 7:18:00 PM9/15/06
to

> Start looking in /var/spool/lpd/pio/@local/custom where the virtual printer
> colon files reside. If you've got a virtual printer for a queue which no
> longer exists, this is where you would find it.

I was able to find a file that needed to be removed in one of those
directories around that area and that solved the problem.

Thanks!
Dale

0 new messages