Issues Printing During Bartender Upgrade Migration
Sorry about the title not really sure how to summarize this.
Our setup has Navision sending jobs to two servers, both are Windows 2003 one is an older server running 7.72 and the other is a newer server running 9.3 SR2. The software is setup with the Commander service feeding jobs to Bartender. We are trying to migrate completely to the newer server, but we are having issues with indivdual printers ceasing to work or causing others to stop working during the migration. We have a mix of networked and LPT printers including HP Laserjets, Zebra XiII and XiIII in all sorts of variants. When the printers cease to function we can see the jobs, go into the printer queue and very quickly disappear. Sometimes pausing commander and letting the jobs pile up can make it work again. We also sometimes have a hung Commander service or have to restart the print spooler.
We have cleared out our Zdesigner drivers uninstalling them from the system.
All our Zebra drivers are on version 7.1.9 on the new printer.
I don't have any excessive cpu usage or memory use most of the time, although sometimes a rundll32.exe runs amok and has to be killed.
We have checked our Bartender history but we don't see any obvious errors.
Bartender support suggested looking at our Heap setting, but I would think Windows would log an error if that was an issue.
We have looked at the windows error log and I have not seen any obvious clues.
On our old server some of the printers were setup with Zebranet ports, but I'm not sure what the advantage to that would be. (Update: I talked to Zebra and they said that there are no benefits to the Zebranet ports. They don’t think we should have any issues with a TCP/IP connection.)
The last time we experienced the issue was around 9AM this morning when I attempted to migrate another printer. I am going to include some screens from around that time, but I already had Bartender support look at them.
Has anyone encountered anything like this or have any suggestions to try?
[attachment=210:Bartender Error Log.JPG]
[attachment=212:Zebra Server Error Log.JPG]
[attachment=211:Zebra Server Error Log Part 2.JPG]
Our setup has Navision sending jobs to two servers, both are Windows 2003 one is an older server running 7.72 and the other is a newer server running 9.3 SR2. The software is setup with the Commander service feeding jobs to Bartender. We are trying to migrate completely to the newer server, but we are having issues with indivdual printers ceasing to work or causing others to stop working during the migration. We have a mix of networked and LPT printers including HP Laserjets, Zebra XiII and XiIII in all sorts of variants. When the printers cease to function we can see the jobs, go into the printer queue and very quickly disappear. Sometimes pausing commander and letting the jobs pile up can make it work again. We also sometimes have a hung Commander service or have to restart the print spooler.
We have cleared out our Zdesigner drivers uninstalling them from the system.
All our Zebra drivers are on version 7.1.9 on the new printer.
I don't have any excessive cpu usage or memory use most of the time, although sometimes a rundll32.exe runs amok and has to be killed.
We have checked our Bartender history but we don't see any obvious errors.
Bartender support suggested looking at our Heap setting, but I would think Windows would log an error if that was an issue.
We have looked at the windows error log and I have not seen any obvious clues.
On our old server some of the printers were setup with Zebranet ports, but I'm not sure what the advantage to that would be. (Update: I talked to Zebra and they said that there are no benefits to the Zebranet ports. They don’t think we should have any issues with a TCP/IP connection.)
The last time we experienced the issue was around 9AM this morning when I attempted to migrate another printer. I am going to include some screens from around that time, but I already had Bartender support look at them.
Has anyone encountered anything like this or have any suggestions to try?
[attachment=210:Bartender Error Log.JPG]
[attachment=212:Zebra Server Error Log.JPG]
[attachment=211:Zebra Server Error Log Part 2.JPG]
0
-
Just to clarify...
We have the drivers installed for almost all our printers on both the new and old servers. Then we just tell Navision to point at one server or the other. When we point some printers or too many printers at the new server (not really sure what is acting as the trigger) it causes printers to stop printing. Sometimes the printer that stops working is the printer we just moved and sometimes it is other printers.0 -
Update: During our troubleshooting Wednesday it seemed like one of our problematic printers would work when we had Commander in application mode but not in service mode. We were hoping to use that as a workaround. Last night we setup a service account and ran Commander in application mode. I left Zebra 29 pointed at the server as I know it’s consistently failed. About 30 minutes to an hour after I did this and left work I received a call that Zebra 29 had stopped working.
I am hoping Seagull Scientific can tell me why the workaround failed, I will keep you updated.0 -
We had tried adding and removing printers before uninstalling the Zdesigner drivers. Now after uninstalling the Zdesigner drivers I removed and readded all the printers. So far it seems to be working... 0
Please sign in to leave a comment.
Comments
3 comments