Glock Talk
Welcome To The Glock Talk Forums.
 |
07-13-2012, 15:29
|
#1
|
|
Senior Member
Join Date: Sep 2002
Location: CA, just outside the United States
Posts: 17,255
|
Print Jobs keep getting stuck in queue
Hi guys.
I have a client who's got two XP machines and an old dot-matrix Epson LQ 570e printer. They use a custom-built command line program for their work.
For now, upgrading the entire system is simply not an option.
That being said, they have a recurrent issue with print jobs keep getting stuck in the queue.
The printer is connected to computer "A" via parallel port, and the printer is shared over the network. The command line program looks for the printer when you execute it, at \\frontcounter\EpsonLQ
Frequently, we will get a "System error 85 has occurred. The local device name is already in use."
I've tried uninstalling and reinstalling the printer (I can actually download the drivers from Epson's site) power cycling the printer and both computers, deleting the printer from the registry, etc. and I'm just stumped now...
__________________
The danger to America is not Barack Obama, but a citizenry capable of entrusting a man like him with the Presidency.
|
|
|
|
07-13-2012, 16:31
|
#2
|
|
Senior Member
Join Date: Jul 2011
Posts: 308
|
Does the command line program add the printer every time they use it?
What about a login script that has "del \\frontcounter\EpsonLQ"
That error 85 would come from trying to add the printer when it is already added.
Last edited by Tackle; 07-13-2012 at 16:31..
|
|
|
|
|
07-13-2012, 16:54
|
#3
|
|
Senior Member
Join Date: Sep 2002
Location: CA, just outside the United States
Posts: 17,255
|
They click a .bat file to start their command line program.
When I right click and edit it, here's what it says:
set clipper=f99;
cd\
cd usa
net use lpt1 \\frontcounter\epsonLQ
menu.exe
I'm also realizing that one of the computers is on XP Home SP1....  And that there may have been fixes released for this exact issue in SP 3....
__________________
The danger to America is not Barack Obama, but a citizenry capable of entrusting a man like him with the Presidency.
|
|
|
|
|
07-13-2012, 17:03
|
#4
|
|
Senior Member
Join Date: Jul 2000
Posts: 4,364
|
SP1! I wouldn't even bother trying to fix that until you get it up to date. Who knows how many fixes are between SP1 and post SP3 updates.
__________________
Let's see. You drive a Ford, you drink crap beer, you quote Hitler, and you haven't had sex in years. Nope, ain't taking your advice. - BALIFF
|
|
|
|
|
07-13-2012, 17:08
|
#5
|
|
Senior Member
Join Date: Sep 2002
Location: CA, just outside the United States
Posts: 17,255
|
Quote:
Originally Posted by srhoades
SP1! I wouldn't even bother trying to fix that until you get it up to date. Who knows how many fixes are between SP1 and post SP3 updates.
|
I think you're right...also just checked the other PC...I coulda sworn it was SP3, but it's SP2....
If anyone has any bright ideas, I still welcome them, otherwise, yes, I'm going to update them both and see how that goes once they are current.....
__________________
The danger to America is not Barack Obama, but a citizenry capable of entrusting a man like him with the Presidency.
|
|
|
|
|
07-13-2012, 17:10
|
#6
|
|
Senior Member
Join Date: Sep 2002
Location: CA, just outside the United States
Posts: 17,255
|
Any ideas though why it would suddenly just stop working?
I know that's the 32 trillion dollar question with computers, but still....
__________________
The danger to America is not Barack Obama, but a citizenry capable of entrusting a man like him with the Presidency.
Last edited by Drjones; 07-13-2012 at 17:10..
|
|
|
|
|
07-13-2012, 17:15
|
#7
|
|
Senior Member
Join Date: Jul 2000
Posts: 4,364
|
I believe the net use command installs the printer in windows. So when the batch is run a second time it will try and install the printer again and it is already in use. Perhaps adding a net del to the beginning of the script to remove the printer will help.
__________________
Let's see. You drive a Ford, you drink crap beer, you quote Hitler, and you haven't had sex in years. Nope, ain't taking your advice. - BALIFF
|
|
|
|
|
07-16-2012, 09:19
|
#8
|
|
Senior Member
Join Date: Nov 2001
Location: Georgia
Posts: 216
|
__________________
U.S. v. Minker, 350 US 179, "Because of what appears to be a lawful command on the surface, many citizens, because of their respect for what only appears to be a law, are cunningly coerced into waiving their rights, due to ignorance." (Paraphrased)
|
|
|
|
|
07-16-2012, 11:33
|
#9
|
|
Senior Member
Join Date: Jul 2011
Posts: 308
|
Quote:
Originally Posted by Drjones
Any ideas though why it would suddenly just stop working?
I know that's the 32 trillion dollar question with computers, but still....
|
You'll have to look up the syntax, but I would add a line before the net use that deletes the printer. Then on the net use ltp1 line add a /p to the end. It may become disconnected after a set time and /p tells it not to disconnect.
|
|
|
|
|
07-17-2012, 09:06
|
#10
|
|
Senior Member
Join Date: Sep 2002
Location: CA, just outside the United States
Posts: 17,255
|
Quote:
Originally Posted by Stompy
|
yes, I've done that and it helps temporarily, but the problem is that it constantly recurs.
What's happening now is if you send a job to the printer then open the print queue, you'll see it rapidly vascillate between 1, 2, 3 jobs and printing/spooling. They are flashing...does that make sense? Best way I can describe it....
__________________
The danger to America is not Barack Obama, but a citizenry capable of entrusting a man like him with the Presidency.
|
|
|
|
|
07-17-2012, 12:42
|
#11
|
|
Senior Member
Join Date: Dec 2008
Posts: 1,377
|
Reads like you need to edit the script, bat file, and kill the spool and delete the printer mount first.
__________________
It it's not on fire,
It's a software problem.
|
|
|
|
|
07-17-2012, 16:51
|
#12
|
|
Senior Member
Join Date: Sep 2002
Location: CA, just outside the United States
Posts: 17,255
|
Quote:
Originally Posted by Linux3
Reads like you need to edit the script, bat file, and kill the spool and delete the printer mount first.
|
Thanks, can you provide a little more guidance as to how exactly to do that? The language, etc.....
__________________
The danger to America is not Barack Obama, but a citizenry capable of entrusting a man like him with the Presidency.
|
|
|
|
|
07-18-2012, 09:58
|
#13
|
|
Senior Member
Join Date: Dec 2008
Posts: 1,377
|
Quote:
Originally Posted by Drjones
Thanks, can you provide a little more guidance as to how exactly to do that? The language, etc.....
|
Sorry,
I could easily do it in bash, csh, T shell scripting but I don't have any Windows systems to try out writing batch files.
You have the file used to print right?
Google around for information on killing network spoolers and printer mounts.
http://social.technet.microsoft.com/...2-2d9af0967d23
Save your existing print file and then edit a copy with the print text to unmount the network attached printer and spooler first then run the rest of the script.
__________________
It it's not on fire,
It's a software problem.
|
|
|
|
|
Sponsored Links
|
Advertisement
|
|
|
| Thread Tools |
|
|
| Display Modes |
 Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -6. The time now is 00:03.
|
|
|
