LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Graph opens up with error message/missing nodes

    Employee
    Posted 01-05-2012 02:46

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: sderban

    Hello all,

    My graph opens up with the error mesage below.

    Syntax Error
    Near Line 20610
    >> ==7
    >>editor:handle=4f0488144efb38e7
    >>editor:sortkey=4f0488144efb38e7
    Argv[1] = "D:\\RA\\FixedNetwork\\Lavastorm_V2\\4.BV\\Billing Validation.brg"

    After this, screen is displayed with some composite nodes missing.
    These nodes were old nodes that have been saved long ago.

    Please help.


    Samuel


  • 2.  RE: Graph opens up with error message/missing nodes

    Employee
    Posted 01-06-2012 08:09

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Tim Meagher

    Hi,

    Are you able to post the graph such that I can help look into the error.

    If you don't want to upload the graph to a public forum, feel free to send this via Private Message.

    Tim.


  • 3.  RE: Graph opens up with error message/missing nodes

    Employee
    Posted 01-09-2012 14:55

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    It looks like the node name somehow got a <newline> character put in it, which will corrupt the file. If you want to fix this, you can edit the file directly, and remove the newline before the "==7" (near line 20610), so it goes above, on the line that contains "editor:Label="

    If you copy and paste multiple lines of text into the node name, this would cause the corruption you have seen. We have added this detection and prevention in 4.1.6 onward for the 4.1.x branch, and it will also be prevented in 4.5.3 on the new 4.5.x branch.

    Cheers
    Rich