Script Build Errors

This appendix describes the error messages that appear in the Script Editor Error Help dialog box. For more information about accessing this dialog box, see Building Scripts with the Text Editor.

Error Number	Error Message	Description	Fixing the Error
WL1001	You should use two backslash characters ("\\") to represent a single backslash character.	Use the string "\\" to represent the backslash character.	Add one more backslash in the string, next to the single backslash that is already there.
WL1002	Not enough parameter values for the action; there must be at least two.	The actions Boolean_And() and Boolean_Or() should have two or more parameters. Each of the actions can have up to five parameters.	Pass 2, 3, 4, or 5 parameters to Boolean_And() and to Boolean_or().
WL1003	Call to non-existing script.	This error occurs if the name doesn’t exactly match the name of a script or if the script does not exist.	Either call a script that exists or write the non-existing script. Make sure that the name of the script matches exactly, including the case of the letters.
WL1004	Division by 0 is not allowed.	The divisor passed to Number_Divide() is zero, and dividing by zero is an undefined mathematical operation.	Make sure to never use 0 as the divisor in Number_Divide().
WL1005	No variable assigned to the value for this action.	The action returns a value, but the script is not using that value.	Create a variable and assign the action’s value to the variable.
WL1006	Call to script references non-existing (or incorrect type) variable.	The variable that is being exchanged with the Call action cannot be found in the called script, or the variable type doesn’t match the type in the called script.	Reference a variable that exists or a variable that is the correct type.
WL1007	The host profile does not exist.	The script activates on a host profile, but that host profile does not exist because the name does not exactly match a host profile or because the host profile has not yet been created.	Either use a host profile that exists or create the host profile. Make sure that the name of the profile matches exactly, including the case of the letters.
WL2001	Text line is too many characters.	The line of text contains too many characters. Long lines of text cause the script to be hard to read or understand.	Break the line into multiple lines. Assign actions to variables instead of passing actions to other actions.
WL2002	Keyword Script already used.	There can be one keyword Script in each script; this error occurs when more than one Script keyword in the script.	Remove any extra Script keywords so that there is only one.
WL2003	Keyword Script must be the first statement.	The keyword Script must be the first statement in a script.	Move all statements before Script to after Script.
WL2004	Missing ( after keyword.	Almost all actions and keywords must have a ( after them. The ( is missing.	Add a ( after the keyword.
WL2005	Missing parameter for keyword or action.	The action or keyword requires one or more parameters, and there are no parameters present.	Add the correct number of parameters to the action or keyword.
WL2006	Second parameter for keyword must be TRUE or FALSE. Invalid parameter for keyword. The second parameter must be a quoted string. Unknown terminal type. Unknown keypress key.	This error indicates an invalid parameter passed to an action or keyword. The most common cause of this error is an invalid parameter to Keypress_Key().	Carefully check the parameters passed to the action or keyword and study the error message to help fix the problem.
WL2007	Missing ) after parameter to keyword. Missing ) after parameter to action.	Most actions and keywords use ( and ). This action or keyword is missing the right parenthesis.	Add ), probably at the end of the line.
WL2008	Extra character(s) after parameter.	There are one or more extra characters after a parameter to an action or to a keyword.	Make sure that after a parameter, there is a right parenthesis ) or a comma and another parameter. Make sure that after the last ), there are no more characters.
WL2009	The variable name is already in use by a string variable.	Variable names may be declared once. This error occurs when a variable name is used in another variable declaration.	Change the name of the variable in the second declaration.
WL2010	The variable name is already in use by a number variable.	Variable names may be declared once. This error occurs when a variable name is used in another variable declaration.	Change the name of the variable in the second declaration.
WL2011	The variable name is already in use by a boolean variable.	Variable names may be declared once. This error occurs when a variable name is used in another variable declaration.	Change the name of the variable in the second declaration.
WL2012	Invalid activation method.	The method in the Activate action is not valid because it is not spelled correctly or because it’s not a valid method.	Check the spelling. The method is case-sensitive. Make sure the method is in the list of activation methods.
WL2013	Non-printable character is not allowed.	A non-printable character is in the line of text. This can happen when pasting text from another program.	Re-type the line of text in the script editor.
WL2014	Blank characters are not allowed in the label. Blank characters are not allowed in the macro name. Invalid character is not allowed. Invalid character is at the beginning of the line.	An invalid character is present in the script text.	Remove or change the character that the error message says is invalid.
WL2015	Parameter cannot be empty. Not enough parameters; there must be 3 for On_Key. Not enough parameters; there must be 3 for On_Input. The label cannot be blank. The macro name cannot be blank.	A parameter is missing from Activate, Keypress_Key, Label, Goto, or Call.	Add the missing parameter. All parameters must be on the same line of text.
WL2016	Too many parameters.	The action contains too many parameters.	Check how many parameters the action needs and remove the extras.
WL2017	Invalid key value; must be 1-0xFFFF.	The key value for Activate(On_Key) cannot be zero.	Change the zero value to a valid key value.
WL2018	Invalid key modifier; must be None or Alt or Ctrl or Shift.	Activate(On_Key) contains a modifier that is not recognized or that is not supported.	Change the modifier to match exactly one of the supported modifiers; None or Alt or Ctrl or Shift.
WL2019	Missing : after keyword.	There must be a colon (:) after the keyword, before the label, for the actions Goto, Label, and Call.	Add a colon after the keyword, before the label.
WL2020	Extra characters after action.	There are some characters after the end of the action, after the last ).	Remove all characters after the last ). Each action must be on a separate line.
WL2021	The value Goto is an action, which is not allowed. The value Activate is a keyword, which is not allowed. No spaces or tabs are allowed in variable names. Unknown string variable.	A keyword or variable is being used for a variable name, or a variable name has spaces or Activate is using an unknown variable.	Use a variable name that is not an action or keyword. Make sure there are no spaces or tabs in the variable name. For Activate, define the variable before using Activate.
WL2022	Missing = after variable.	When setting a variable, use =.	Add a = after the variable.
WL2023	Missing assignment for variable.	After the = there must be a variable, action or constant, all on the same line.	If the assignment is split into two lines, combine them. If there is nothing after = add a variable or action or constant.
WL2024	Invalid assignment for variable.	A variable is being assigned to an unknown variable or to an unknown action or to an incorrect value.	If assigning to a variable or action, correct the case-sensitive spelling of the variable or action.
WL2025	Unknown action.	The script contains an action that is not known. Action names are case-sensitive.	Correct the spelling or the case of the action name. Make sure the _ is in the correct place in the name.
WL2026	Variable type is not the same as the action return type.	The return type of the action must be the same as the type of the variable.	Change the type of the variable or use another variable that has the same type as the action.
WL2027	Variable type is not the same as the variable type.	The type of the two variables must be the same.	Change the type of the variable or use another variable that has the same type.
WL2028	Variable type is not the same as the assignment type.	The type of the two variables and the constant must be the same.	Change the type of the variable or constant. Use another variable or constant that has the same type.
WL2029	No closing quote is found in string. The parameter is not valid.	A string must be surrounded by quotation marks. A parameter must be a string, number, variable, or action.	If the string is missing a quotation mark, add one to the end of the string. If the parameter is not valid, check its spelling and the case of its letters. If the parameter is a variable, make sure the variable is declared above this line.
WL2030	The label cannot be an action. The label cannot be a variable. The parameter type doesn’t match the return type for the action. The parameter type must be the type.	Labels cannot be variables or actions. If an action is used as a parameter, the action return type must be the same as the parameter type.	For labels, use a unique name that is not an action or variable name. Instead of using an action as a parameter, use a variable that calls the action in a line before.
WL2031	Unexpected character.	The line of text is not quite right because a character is extra or out of place.	Use the error message information to help determine which character is incorrect.
WL2032	Not enough parameter values.	The action is missing one or more parameters.	Check the specification for the action and add parameters to it.
WL2033	Could not open file; error.	A script file could not be opened, probably because the user does not have the correct permission for the file or its folder.	Verify read and write permissions for the file and its folder.
WL2034	File is too small.	A script file must contain at least three bytes so that the script editor can determine if it’s Unicode, UTF-8, or ANSI text.	Use a different file that is larger.
WL2035	File encoding not supported: Unicode big endian.	Script files may be encoded as Unicode (little endian), ANSI, or UTF-8. Script files cannot be encoded as Unicode big endian.	Open the file in Notepad, select File > Save As > Encoding, and change it to something other than Unicode big endian.
WL2036	Could not write to file.	A script file could not be written, probably because the user does not have the correct permission for the file or its folder.	Verify read and write permissions for the file and its folder.
WL2037	Memory allocation failed.	There is not enough memory left for the program to run correctly.	Restart the computer.
WL2038	Too many nested calls.	An action has a parameter that is an action that has a parameter that is an action and so on, too many times.	Make one action call per line of text, assigning the return value to a variable. Use the variable as a parameter to another action. Do not use actions as parameters.
WL2039	Script error.	The script contains a generic problem.	Use the error message to help determine the cause of the problem. Try commenting-out or removing some lines of the script to isolate the problem.

Error Number

Error Message

Description

Fixing the Error

WL1001

You should use two backslash characters ("\\") to represent a single backslash character.

Use the string "\\" to represent the backslash character.

Add one more backslash in the string, next to the single backslash that is already there.

WL1002

Not enough parameter values for the action; there must be at least two.

The actions Boolean_And() and Boolean_Or() should have two or more parameters. Each of the actions can have up to five parameters.

Pass 2, 3, 4, or 5 parameters to Boolean_And() and to Boolean_or().

WL1003

Call to non-existing script.

This error occurs if the name doesn’t exactly match the name of a script or if the script does not exist.

Either call a script that exists or write the non-existing script. Make sure that the name of the script matches exactly, including the case of the letters.

WL1004

Division by 0 is not allowed.

The divisor passed to Number_Divide() is zero, and dividing by zero is an undefined mathematical operation.

Make sure to never use 0 as the divisor in Number_Divide().

WL1005

No variable assigned to the value for this action.

The action returns a value, but the script is not using that value.

Create a variable and assign the action’s value to the variable.

WL1006

Call to script references non-existing (or incorrect type) variable.

The variable that is being exchanged with the Call action cannot be found in the called script, or the variable type doesn’t match the type in the called script.

Reference a variable that exists or a variable that is the correct type.

WL1007

The host profile does not exist.

The script activates on a host profile, but that host profile does not exist because the name does not exactly match a host profile or because the host profile has not yet been created.

Either use a host profile that exists or create the host profile. Make sure that the name of the profile matches exactly, including the case of the letters.

WL2001

Text line is too many characters.

The line of text contains too many characters. Long lines of text cause the script to be hard to read or understand.

Break the line into multiple lines. Assign actions to variables instead of passing actions to other actions.

WL2002

Keyword Script already used.

There can be one keyword Script in each script; this error occurs when more than one Script keyword in the script.

Remove any extra Script keywords so that there is only one.

WL2003

Keyword Script must be the first statement.

The keyword Script must be the first statement in a script.

Move all statements before Script to after Script.

WL2004

Missing ( after keyword.

Almost all actions and keywords must have a ( after them. The ( is missing.

Add a ( after the keyword.

WL2005

Missing parameter for keyword or action.

The action or keyword requires one or more parameters, and there are no parameters present.

Add the correct number of parameters to the action or keyword.

WL2006

Second parameter for keyword must be TRUE or FALSE.
Invalid parameter for keyword.
The second parameter must be a quoted string.
Unknown terminal type.
Unknown keypress key.

This error indicates an invalid parameter passed to an action or keyword. The most common cause of this error is an invalid parameter to Keypress_Key().

Carefully check the parameters passed to the action or keyword and study the error message to help fix the problem.

WL2007

Missing ) after parameter to keyword.
Missing ) after parameter to action.

Most actions and keywords use ( and ). This action or keyword is missing the right parenthesis.

Add ), probably at the end of the line.

WL2008

Extra character(s) after parameter.

There are one or more extra characters after a parameter to an action or to a keyword.

Make sure that after a parameter, there is a right parenthesis ) or a comma and another parameter. Make sure that after the last ), there are no more characters.

WL2009

The variable name is already in use by a string variable.

Variable names may be declared once. This error occurs when a variable name is used in another variable declaration.

Change the name of the variable in the second declaration.

WL2010

The variable name is already in use by a number variable.

Variable names may be declared once. This error occurs when a variable name is used in another variable declaration.

Change the name of the variable in the second declaration.

WL2011

The variable name is already in use by a boolean variable.

Variable names may be declared once. This error occurs when a variable name is used in another variable declaration.

Change the name of the variable in the second declaration.

WL2012

Invalid activation method.

The method in the Activate action is not valid because it is not spelled correctly or because it’s not a valid method.

Check the spelling. The method is case-sensitive. Make sure the method is in the list of activation methods.

WL2013

Non-printable character is not allowed.

A non-printable character is in the line of text. This can happen when pasting text from another program.

Re-type the line of text in the script editor.

WL2014

Blank characters are not allowed in the label.
Blank characters are not allowed in the macro name.
Invalid character is not allowed.
Invalid character is at the beginning of the line.

An invalid character is present in the script text.

Remove or change the character that the error message says is invalid.

WL2015

Parameter cannot be empty.
Not enough parameters; there must be 3 for On_Key.
Not enough parameters; there must be 3 for On_Input.
The label cannot be blank.
The macro name cannot be blank.

A parameter is missing from Activate, Keypress_Key, Label, Goto, or Call.

Add the missing parameter. All parameters must be on the same line of text.

WL2016

Too many parameters.

The action contains too many parameters.

Check how many parameters the action needs and remove the extras.

WL2017

Invalid key value; must be 1-0xFFFF.

The key value for Activate(On_Key) cannot be zero.

Change the zero value to a valid key value.

WL2018

Invalid key modifier; must be None or Alt or Ctrl or Shift.

Activate(On_Key) contains a modifier that is not recognized or that is not supported.

Change the modifier to match exactly one of the supported modifiers; None or Alt or Ctrl or Shift.

WL2019

Missing : after keyword.

There must be a colon (:) after the keyword, before the label, for the actions Goto, Label, and Call.

Add a colon after the keyword, before the label.

WL2020

Extra characters after action.

There are some characters after the end of the action, after the last ).

Remove all characters after the last ). Each action must be on a separate line.

WL2021

The value Goto is an action, which is not allowed.
The value Activate is a keyword, which is not allowed.
No spaces or tabs are allowed in variable names.
Unknown string variable.

A keyword or variable is being used for a variable name, or a variable name has spaces or Activate is using an unknown variable.

Use a variable name that is not an action or keyword. Make sure there are no spaces or tabs in the variable name. For Activate, define the variable before using Activate.

WL2022

Missing = after variable.

When setting a variable, use =.

Add a = after the variable.

WL2023

Missing assignment for variable.

After the = there must be a variable, action or constant, all on the same line.

If the assignment is split into two lines, combine them. If there is nothing after = add a variable or action or constant.

WL2024

Invalid assignment for variable.

A variable is being assigned to an unknown variable or to an unknown action or to an incorrect value.

If assigning to a variable or action, correct the case-sensitive spelling of the variable or action.

WL2025

Unknown action.

The script contains an action that is not known. Action names are case-sensitive.

Correct the spelling or the case of the action name. Make sure the _ is in the correct place in the name.

WL2026

Variable type is not the same as the action return type.

The return type of the action must be the same as the type of the variable.

Change the type of the variable or use another variable that has the same type as the action.

WL2027

Variable type is not the same as the variable type.

The type of the two variables must be the same.

Change the type of the variable or use another variable that has the same type.

WL2028

Variable type is not the same as the assignment type.

The type of the two variables and the constant must be the same.

Change the type of the variable or constant. Use another variable or constant that has the same type.

WL2029

No closing quote is found in string.
The parameter is not valid.

A string must be surrounded by quotation marks.
A parameter must be a string, number, variable, or action.

If the string is missing a quotation mark, add one to the end of the string.
If the parameter is not valid, check its spelling and the case of its letters.
If the parameter is a variable, make sure the variable is declared above this line.

WL2030

The label cannot be an action.
The label cannot be a variable.
The parameter type doesn’t match the return type for the action.
The parameter type must be the type.

Labels cannot be variables or actions. If an action is used as a parameter, the action return type must be the same as the parameter type.

For labels, use a unique name that is not an action or variable name. Instead of using an action as a parameter, use a variable that calls the action in a line before.

WL2031

Unexpected character.

The line of text is not quite right because a character is extra or out of place.

Use the error message information to help determine which character is incorrect.

WL2032

Not enough parameter values.

The action is missing one or more parameters.

Check the specification for the action and add parameters to it.

WL2033

Could not open file; error.

A script file could not be opened, probably because the user does not have the correct permission for the file or its folder.

Verify read and write permissions for the file and its folder.

WL2034

File is too small.

A script file must contain at least three bytes so that the script editor can determine if it’s Unicode, UTF-8, or ANSI text.

Use a different file that is larger.

WL2035

File encoding not supported: Unicode big endian.

Script files may be encoded as Unicode (little endian), ANSI, or UTF-8. Script files cannot be encoded as Unicode big endian.

Open the file in Notepad, select File > Save As > Encoding, and change it to something other than Unicode big endian.

WL2036

Could not write to file.

A script file could not be written, probably because the user does not have the correct permission for the file or its folder.

Verify read and write permissions for the file and its folder.

WL2037

Memory allocation failed.

There is not enough memory left for the program to run correctly.

Restart the computer.

WL2038

Too many nested calls.

An action has a parameter that is an action that has a parameter that is an action and so on, too many times.

Make one action call per line of text, assigning the return value to a variable. Use the variable as a parameter to another action. Do not use actions as parameters.

WL2039

Script error.

The script contains a generic problem.

Use the error message to help determine the cause of the problem. Try commenting-out or removing some lines of the script to isolate the problem.

Was this article useful?

The topic was:

Inaccurate

Incomplete

Not what I expected

Other