Skip to content

Error Messages

The topic lists parser and internal error messages that can be returned by SQL Enlight.

ER0134: The variable name @xyz has already been declared.

Section titled “ER0134: The variable name @xyz has already been declared.”

Parser error indicates that the variable name is not unique within the query batch or stored procedure.

How to resolve:Check the code and remove the duplicating @xyz variable.

ER0137: Must declare the scalar variable @xyz.

Section titled “ER0137: Must declare the scalar variable @xyz.”

Parser error indicating that variable is not declared.

How to resolve:Declare the @xyz variable.

ER0154: USE statement is not allowed in stored procedures, functions, and triggers.

Section titled “ER0154: USE statement is not allowed in stored procedures, functions, and triggers.”

Parser error indicating the USE statement was found inside stored procedures, functions, and triggers.

How to resolve:Remove USE statements from the body of the SQL module.

The parser encountered syntax error near token ‘xyz’.

How to resolve:Check the syntax and correct the error.

Internal SQL Enlight error.

How to resolve:Contact support.

ER0999: Internal error applying transformation.

Section titled “ER0999: Internal error applying transformation.”

Internal SQL Enlight error.

How to resolve:Contact support.

How to resolve:Contact support.

ER9001: License error. The trial period has expired.

Section titled “ER9001: License error. The trial period has expired.”

How to resolve:Activate the license.

ER9002: License error. Product requires re-activation.

Section titled “ER9002: License error. Product requires re-activation.”

How to resolve:Activate the license.

ER9003: License error. The license is not valid!

Section titled “ER9003: License error. The license is not valid!”

How to resolve:Contact support.

How to resolve:Contact support.

INF995: Rule is disabled. The rule requires SQL connection or Analysis Context, which is not available.

Section titled “INF995: Rule is disabled. The rule requires SQL connection or Analysis Context, which is not available.”

When performing analysis with rules that require SQL connection or Analysis Context, which are not available, these rules are ignored, and the INF995 messages are added to the error list instead.

How to resolve:Provide SQL Connection or Analysis Context.

INF996: Batch skipped due to syntax errors.

Section titled “INF996: Batch skipped due to syntax errors.”

Syntax errors were encountered while parsing the query batch. The batch was skipped during the code analysis.

The related syntax errors are shown in separate messages.

How to resolve:Correct the syntax errors.

INF997: Batch skipped. The batch is too big.

Section titled “INF997: Batch skipped. The batch is too big.”

The query batch was too big and was skipped during the code analysis.