May 302017
 
The latest release of DLS is now available for customers that have been experiencing Chrome security issues with the previous release!

You can download the Windows release via the following link:

Windows Download link:
http://labelwriter.com/software/dls/win/DLS8Setup.8.6.2.658.exe

The Mac OS X version will follow within the next few days.

  54 Responses to “New DLS 8 released! (This fixes security certificate issue for Windows)”

  1. Thanks! Seems to work fine.

  2. Thanks Jeff,

    This did the trick.

  3. Do we need a new framework to go along with this?

    • You should be able to just install this and carry on. If you have any problems, uninstall everything and reinstall again.

  4. Seems to work now thank you finally for the reply

  5. Fixed! Thank you, Jeff!!

  6. Am I the only one that get error while trying to print?
    https://localhost:41951/DYMO/DLS/Printing/PrintLabel
    Request URL:https://localhost:41951/DYMO/DLS/Printing/PrintLabel
    Request Method:POST
    Status Code:400
    Referrer Policy:no-referrer-when-downgrade

  7. Here is the response:
    “[0] Could not load file or assembly ‘MDYMOBarcode.dll’ or one of its dependencies. The specified module could not be found. [1] Exception has been thrown by the target of an invocation. [2] There is an error in XML document (28, 4). [3] There is an error in XML document (28, 4). [4] There is an error in XML document (28, 4). [5] Unable to load label template “

    • Try uninstalling everything (including older versions) and re-installing. Also, please post your issue only once as multiple posts only make it more difficult to track.

      • We’re getting the exact same error message on one of our Windows PCs(Win 10 Home, build 10586.962).

        It does not matter whether we’re trying to print from a HTTP or HTTPS page.

        We’ve tried uninstalling DYMO and then installing either 8.6.1 or the new 8.6.2 version to no avail.

        Even the “Print me that label”(http://www.labelwriter.com/software/dls/sdk/samples/js/PrintMeThatLabel/pl.html) demo page gives the same error message: “There is an error in XML document (1, 559)” — you can see that the line/column numbers change depending on the label template being used, but they all return this error message.

        Please advise.

  8. v8.6.2.658 does appear to resolve the problem with Chrome accepting the certificate, but with both v8.6.2.658 and v8.6.1, the sample page (below) fails to print.

    Dymo Preview and Print Label Sample

    The browser pops up a window that says “Failed to execute webservice command: 400: Bad Request.

    Looking at the event in the Chrome Developer Tools, I can see the following response:
    “[0] Root element is missing. [1] PrintTicket XML is not well-formed. Root element is missing. [2] Printing Error: PrintTicket XML is not well-formed. Root element is missing. ”

    But the Form Data for the request shows that labelXml does have valid XML which does have a root element.

      • There is a known bug in the PrintMeThatLabel sample. I can print once from it but then it stops working until I reload the page.

        The PreviewAndPrintLabel sample works for me. What error message are you getting?

    • Please provide a link to the sample in question.

      • Error occurs with either of the Dymo provided samples (links in previous reply).

        The error is as documented above – 400 status code and result message indicating the XML is not well formed, even though the POST content has well-formed XML.

        Error occurs the first time attempting to print after loading the sample page.

      • Error occurs with Chrome or IE on Windows 8.1. I can print labels with the DYMO app running on the desktop. The printer is attached to a DYMO network adapter.

    • FYI – I have a client with a production application where they’re printing mailing labels many times a day. They’re stuck using the older version of DYMO software that doesn’t support Chrome, and they’re forced to use IE when they want to print labels.

    • FWIW, both my production app and the DYMO samples work from Chrome and IE on Windows 7. I’ll try it from Windows 10 later today.

      • Tried a dev version of my production app and the DYMO samples from Chrome and IE from Windows 10, and it all worked. So it looks like the problem is just on Windows 8.1. Have you been able to replicate the problem?

        • I created a Windows 8.1 virtual machine and installed DLS. The “Add Printer Utility” app works fine. When you attempt to install DLS, do you get a dialog that informs you Bonjour needs to be installed?

          As a test, I uninstalled Bonjour and tried to run the utility again. It crashes as expected. We will investigate this a bit further but so far we haven’t been able to replicate it anymore.

          • Bonjour service is installed and running. I did not get an error about that.

  9. Hi Dymo,

    Can’t find a contact address for SDK issues, so I’ll try here. Feel free to refer me elsewhere. I noticed the dymo javascript SDK is using a self signed certificate and requiring end users to apply workarounds to get this certificate to work.

    You could fix this issue for all your users without having to resort to self-signed/installing certificates the following way:

    – create a hostname ‘connect-local.labelwriter.com’ or something similar in your DNS, pointing to 127.0.0.1
    – get a DV certificate using email validation (things like letsencrypt obviously won’t work)

    you can get a certificate with five years of validity for less than $100 with eg. comodo.

    we’ve had to solve the problem for a similar situation, and this pretty much solves the certificate issue in a crossplatform way without bugging your users. and with a 5 year certificate, users can go a long time without requiring a software update.

    you can contact me if you want more info on how to do it, as I’d also love not to have to bother my customers about messing with certificates (and I definitely don’t want them to learn how to ‘work around’ SSL certificate issues)

  10. We are getting the message “None of the ports were configured to use SSL certificate” when clicking diagnose.

  11. Thank you for the update, Chrome appears to be printing again. However, I am still getting the following error when using FireFox, any ideas?

    “Dymo Label framework doesn’t appear to be running”

  12. Hi, I’m getting the same error on two different machines trying to print from powershell.

    The code looks like this
    #Badge
    $badgefile = "$PSScriptRoot\badge\badge.label"
    $runtime = "$PSScriptRoot\required\DYMO.DLS.Runtime.dll"
    $framework = "$PSScriptRoot\required\DYMO.Label.Framework.dll"
    $common = "$PSScriptRoot\required\DYMO.Common.dll"
    [reflection.assembly]::LoadFile($runtime)
    [reflection.assembly]::LoadFile($framework)
    [reflection.assembly]::LoadFile($common)
    #$printername = [DYMO.Label.Framework.Framework]::GetLabelWriterPrinters() | select -ExpandProperty name
    $label = [DYMO.Label.Framework.Framework]::Open($badgefile)

    function Create-Badge($name, $company, $chost){

    $label.SetObjectText("TEXT","$name")
    $label.SetObjectText("TEXT_1","$company")
    $label.SetObjectText("TEXT_2","$chost")
    #Print $label
    $label.Print("DYMO LabelWriter 450")

    }

    This is the error I’m getting,

    Exception calling "Print" with "1" argument(s): "Object reference not set to an instance of an object."
    At C:\Users\*******\test_3.ps1:26 char:1
    + $label.Print("DYMO LabelWriter 450")
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : NullReferenceException

    Would be thankful for any advice you could give me.

    • Do you have any other error output?

      We don’t have any PowerShell samples to try, but have you tried running our other samples to make sure your DLS install is working correctly? If you can send me a link to somewhere I can download your project I can try running it myself.

      • That’s the error output I get, the code I posted is the full code, run the script and call the function: Create-Badge(“John Doe”,”DYMO CORP”, “Whatever”)

        This is what happens from start til end. (I added some * for privacy)


        PS C:\*>.\DymoCreateBadge.ps1

        GAC Version Location
        --- ------- --------
        False v4.0.30319 C:\*\required\DYMO.DLS.Runtime.dll
        False v4.0.30319 C:\*\required\DYMO.Label.Framework.dll
        False v4.0.30319 C:\*\required\DYMO.Common.dll

        PS C:\*> Create-Badge("John Doe", "Dymo Corp", "Whatever")

        Exception calling "Print" with "1" argument(s): "Object reference not set to an instance of an object."
        At C:\*\DymoCreateBadge.ps1:26 char:1
        + $label.Print("DYMO LabelWriter 450")
        + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : NullReferenceException

        I’ve tried your JS page examples and it’s possible to create and print labels from them.
        How can I know if the framework is correctly installed, and it seems suspicious to me that I would get the exact same error on both Win10 and Win8.1.

  13. Hi Dymo Dev team, the actual customer support (at the dymo labelwriter end user side) seems to be very hit or miss as to whether or not the person you call and end up talking to is even aware that the Dymo web service exists. I had a client contact me to see what was wrong with our site (nothing wrong with our site, they were using chrome and after switching to edge had no further issues) and they told me the dymo tech they talked simply remote accessed their machine, went into the DLS 8 and printed a label and then told them that it must be our site that was broken. They dont even seem to know about the labelwriter page you guys have set up for testing the web service which is invaluable for trouble shooting http://labelwriter.com/software/dls/sdk/samples/js/PrintMeThatLabel/pl.html
    A baseline knowledge of what your software is actually capable for your support staff would be great. We try to let our clients know as soon as any issues that we are aware of with the software arise so that we can direct them to a different solution

    • Hi David,

      Thanks for your reply. The customer support team to which you are referring is geared towards end-user/consumer inquiries (i.e., my printer is jammed, what is a USB cable, etc.). They are not trained in SDK-related issues.

      This blog is where you need to go for SDK-related inquiries. You can alternatively email SDKReply@newellco.com should you prefer email-based support.

      I will, however, put in a request to train them enough to refer customers to our support for issues outside of their scope.

      As an FYI, there is not only a workaround for your Chrome security issues, but a new release of DLS that should cure them entirely:

      http://developers.dymo.com/2017/05/04/google-chrome-not-secure-warning-fix-is-on-the-way/

      I hope that helps.

      Regards,
      dymojeff

  14. It’s been “A few days” (14) – Any update on MacOSx?

  15. Any Mac fix yet?

  16. The Dymo site still lists 8.6.1 as the latest version available for download, both for Win and OS X:

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

    Is 8.6.2 a general-availability release? Is it going to be listed on the above site? Thanks!

 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)