f



A printer attached to Windows report printer faulted printing

Does anybody knows how to solve this error?

The output below is from a printer attached to an Windows Server

root@sapunx10 # lpstat -p BAPRIP01
printer BAPRIP01 faulted printing BAPRIP01-0. enabled since Dec 28
11:03 2006. available.

                         Windows NT LPD Server
                              Printer BAPRIP01

Owner       Status         Jobname          Job-Id    Size   Pages
Priority
----------------------------------------------------------------------------
root (10.0. Waiting   /etc/apache/httpd-s   1326      9402      0
1
cbpadm (10. Waiting   /usr/sap/CBP/D01/da   2401      2084      0
1
cbpadm (10. Waiting   /usr/sap/CBP/D01/da   2380      2084      0
1

There is something that can made from the Unix side or this problem
should be resolved by the Windows  admin?

Thanks
--
Emerson Takahashi

0
eseiti (10)
12/28/2006 2:12:58 PM
comp.unix.solaris 26025 articles. 2 followers. Post Follow

1 Replies
1524 Views

Similar Articles

[PageSpeed] 18

Emerson Seiti Takahashi wrote:
> Does anybody knows how to solve this error?
>
> The output below is from a printer attached to an Windows Server
>
> root@sapunx10 # lpstat -p BAPRIP01
> printer BAPRIP01 faulted printing BAPRIP01-0. enabled since Dec 28
> 11:03 2006. available.
>
>                          Windows NT LPD Server
>                               Printer BAPRIP01
>
> Owner       Status         Jobname          Job-Id    Size   Pages
> Priority
> ----------------------------------------------------------------------------
> root (10.0. Waiting   /etc/apache/httpd-s   1326      9402      0
> 1
> cbpadm (10. Waiting   /usr/sap/CBP/D01/da   2401      2084      0
> 1
> cbpadm (10. Waiting   /usr/sap/CBP/D01/da   2380      2084      0
> 1
>
> There is something that can made from the Unix side or this problem
> should be resolved by the Windows  admin?


once the job has moved to the server, it's the server that needs to
handle it.  So, involve your Windows admin; perhaps there is some
garbage in the spooling directory or something like that.
> 
> Thanks
> --
> Emerson Takahashi

0
mlstarkey
12/28/2006 9:13:52 PM
Reply: