Apr 242018
 

UPDATE

A new version of DLS is available that resolves this issue. This will need to be installed on any client machine experiencing the slow printing issue. You can download it here:

 http://download.dymo.com/dymo/Software/Win/DLS8Setup.8.7.1.exe

UPDATE 2

The above version of DLS is now live on DYMO.com for all regions.

http://www.dymo.com/en-US/online-support/dymo-user-guides

Since 4/23/2018 all users of the windows version of our SDK have been experiencing a 10-15 second slowdown. The issue can also cause performance issues when opening label files in DLS.  This appears to be caused by our code attempting to contact 128.30.52.100 (http://www.w3.org/1998/XMLSchema)  in order to validate each label before printing.

We have identified a fix for this issue and we are currently expediting a test cycle so we can release a patch as soon as possible.

Until the actual fix goes out, users can alleviate this slowdown by preventing this call.  We have seen success with two methods thus far.

  1. Prevent connections to 128.30.52.100 (http://www.w3.org/1998/XMLSchema)
  2. Use the windows defender firewall to prevent DYMO.DLS.Printing.Host.exe from making outbound connections.

 

We apologize for the inconvenience, and will update this post as soon as the situation has been resolved.

-Regards,

DYMO Team

  54 Responses to “Recent issues with slow printing”

  1. Thank you for posting this!

  2. To be clear, this issue also impacts DLS.exe. If you launch DLS, it takes a long time to load all your saved labels. Initially, support was saying it was having issues accessing the folders. However, DLS is also trying to validate. If you also setup a block for DLS.exe and then launch it, your labels will load instantly.

  3. Potentially a redundant comment but this is also effecting the MS Word add-on. Rather than a 10-15 second delay my users were seeing 60 second plus pause between clicking the add-on and the print dialog appearing. Blocking the IP was successful.

    • Hi. I’ve been having the 60 second plus issue too. I downloaded the new version – as stated above. Now it won’t print at all. I have no idea how to block that IP. Can you give me any tips please? Thanks so much!

      • Hi Karin,

        You might try Uninstalling DLS before Installing the latest version. We have also heard of a couple of instances where a reboot was necessary after the upgrade.

        Ron

  4. Hi,
    I have started to hear complaints from my clients about slowness when printing. I just check my code and it’s taken 15 seconds when I make this call
    DYMO.Label.Framework.Label.Open(template);

    Is this also related?
    Regards
    Hugo

  5. This also seems to be affecting the Javascript SDK as well. I just started receiving multiple reports from clients about a delay before printing and have experienced this in my own testing.

  6. Any ETA on the fix, all of our customers affected because of this

  7. Any update on when this will be fixed?

  8. Simple fix is to put this line in the file at `c:\windows\system32\drivers\etc\hosts`

    127.0.0.1 http://www.w3.org

    This redirects all DNS requests for w3.org to go to the local machine, which should immediately deny the connection request (unless you have an http server listening on 127.0.0.1:80)

  9. Thanks for updating us. Our community uses the DYMO almost exclusively over at http://www.accelerlist.com. HOw can we get a line of communication to your dev team? Thanks.

  10. are we close to a real resolution?

  11. How to: “Prevent connections to 128.30.52.100”?

  12. adding to the hosts file fixed the issue for us

  13. Hi guys, thanks for your quick action on this and you’re clear, open communication. If only every supplier was this good.

    I’ve managed to get my users working with the firewall fix, however we do have an issue, which may or may not be related to this.

    User logs into windows, prints fine.
    Someone else comes along uses Switch User to log in. Labels don’t display or print for them.
    It’s as if the first user is locking something.

    May not be related and just coincidentally reported after the firewall work-around went in.

    • Hi Mike,

      I think this issue is unrelated, however we are working on a fix for this issue as well. I would look for a release on this issue in about a month.

      Ron

  14. add a new line
    127.0.0.1 http://www.w3.org
    to the file `c:\windows\system32\drivers\etc\hosts`
    is working fine for me also, thanks

  15. No http:// , why automatically add http:// to my comment?

  16. Does the updated DLS require uninstalling, rebooting, and then reinstalling the new version, or can it be simply installed over the existing version?

  17. Thanks for the fix! We’ve tested it on our end and labels are printing much faster!

    On another note, the download is REALLY slow. We’re getting multiple reports of slow or timed out connections in trying to download the update. In my own experience, it took nearly an hour to download the 162MB file on a 100Mb/s cable internet connection.

    For comparison, it takes about 30 seconds to download a 200MB file from https://www.thinkbroadband.com/download

  18. How does this impact me when I use dymo printer for address labels and I DO want to verify the address?

  19. Tried installing the latest 8.7.1 update on a client machine but my custom program written in previous SDK version 8.6.1 got an error when it tries to look for the default Dymo printer (a Twin Turbo 450). I am guessing will have to wait for new SDK to recompile.

    • there were no changes to the code that finds/selects printers. You may want to make sure your printer is still installed. You also may try unplugging your printer (from the computer), deleting your printer (in the control panel) and plug the printer back in. This should do the trick.

      Regards,
      Ron

  20. You REALLY need to put this on a CDN somewhere. Or put up a torrent for it.

    I download it once to the webserver, and then fetch it there for each client.

  21. Would have been nice to have known this before this morning (Sunday). We check in 100 children and 80 workers every Sunday using self checkin. We have 9 checkin stations. Today was an absolute disaster trying to figure out what was going on. NOW that the rush dealing with telling everyone to be patient is over, I had time to search and find this post.

    SO, will the problem be resolved BEFORE next Sunday? Or, do I need to try to patch all 9 computers, only to have to do it again later???

    • Hi John,

      Sorry you had this result… The patch has been released and should work just fine for you now.

      Regards,
      Ron

  22. Hi DYMO Developers!

    I was wondering if you were going to release updated Android SDK code for your new Wireless LabelWriter. I am developing an app that features your new Wireless LabelWriter, but I am having difficulties writing code that will print to it. Please respond as soon as you can. I look forward to any and all updates on the Android code.

    Thanks

    • Hi Jacob,

      An Android (and iOS) SDK release is on our roadmap but I don’t have an approximate time for release.

      Ron

  23. THANK YOU !!!!
    Tested and it works with our cloud app.

    We appreciate the patch.

  24. Wow!
    that fixed it.
    Thanks

  25. Any update yet?

  26. Have u find permanent solution yet?
    i am looking for permanent solution..
    please tell me ETA solution.

  27. Please next time write a new post, so I can get notified thru my RSS reader and not be forced to check the website for updates. Thanks :)

  28. Any update regarding the issue where the installer process spawns a new process and terminates before the installation has completed? I posted about this previously here. Another user has generously supplied a workaround but it’s not an ideal solution, especially since it seems the installer may require a restart and there is no way to retrieve the exit code to determine whether that is the case.

  29. Should this fix completely eliminate the increased (~15s) the wait time on DYMO.Label.Framework.Label.Open() calls? It seemed to work on my machine, but when I deployed to one of my clients (I halted deployment after the first), the wait time remained and now I’m getting a NullReference Exception when I call .Print(). I’ve tried disconnecting the printer, uninstalling, reinstalling, rebooting, etc with no change. I’m afraid to roll it out to my other deployments for fear that the same thing will happen. This is game-breaking for me… Anyone else still having slowdown issues or issues with the NullReference Exception on .Print calls?

    • Hi Eric,

      If your custom app uses the javascript SDK, it may be necessary to reboot the client computer after installing the latest version of DLS on that machine.

      Before taking any further action, I would recommend printing a label from DLS on the client machine. Also, confirm the DLS version from the about box.

      Ron

  30. Can the version be detected from javascript?

    if (dymo.sdk.version<80701) {alert("Dymo driver need to be upgraded"}

  31. Hello DYMO, one of clients did a Microsoft Windows Update today, and the DYMO 450 Turbo has stopped printing. Says the printer is ‘ERROR State’. The printer is using the latest release mentioned Rain this post. Any ideas on how to fix this ? Thanks in advance.

    • Hi Roger,

      Sorry for the late response…

      Can your user print from DLS to this printer? If not, try unplugging the printer, removing the printer from the control panel, and replugging the printer in. This should get things back to normal.

      Let me know if this does not work for you,

      ron

  32. We have installed the new DYMO exe and we are experience slow printing times… I’m using the Javascript Framework to print the Labels. This happen on some machines not all. Is there anything we can look at to find out why it is slow on some machines??

    • Hi Lonny,

      This was a known problem on an older version of DLS. Make sure all of the machines have the latest DLS installed.

      Let me know if this doesn’t fix the issue.

      Regards,
      Ron

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

(required)

(required)