Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
1589 views

NDPS - Printer Jams - Job starts from begining

Hey there folks.

I have an accounting client that is currently running 3 HP-LJ5Si's in a
major production environment. There are NDPS printers and each is
pointed to a single Queue with the Manager started with load balancing.

The problem is that lots of the jobs they are sending are over 500 pages
in length. VERY large tax returns and associated paperwork.

They will get paper jams now and then of course, thats just life with
printers. But the problem is that even if the job is say, 98% complete,
NDPS will re-queue then ENTIRE job! This is a huge waist of paper and time.

Is there any way ( I haven't found a way in either iManager or NWadm32 )
to make it simply pick up from where it left off?

- Bill
0 Likes
5 Replies
Absent Member.
Absent Member.


Bill Sappington;2664426 Wrote:
> Hey there folks.
>
> I have an accounting client that is currently running 3 HP-LJ5Si's in
> a
> major production environment. There are NDPS printers and each is
> pointed to a single Queue with the Manager started with load
> balancing.
>
> The problem is that lots of the jobs they are sending are over 500
> pages
> in length. VERY large tax returns and associated paperwork.
>
> They will get paper jams now and then of course, thats just life with
> printers. But the problem is that even if the job is say, 98%
> complete,
> NDPS will re-queue then ENTIRE job! This is a huge waist of paper and
> time.
>
> Is there any way ( I haven't found a way in either iManager or NWadm32
> )
> to make it simply pick up from where it left off?
>
> - Bill


NDPS does not have any idea what is exactly in the job and how much is
exactly printed. For instance, if the pritner fails, the printer may
alreaday have had multiple pages in memory that were not pritned yet.
For this reason, on a failed job, NDPS always restarts a job from the
beginning.


--
cimetmc

Marcel Cox
http://support.novell.com/forums
0 Likes
Absent Member.
Absent Member.

cimetmc wrote:
> Bill Sappington;2664426 Wrote:
>> Hey there folks.
>>
>> I have an accounting client that is currently running 3 HP-LJ5Si's in
>> a
>> major production environment. There are NDPS printers and each is
>> pointed to a single Queue with the Manager started with load
>> balancing.
>>
>> The problem is that lots of the jobs they are sending are over 500
>> pages
>> in length. VERY large tax returns and associated paperwork.
>>
>> They will get paper jams now and then of course, thats just life with
>> printers. But the problem is that even if the job is say, 98%
>> complete,
>> NDPS will re-queue then ENTIRE job! This is a huge waist of paper and
>> time.
>>
>> Is there any way ( I haven't found a way in either iManager or NWadm32
>> )
>> to make it simply pick up from where it left off?
>>
>> - Bill

>
> NDPS does not have any idea what is exactly in the job and how much is
> exactly printed. For instance, if the pritner fails, the printer may
> alreaday have had multiple pages in memory that were not pritned yet.
> For this reason, on a failed job, NDPS always restarts a job from the
> beginning.
>
>

I see... Well just tell me ( if you know ) that MS printing isn't any
different. I am going to have to explain this to them and make it clear
that there is no solution, no matter who's server you use.
0 Likes
Absent Member.
Absent Member.

> Hey there folks.
>
> I have an accounting client that is currently running 3 HP-LJ5Si's in a
> major production environment. There are NDPS printers and each is
> pointed to a single Queue with the Manager started with load balancing.
>
> The problem is that lots of the jobs they are sending are over 500 pages
> in length. VERY large tax returns and associated paperwork.
>
> They will get paper jams now and then of course, thats just life with
> printers. But the problem is that even if the job is say, 98% complete,
> NDPS will re-queue then ENTIRE job! This is a huge waist of paper and time.
>
> Is there any way ( I haven't found a way in either iManager or NWadm32 )
> to make it simply pick up from where it left off?
>
> - Bill


Hi Bill,

I am having a similar issue with my printers around campus. Large print
jobs fail and re-queue on all of our HP laser printers. Allow me to ask
you this, is it physical jamming that is occuring or are you getting any
communication errors that may "aseem" like paper jams? I ask because our
printers give a "MIO 40xx" error and my clients assumed it was a jam until
I looked into it further.

As far as I know, there is no way in the iManager/NWadm32 program to tell
it to continue the job from where it had an issue.

Take care,
Shahid

0 Likes
Absent Member.
Absent Member.

> I am having a similar issue with my printers around campus. Large print
> jobs fail and re-queue on all of our HP laser printers. Allow me to ask
> you this, is it physical jamming that is occuring or are you getting any
> communication errors that may "aseem" like paper jams? I ask because our
> printers give a "MIO 40xx" error and my clients assumed it was a jam until
> I looked into it further.
>
> As far as I know, there is no way in the iManager/NWadm32 program to tell
> it to continue the job from where it had an issue.
>
> Take care,
> Shahid
>


These are physical paper jams, crinkled paper in the fuser section, feed
section etc.
0 Likes
Absent Member.
Absent Member.

From what I remember (and my memory is fuzzy), Microsoft isn't any better.
However newer printer technology might help (5si's are a bit ancient now).
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.