|
|
|
|
|
|
|
|
|
|
KipCody medical school grad
Joined: 16 Jul 2013 Posts: 65 Location: Knoxville, TN |
Posted: Wed Mar 04, 2015 3:26 pm Post subject: Bad Ascii job ticket |
|
|
I have a customer with a 3000 that is printing from a Mac over wireless to the printer via Print Net. Everything was working fine up until yesterday when every file he sent came out like this : Bad ASCII Job Ticket: D:\Monpath1\Request\MIVPXAYB\MIVPXAYB.Kip I was hoping that someone could shed some light on what I can do to resolve this. |
|
|
|
|
|
|
|
|
|
|
cjwilt doctor
Joined: 24 Jan 2007 Posts: 1041
|
Posted: Wed Mar 04, 2015 3:43 pm Post subject: |
|
|
Have you tried anything to resolve this? Like run check disk or clear out the Monpath1\request folder?
Do the internal test prints come out? |
|
|
|
|
|
|
|
|
|
|
KipCody medical school grad
Joined: 16 Jul 2013 Posts: 65 Location: Knoxville, TN |
Posted: Wed Mar 04, 2015 3:56 pm Post subject: |
|
|
I haven't had the chance to go out there yet, I wanted to have a couple of options to try before I got there. |
|
|
|
|
|
|
|
|
|
|
cjwilt doctor
Joined: 24 Jan 2007 Posts: 1041
|
Posted: Wed Mar 04, 2015 4:00 pm Post subject: |
|
|
Cool.
I would start with trying an internal test print. Then clear D:Monpath1\request then check disk.
I hope this helps. |
|
|
|
|
|
|
|
|
|
|
KipCody medical school grad
Joined: 16 Jul 2013 Posts: 65 Location: Knoxville, TN |
Posted: Wed Mar 04, 2015 4:09 pm Post subject: |
|
|
Thanks for the tips! I'll let you know how it turns out. |
|
|
|
|
|
|
|
|
|
|
jezebel09 resident
Joined: 12 Jun 2013 Posts: 209
|
Posted: Wed Mar 04, 2015 6:17 pm Post subject: |
|
|
Is it just a single user that is having the issue or is it multiples?
I would also go with the previous suggestion as PrintNET is running from the printer controller and it is creating the job ticket on the controller; unlike from KIP Print/Request or the printer drivers....they do this remotely and then send the data over.
A bad job ticket is something that is corrupted in the .kip file and/or the KIP Unattend program cannot read what is in the job ticket for some reason....again odd since PrintNET is generating it. _________________ **************************************
Ockham's razor - usually is the best answer....
************************************** |
|
|
|
|
|
|
|
|
|
|
KipCody medical school grad
Joined: 16 Jul 2013 Posts: 65 Location: Knoxville, TN |
Posted: Thu Mar 05, 2015 2:57 pm Post subject: |
|
|
It's just a single user. I attempted to run check disk, and after shutting everything down for the restart all I get now is a blank screen from the IPS. It's getting power but no display whatsoever. |
|
|
|
|
|
|
|
|
|
|
cjwilt doctor
Joined: 24 Jan 2007 Posts: 1041
|
Posted: Thu Mar 05, 2015 3:10 pm Post subject: |
|
|
Check disk can take some time to run. During this time the screen will be black and you should not power cycle the printer because it will start check disk back from the start.
How long have you waited for it to come back up? |
|
|
|
|
|
|
|
|
|
|
KipCody medical school grad
Joined: 16 Jul 2013 Posts: 65 Location: Knoxville, TN |
Posted: Fri Mar 06, 2015 4:39 pm Post subject: |
|
|
I waited for about 10 minutes or so. Still a blank screen, so I brought the IPS back to the shop to check a couple of things out and it fired right up on the bench. So i'm going to go back to my customer's office and see if it works again. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|