LAE

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.unexpectedNodeErrorDuring.

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

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

Originally posted by: Tim Meagher

This error occurs in any of the Java based nodes which are throwing an undeclared exception or error.

If you have written your own Java node, then you should ensure that within the setup,processAll & cleanup methods you only throw a "NodeFailedException".
Generally, if you catch an exception, or notice an error condition in your code, you should log the exception then call:
throw fail();
Which will notify the node infrastructure that there was a problem in executing the node, but that you have taken care of logging all of the error information.
Detailed information about logging and error handling within the Java node can be found in the Java Node Getting Started Guide which is shipped with the LAE, and can be found in the docs directory of your LAE installation.

If you have not written your own Java node, and this error is appearing within a node that comes supplied with the LAE or via LAL, then this is likely a bug in the node itself.
In such cases, post the message that is being reported by the node, together with the type of the node (Dimensional Aggregator node, Pivot - Data to Names, XML Data etc) in the "Nodes" section of the forum and someone will either be able to help you with your specific problem or if this is a bug in the node, the problem will be able to be rectified in a subsequent LAE or LAL release.

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

Originally posted by: ryeh

I'm getting this from the Fuzzy X-Ref node if I don't use anything for the exact match. Adding 1's (TRUE) to both expressions solves the problem, but the error is not intuitive.