Skip to content

PrintNode Connector

PrintNode Update Printers does no longer work

Viewing 3 posts – 1 through 3 (of 3 total)
  • Author
    Posts
  • #8160
    Bernhard K.

    Hello,

    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:
    32c952a1-cc5b-445e-9279-0e594efdd38f

    Application Insights session ID:
    26603156-9834-41ba-9865-757e015b30e7

    Client activity id:
    80bd63ac-54d3-40bf-a9de-351d701ffed0

    Time stamp on error:
    2022-11-22T12:19:35.1722683Z

    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

    #9345
    Travis P.
    Insight Works
    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.
    #9347
    Bernhard K.

    Thank you, this was the error

Viewing 3 posts – 1 through 3 (of 3 total)
  • Sign in below to reply.