73 lines
2.7 KiB
Markdown
73 lines
2.7 KiB
Markdown
# 📦 Barcode Printing Issues — Troubleshooting Tree
|
|
|
|
## Step 1: Identify the Printing Path
|
|
- [ ] Is the label supposed to print **directly from Epicor (SSRS/Edge Agent)**? → Go to **Path A**
|
|
- [ ] Or is it sent to **Azure share → Bartender Integration Service**? → Go to **Path B**
|
|
|
|
---
|
|
|
|
## 🔹 Path A — Epicor (SSRS → Edge Agent → Printer)
|
|
|
|
### Step 2A: Did the SSRS report generate correctly in Epicor?
|
|
- [ ] Yes → Go to Step 3A
|
|
- [ ] No → Check report parameters, dataset, or permissions in Epicor
|
|
|
|
### Step 3A: Did the Edge Agent receive the print job?
|
|
- [ ] Yes → Go to Step 4A
|
|
- [ ] No → Check Edge Agent service status on the client/server
|
|
- Restart Edge Agent service if stopped
|
|
- Review logs in `C:\ProgramData\Epicor Software Corporation\EdgeAgent\Logs`
|
|
|
|
### Step 4A: Was the job sent to the correct printer?
|
|
- [ ] Yes → Go to Step 5A
|
|
- [ ] No → Verify printer mapping in Epicor → Company/Plant/Workstation settings
|
|
|
|
### Step 5A: Is the printer online and reachable?
|
|
- [ ] Yes → Check Windows print queue for stuck jobs
|
|
- [ ] No → Power cycle printer, verify network connectivity, driver status
|
|
|
|
---
|
|
|
|
## 🔹 Path B — Azure Share → Bartender Integration Service → Printer
|
|
|
|
### Step 2B: Did Epicor export the file to the Azure share?
|
|
- [ ] Yes → Go to Step 3B
|
|
- [ ] No → Verify Epicor report style is set to **Export**, confirm user has write access to share
|
|
|
|
### Step 3B: Did the file appear in the watched folder?
|
|
- [ ] Yes → Go to Step 4B
|
|
- [ ] No → Check Azure storage permissions, sync status, or network connectivity
|
|
|
|
### Step 4B: Did the Bartender Integration Service pick up the file?
|
|
- [ ] Yes → Go to Step 5B
|
|
- [ ] No →
|
|
- Check Bartender Integration logs in `C:\ProgramData\Seagull\Bartender\Logs`
|
|
- Confirm the integration service is running
|
|
- Validate file naming convention matches trigger rules
|
|
|
|
### Step 5B: Was the file processed into a print job?
|
|
- [ ] Yes → Go to Step 6B
|
|
- [ ] No → Check Bartender template config, action rules, and variables
|
|
|
|
### Step 6B: Was the job sent to the correct printer?
|
|
- [ ] Yes → Go to Step 7B
|
|
- [ ] No → Confirm Bartender printer mapping settings
|
|
|
|
### Step 7B: Is the printer online and reachable?
|
|
- [ ] Yes → Check Windows print queue for stuck jobs
|
|
- [ ] No → Power cycle printer, verify network connectivity, driver status
|
|
|
|
---
|
|
|
|
## 🚩 Escalation Points
|
|
- **SSRS failures** → ERP/report developer
|
|
- **Edge Agent service errors** → Epicor admin / IT infra
|
|
- **Bartender misconfigurations** → automation admin / IT infra
|
|
- **Persistent printer errors** → local IT / vendor support
|
|
|
|
---
|
|
|
|
## 🧭 Notes
|
|
- Keep a **sample successful job log** for both Epicor and Bartender as a baseline.
|
|
- Document **which printers use which path** (Edge Agent vs Bartender).
|