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.  LAE Error Code: brain.node.HierarchicalURI.cpp.114

    Employee
    Posted 05-11-2016 03:59

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

    Originally posted by: lae_errors

    This post has been created for discussion of error code brain.node.HierarchicalURI.cpp.114.

    Please reply to this thread with any description of error conditions, diagnostic information, and recommended resolutions.


  • 2.  RE: LAE Error Code: brain.node.HierarchicalURI.cpp.114

    Employee
    Posted 05-16-2018 02:07

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

    Originally posted by: henk01

    Hello,

    I received the error:
    			
    				Error while starting execution of node Test.DB+Store'
    Error executing node: Node :Test.DB+Store' (handle: 5afbe1c7750e768d) encountered error during initialization
    WARN: invalid port string
    Error Code: brain.node.HierarchicalURI.cpp.114

    ERROR: Node execution terminated while opening i/o streams by error:
    invalid port string
    Error Code: lae.node.executionTerminated
    Some more background information. The "DB Execute" node works fine, I can create a test table, and also insert data into the test table. However the "DB Store" node fails with the above error. The connection used is an ODBC connection to an SQLserver database.

    After experimenting some more, the node works fine when the "DB Service" name is shortened. So for example the "DB Execute" node fails when using "Production_database1" as "DbService", but seems fine when using name "Prod_database1" instead. Does the "DB Store" node truncate the "DB Service" name in any way?

    Best Regards,

    Henk


  • 3.  RE: LAE Error Code: brain.node.HierarchicalURI.cpp.114

    Employee
    Posted 05-17-2018 02:52

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

    Originally posted by: awilliams1024

    Hi Henk,

    We have had a similar issue reported (when integrating with Oracle) which was due to the presence of certain characters in users' passwords. Can you check whether the user password contains special characters such as double quotes, * or #.

    Regards,
    Adrian