You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm troubleshooting a really odd issue with DYMO Connect 1.4.6.37.
Sometimes, the DYMO service will ignore the spool selection. This seems to only occur if:
The DYMO LabelWriter 450 Twin Turbo has been plugged in since the system started up
DYMO Connect desktop application has been used to print a label
In this case, the label prints dispatched via the browser will always print to the most recent spool used by DYMO Connect, ignoring the TwinTurboRoll value set in printParamsXML (see screenshots). No errors are raised by the software or the Windows print system, including out-of-paper errors.
Reproducing this issue is troublesome, but we're seeing it on a test installation as well as production systems. Interestingly, the "use both rolls" option in DYMO Connect is off.
I have been able to resolve this issue in my test installation by restarting the computer, but this is inconvenient, especially since I haven't identified what causes the system to break.
My hypothesis is that under certain conditions, the printer is set to use spool "Auto" globally. How do I go about resolving this permanently?
The text was updated successfully, but these errors were encountered:
I'm troubleshooting a really odd issue with DYMO Connect 1.4.6.37.
Sometimes, the DYMO service will ignore the spool selection. This seems to only occur if:
In this case, the label prints dispatched via the browser will always print to the most recent spool used by DYMO Connect, ignoring the TwinTurboRoll value set in printParamsXML (see screenshots). No errors are raised by the software or the Windows print system, including out-of-paper errors.
Reproducing this issue is troublesome, but we're seeing it on a test installation as well as production systems. Interestingly, the "use both rolls" option in DYMO Connect is off.
I have been able to resolve this issue in my test installation by restarting the computer, but this is inconvenient, especially since I haven't identified what causes the system to break.
My hypothesis is that under certain conditions, the printer is set to use spool "Auto" globally. How do I go about resolving this permanently?
The text was updated successfully, but these errors were encountered: