Home Forums PrintNode Connector PrintNode Update Printers does no longer work

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • Bernhard KloibmüllerBernhard Kloibmüller
      Post count: 7


      we have a big problem with the PrintNode Connector since yesterday we had the problem that sometimes PrintNode could not print an a printer. After setting up a new print server we have now the problem that we cannot update the printers from printprint node.


      we receive this error:

      Unable to convert from Microsoft.Dynamics.Nav.Runtime.NavJsonToken to Microsoft.Dynamics.Nav.Runtime.NavJsonObject.

      Internal session ID:

      Application Insights session ID:

      Client activity id:

      Time stamp on error:

      AL call stack:
      “IWX PrintNode Printer Mgt.”(CodeUnit 70097841).SetupPrintNodePrinters line 55 – Insight Works PrintNode Connector by Insight Works
      “IWX PrintNode Conn. Printers”(PageExtension 70097841).”IWXRefreshPrintNodePrinters – OnAction”(Trigger) line 4 – Insight Works PrintNode Connector by Insight Works


      Is there anything we can do to use the printer again? Thank you in advance

      Best Regards

      Bernhard Kloibmüller

      Travis PlettTravis Plett
        Post count: 160
        This message means you have an invalid printer defined in your PrintNode app. Log into your PrintNode account and remove inactive printers so only valid printers remain: https://api.printnode.com/app/devices
        Then click on “Update PrintNode Printers” on the PrintNode Printers list to refresh it in Business Central.
        If that does not work, save the Printer Selection table (78) with a config package and then take the “Load/Reload PrintNode Printers” action from the PrintNode Setup page. This will wipe out all old settings and re-build the list from scratch, so the printer selections will need to be applied from the configuration package or else created manually.
        Bernhard KloibmüllerBernhard Kloibmüller
          Post count: 7

          Thank you, this was the error

        Viewing 3 posts - 1 through 3 (of 3 total)
        • You must be logged in to reply to this topic.