We have a network printer (TSC TTP-247) that prints tags typically from the software Bartender – Epicor is compatible with Bartender formats. Our question is the Edge Agent on our server is not allowing a workstation to send print jobs to that printer. Epicor maintains that it is not a problem with the Edge Agent, but that it is a problem with a setting on the server. Our IT people are at a loss to figure out what the issue may be.
Looking for anyone that may have worked through this issue or can give us help figuring out where to turn now. It is the Edge Agent (who is the developer or owner of that product?) Is it a setting on our server?
Thank you for the quick reply - our set up does not include individual workstations set up - not sure if that is a requirement with cloud based SaaS, which we are. But I did check that the printer maint set up for that printer matches our network server, so that box is checked.
We’re on-prem so it will definitely be different. Might want to check in on that other thread I linked - I think someone mentioned cloud with an onprem BarTender scenario
Thank you - it is a printer that works with bartender and we are currently using bartender software to do it by hand…not ideal. We have tried getting help from Epicor as it appears to be a problem with the Edge Agent and some setting on our server.
This is a longshot I suppose…if BarTender’s on a local server (with Kinetic in the cloud) and the printer is local…does the printer need to be shared out for Kinetic (and Edge Agent) to see it?
We are on epicor cloud and have an on-prem windows 10 VM running bartender. We mapped our epicor file share location to that computer. I installed the edge agent on that local server and didnt have any issues. I am still working on testing the labels printing via SSRS to it, but I was able to test print from the edge agent to the label printer without any errors.