# Zebra Label Printer Issues

**URL:** <https://the.fmsoup.org/t/zebra-label-printer-issues/2907>\
**Category:** Questions\
**Tags:** zebra\
**Created:** [May 13, 2022, 3:41am UTC](https://the.fmsoup.org/t/zebra-label-printer-issues/2907 "2022-05-13T03:41:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![steverichter](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/steverichter/32/1022_2.png) [@steverichter](https://the.fmsoup.org/u/steverichter)\
**Post date:** [May 13, 2022, 3:41am UTC](https://the.fmsoup.org/t/zebra-label-printer-issues/2907/1 "2022-05-13T03:41:14Z")

</div>

I’m running FMS19 (AWS) and FMP19 (Win 10). My Win 10 machine developed some intermittent overheating issues so I replaced it with another Win 10 machine.

Immediately, my Zebra 410 label printer stopped working. I can successfully print a test from Windows, so I know the hardware is connected properly. (I made no changes to scripts, etc.)

When I now print from FMP19, I can see the Zebra power light blinking green, which indicates the printer is receiving data; however, nothing prints.

Any suggestions on where to begin troubleshooting?

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [May 13, 2022, 11:23am UTC](https://the.fmsoup.org/t/zebra-label-printer-issues/2907/2 "2022-05-13T11:23:08Z")

</div>

Common denominator: Windows. ☹

Seriously though, hope you get it fixed.

I use a Dymo 450 and have never had a hitch. Way back when, I was told that this was the printer that FMI used internally.

---

<div class="post-metadata">

**Author:** ![harvest](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/harvest/32/231_2.png) [@harvest](https://the.fmsoup.org/u/harvest)\
**Post date:** [May 13, 2022, 1:18pm UTC](https://the.fmsoup.org/t/zebra-label-printer-issues/2907/3 "2022-05-13T13:18:26Z")

</div>

did you try to write a new script in a new local FileMaker file just for testing the printer with a fresh environment/setting - sometimes cached printing settings persist within the file and can only be reset by exchanging the printer related scriptsteps when opened locally

---

<div class="post-metadata">

**Author:** ![steverichter](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/steverichter/32/1022_2.png) [@steverichter](https://the.fmsoup.org/u/steverichter)\
**Post date:** [May 13, 2022, 1:22pm UTC](https://the.fmsoup.org/t/zebra-label-printer-issues/2907/4 "2022-05-13T13:22:29Z")

</div>

After further troubleshooting, I believe the issue is with FileMaker’s “print setup” script step. I have the label size set to 1x2, but that setting is being overwritten with dimensions larger than the actual label, causing the printer not to print.

SOLVED: Inexplicably, the print setup script step was changed to a label size far larger than the actual label. After I updated the script everything returned to normal.

---

<div class="post-metadata">

**Author:** ![Daniel](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@Daniel](https://the.fmsoup.org/u/Daniel)\
**Post date:** [May 15, 2022, 1:23am UTC](https://the.fmsoup.org/t/zebra-label-printer-issues/2907/5 "2022-05-15T01:23:27Z")

</div>

I've got a vague memory that some of the printer setup details get stored in the Windows Registry. That could be the reason for the print setup script step changing without user input.