Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Lost Print Jobs

Status
Not open for further replies.

MailMan2

Programmer
Dec 2, 2002
8
CA
We have some users complaining of lost or incomplete print jobs. They will request 5 copies and might get one, two or partial sets. I have simulated the problem by forcing an out of paper situation, I get the RED box TERM/0 Quit Retry... add paper select retry and it might print another 10-20 pages of my expected 50. Application and databases reside on a Win 2000 server SP2 and the users run the application from a Win 95 box. Printers used are either Lexmark Optra T520 or T612.

Any help appreciated.

Thanks!

MailMan2
 
Odd questions. 1) These are not Windows only printers, right? 2) Was it working fine before? 3) The printer cable is FULLY plugged in?

Frank
 
You know never thought of checking if they supported DOS printing. However problem has started to appear even when using older Xerox 4213 model printer. Cable is well plugged even went out and bought the recommended IEEE 1284 compliant cable.

MailMan2
 
Well, next question is this occuring on all computers, or only one. Are all the computers Win2000, or can you test on a Win95 or Win98 machine? Data streaming out should not just disappear!
 
It occurs on all workstations which are Win95 boxes.

Currently LexMark are investigating the issue further as we cannot even send a file from a DOS prompt to the printer. They suspect it might have something to do with insufficient memory on the printer or the SIMM card which translates the XES code.

Will keep you posted.

MailMan2
 
Additional error trapping added to the SIMM card which translates our XES code to PS has provided us with the following bit of info...

When there is a problem with the printer (out of paper for example) and our application detects it we get the red box "Error TERM/0 Print Error, Quit Retry". It appears that once you reload the paper and hit retry either the application or Windows resends the last string it sent to the printer and this causes the print job to abort because the XES Emulator cannot interpret that line.

Any ideas would be appreciated.

Regards,

MailMan2
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top