Advantage 34xx Error Codes

Advantage Error Guide

3401 Incomplete "is expression valid" function expression
3402 Incorrect parameter count within a function call in "is expression valid" function expression
3403 Missing string delimiter in "is expression valid" function expression
3404 Literal value too long in "is expression valid" function expression
3405 Unsupported data type value in "is expression valid" function expression
3406 Unsupported operator found in "is expression valid" function expression
3407 Unsupported function found in "is expression valid" function expression
3408 Invalid delimiter in function parameter in "is expression valid" function expression
3409 Unsupported data type in function parameter in "is expression valid" function expression
3410 Unknown alias name used with field name in "is expression valid" function expression
3411 Unknown identifier found in "is expression valid" function expression
3414 Advantage Expression Engine memory allocation failed
3415 Invalid field type found in "is expression valid" function expression
3416 Advantage Expression Engine operator stack overflow
3417 Number of "is expression valid" function expression parameters exceed the capability of the parser
3418 Mismatched number of parentheses in the "is expression valid" function expression
3419 Parser working stack is about to overflow
3422 Advantage server thread's working stack about to overflow

3401 Incomplete "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. The error was in the "is expression valid" function expression. The parse finished but the expression was incomplete.

Solution: Contact Advantage Technical Support if this error occurs.

3402 Incorrect parameter count within a function call in "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. A function in the "is expression valid" function expression contained too few or too many parameters.

Solution: Review the function calls within the "is expression valid" function expression to correct the number of parameters within the function call in error.

3403 Missing string delimiter in "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. A string in the "is expression valid" function expression is missing a delimiter.

Solution: Add a string delimiter to the string that is missing the delimiter within the "is expression valid" function expression.

3404 Literal value too long in "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. A literal value in the "is expression valid" function expression is longer than 32K.

Solution: Use literal values less than 32K in length within the "is expression valid" function expression.

3405 Unsupported data type value in "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. A value in the "is expression valid" function expression is not a supported data type.

Solution: Contact Advantage Technical Support if this error occurs.

3406 Unsupported operator found in "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. The "is expression valid" function expression contains an unsupported operator.

Solution: Verify operators in the expression are valid client operators that are supported by the Advantage Expression Engine.

3407 Unsupported function found in "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. The "is expression valid" function expression contains an unsupported function.

Solution: Verify the function names are not misspelled and are supported by the Advantage Expression Engine. For a list of all supported, see Advantage Expression Engine.

3408 Invalid delimiter in function parameter in "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. Parameters to a function within the "is expression valid" function expression are separated by an invalid delimiter.

Solution: Verify the delimiters separating parameters within a function call in the expression are valid.

3409 Unsupported data type in function parameter in "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. A parameter to a function or an operand within the key expression was of the wrong data type.

Solution: Verify the data types of the function parameters are of the correct data type.

3410 Unknown alias name used with field name in "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. A field name within the "is expression valid" function expression was aliased by an unknown alias name.

Solution: Advantage only supports aliases for the current work area. If an alias to another work area is referenced, this error will result. Verify the alias name is spelled properly.

3411 Unknown identifier found in "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. An identifier within the "is expression valid" function expression is unknown to the parser.

Solution: This error is usually caused by the use of memory variables within the "is expression valid" function expression. The Advantage Expression Engine does not support memory variables. The variables are visible only to the client. This error may also result from a misspelled field name or from a field name that does not exist in the current work area.

3414 Advantage Expression Engine memory allocation failed

Problem: An error occurred in the Advantage Expression Engine parser. A memory allocation failed.

Solution: If this error occurs, retry the command. If this error repeatedly occurs, more memory is needed on the server.

3415 Invalid field type found in "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. The "is expression valid" function expression contained an invalid field type.

Solution: This error is most likely due to the use of a memo field within the "is expression valid" function expression. Memo fields are not supported by the Advantage Expression Engine parser.

3416 Advantage Expression Engine operator stack overflow

Problem: An error occurred in the Advantage Expression Engine parser. The internal stack has exceeded the maximum number of operators.

Solution: This is most likely due to the "is expression valid" function expression containing an unusually high number of operators. Contact Advantage Technical Support.

3417 Number of "is expression valid" function expression parameters exceed the capability of the parser

Problem: An error occurred in the Advantage Expression Engine parser. The "is expression valid" function expression contained too many parameters for the parser to handle.

Solution: Contact Advantage Technical Support.

3418 Mismatched number of parentheses in the "is expression valid" function expression

Problem: An error occurred in the Advantage Expression Engine parser. The "is expression valid" function expression contains a mismatched number of parentheses.

Solution: Verify the parentheses are matched and are in the correct position.

3419 Parser working stack is about to overflow

Problem: An error occurred in the Advantage Expression Engine parser. The parser working stack was about to overflow.

Solution: This error is due to an extraordinarily large "is expression valid" function expression. Contact Advantage Technical Support.

3422 Advantage server thread's working stack about to overflow

Problem: An error occurred in the Advantage Expression Engine parser. The Advantage server thread's working stack was about to overflow. The problem is most likely due to an expression with a very large nesting of parentheses (hundreds of levels deep). This can occur when evaluating an Advantage Optimized Filter expression with a large number of OR operators on fields that are not indexed. It can also occur when evaluating the IN clause of an SQL statement on a field that is not indexed. For example, a query of the form "select * from T where F in (1, 2, 3, 4, .... 3000 )" could produce a very deep nesting if the field "F" is not indexed.

Solution: Either reduce the number of items in the filter or query, or create an index on the field so that it is fully optimized.