Saltar al contenido principal

Búsqueda

Búsqueda

Serialization failures

Comentarios

4 comentarios

  • Avatar
    pthane

    The first thing I would suggest is update your version to 2021 R9 and see if that fixes it. 

    What type of printer are you using?  If it has a Seagull driver try amending the text field to use a device font rather than a true type (such as Zebra Trumvirate instead of Arial for a Zebra printer) and try enabling the File>Print>Performance>Allow Serialisation. 

    0
  • Avatar
    Jorge Munarriz

    Hi Peter,

    Thank you for your reply. We are using Cab Squix printers for this label. The text field was using a CAB font, specifically the Cab Swiss font. I've changed the font to anoher CAB one, and then I've printed about 70 or 80 labels with 0 problems. It seems it's working now, but the acid test will be the next monday. I'll tell you the results.

    The Allow Serialisation was already enabled. And we have no manteinance currently, so I'm not able to upgrade to R9.

    You've been very helpful. Best regards,

    Jorge

    0
  • Avatar
    Declan Hynes

    So, I have BarTender 2016, R8 running on Windows 10 print to a Zebra ZT610 running Zebra 2022.2 drivers from Seagull.

    Since the update to KB5039211 we've seen similar issues.
    For our serialisation we start at a high number and count down. We see the number not decrement initially, which is obvious to the print operators.
    We have also seen the number decrement correctly for 200 or 300 labels and then not decrement.

    We have also seen a strange case where data that should be fixed (expiry date) begins to decrement.

    We can only point to the recent Windows update as to have some sort of effect which we have not fully characterised yet.
    Removing the update has stopped the errors, or at least we believe so, as it is being monitored because the errors were not consistent, nor easily reproducible.

    0
  • Avatar
    pthane

    This is sounding more like an issue after the recent security update (something similar happened a few years back that effected a whole bunch of different softwares and Microsoft ending pulling the update and replacing).

    I am guessing Seagull's Tech team are aware but have messaged them directly anyway

    1

Iniciar sesión para dejar un comentario.