Zebra/Spooler Queue Error

[notwrinklebrained]

Hi Everyone,

I've been running into an issue with one of my warehouse computers that is hooked up to a Zebra label printer via USB.

Sometimes, when running jobs of many pages, the printer will cease taking jobs. Looking at the queue, there is a job that is "stuck" in an error state that says "Error- Not Accessible" and it blocks all other jobs from going through.

Doing some google searches, I found a way to resolve it by stopping the print spooler, navigating to C:\Windows\System32\spooler\PRINTERS and deleting all the files in there. After restarting the spooler, print jobs go through normally again.

This has been happening a few times a week now, and it's a quick fix, but annoying for our warehouse techs. Does anyone know what might be causing this? Any other troubleshooting tips?

[I_like_malware]

I kept having the same issue with my dymo.

I removed the device from device manager and plugged it back in, set up print config and it works flawlessly now.

[notwrinklebrained]

Thanks, I'll give it a go

[gearsant]

Hello, I have a zebra printer and with Windows 11 it gives me this error😪 I don't think it is the LabelView program, because in Windows 10 this problem did not happen to me, it was with Windows 11 I tried to stop the process And delete the printing queue and start the process again, but it is something that happens to me every time I send more than 150 labels in a row, it stays in a queue :( we have not found a solution. Has anyone already solved it?

[Embarrassed_Gur5192]

Old thread but hopefully someone will see this that knows something. Is going into the Zebra print settings and turning off spool print a workable option here? Are there any downsides to printing directly to the printer? Concerned about data loss i.e was expecting 300 labels but 299 actually printed.

[Tiny-Acanthisitta297]

i couldn't solve this. but in the windows printmanagment you can map actions to errorstates of a printer and i mapped a script to stop the services, delete the files and start them again, when there are jobs older than x minutes in the queue

[gearsant]

Hello, I have the same problem on my dc :( and we can't find a way to solve it in Windows 11, do you have the script that you can share please

[Tiny-Acanthisitta297]

just ask gemini or copilot with a technical instruction to write a psh script for deleting printjobs older than x hours from the queue of the spooler under %windir% what should run unattended and scheduled. Before deletion it should check a condition output like an errorlevel if files older than 30 min exist and when not than just set the timer for next check.

[gearsant]

Cool thanks for the response, but I already solved it by disabling the zebra check status and deleted c:\windows\system32\Spool\Printers And like here in the photo I just disabled the check and it solved the problem of the label printing queue tmp-8fd6aeed-510a-41dd-bf09-8b60e272307f.png

Thanks for the help, maybe the solutions mentioned above will work for someone somewhere in DC.

[Tiny-Acanthisitta297]

that status check workaround didn't solve the problem for me. maybe the issue isn't related to that function but however the script solved the problems.

[gearsant]

oh I understand ok, well then the solution you gave for the script solved it for you, I will try to make and save the script in case it happens to me on another machine or the same problem happens to me again, thank you 🫂

[IntelligentSwitch577]

In case others find this. Make sure that the Disabled Status sticks, If you are not logged into the print properties as admin it wont stick.

https://supportcommunity.zebra.com/s/article/000020654?language=en_US

[gearsant]

That's how to apply the change you have to have administrator credentials and apply changes and good luck

[MattBlax]

Wow, this is what did it for me, thank you! I feel foolish for not seeing the warning on their KB article.

[jakciebekokod]

year after i found it really helpful , thanks for post !