Excel Link

Error Messages and Troubleshooting

Excel Cell Error Messages	Error messages displayed in a worksheet cell.
Excel Error Message Boxes	Error messages displayed in an Excel error message box.
Audible Error Signals	Audible error signals while passing data to MATLAB.
Data Errors	Undesirable data characteristics.

Excel Cell Error Messages

Excel may display one of these error messages in a worksheet cell.

Table A-1: Excel Cell Error Messages
Excel Cell Error Message
Meaning
Solution

#COLS>256
Your MATLAB variable exceeds the Excel limit of 256 columns.
This is a limitation in Excel. Try the computation with a variable containing fewer columns.

#COMMAND!
MATLAB does not recognize the command in an MLEvalString function. The command may be misspelled.
Verify the spelling of the MATLAB command. Correct typing errors.

#DIMENSION!
You used MLAppendMatrix and the dimensions of the appended data do not match the dimensions of the matrix you want to append.
Verify the matrix dimensions and the appended data dimensions, and correct the argument. See MLAppendMatrix in Function Reference.

#INVALIDNAME!
You entered an illegal variable name.
Make sure to use legal MATLAB variable names. MATLAB variable names must start with a letter followed by up to 30 letters, digits, or underscores.

#INVALIDTYPE!
You have specified an illegal MATLAB data type with MLGetVar or MLGetMatrix.
See Data Types for a list of supported MATLAB data types.

#MATLAB?
You used an Excel Link function and MATLAB is not running.
Start Excel Link and MATLAB. See Starting Excel Link.

#NAME?
Excel doesn't recognize the function name. The excllink.xla add-in is not loaded, or the function name may be misspelled.
Be sure the excllink.xla add-in is loaded. See Configuring Excel to Work with Excel Link. Check the spelling of the function name. Correct typing errors.

#NONEXIST!
You referenced a nonexistent matrix in an MLGetMatrix or MLDeleteMatrix function. The matrix name may be misspelled.
Verify the spelling of the MATLAB matrix. Use the MATLAB whos command to display existing matrices. Correct typing errors.

#ROWS>65536
Your MATLAB variable exceeds the Excel limit of 65536 rows.
This is a limitation in Excel. Try the computation with a variable containing fewer rows.

#SYNTAX?
You entered an Excel Link function with incorrect syntax; for example, the double quotes (") may be missing, or you used single quotes (') instead of double quotes.
Verify and correct the function syntax. See the Function Reference for function syntax.

#VALUE!
An argument is missing from a function, or a function argument is the wrong type.
Supply the correct number of function arguments, of the correct type.

#VALUE!
A macro subroutine uses MLGetMatrix followed by MatlabRequest, which is correct standard usage. A macro function calls that subroutine, and you execute that function from a worksheet cell. The function works correctly, but this message appears in the cell.
Since the function works correctly, you may ignore the message. Or, in this special case, remove MatlabRequest from the subroutine.

**Table A-1: Excel Cell Error Messages**
Excel Cell Error Message	Meaning	Solution
`#COLS>256`	Your MATLAB variable exceeds the Excel limit of 256 columns.	This is a limitation in Excel. Try the computation with a variable containing fewer columns.
`#COMMAND!`	MATLAB does not recognize the command in an `MLEvalString` function. The command may be misspelled.	Verify the spelling of the MATLAB command. Correct typing errors.
`#DIMENSION!`	You used `MLAppendMatrix` and the dimensions of the appended data do not match the dimensions of the matrix you want to append.	Verify the matrix dimensions and the appended data dimensions, and correct the argument. See `MLAppendMatrix` in Function Reference.
`#INVALIDNAME!`	You entered an illegal variable name.	Make sure to use legal MATLAB variable names. MATLAB variable names must start with a letter followed by up to 30 letters, digits, or underscores.
`#INVALIDTYPE!`	You have specified an illegal MATLAB data type with `MLGetVar` or `MLGetMatrix`.	See Data Types for a list of supported MATLAB data types.
`#MATLAB?`	You used an Excel Link function and MATLAB is not running.	Start Excel Link and MATLAB. See Starting Excel Link.
`#NAME?`	Excel doesn't recognize the function name. The `excllink.xla` add-in is not loaded, or the function name may be misspelled.	Be sure the `excllink.xla` add-in is loaded. See Configuring Excel to Work with Excel Link. Check the spelling of the function name. Correct typing errors.
`#NONEXIST!`	You referenced a nonexistent matrix in an `MLGetMatrix` or `MLDeleteMatrix` function. The matrix name may be misspelled.	Verify the spelling of the MATLAB matrix. Use the MATLAB `whos` command to display existing matrices. Correct typing errors.
`#ROWS>65536`	Your MATLAB variable exceeds the Excel limit of 65536 rows.	This is a limitation in Excel. Try the computation with a variable containing fewer rows.
`#SYNTAX?`	You entered an Excel Link function with incorrect syntax; for example, the double quotes (") may be missing, or you used single quotes (') instead of double quotes.	Verify and correct the function syntax. See the Function Reference for function syntax.
`#VALUE!`	An argument is missing from a function, or a function argument is the wrong type.	Supply the correct number of function arguments, of the correct type.
#`VALUE!`	A macro subroutine uses `MLGetMatrix` followed by `MatlabRequest`, which is correct standard usage. A macro function calls that subroutine, and you execute that function from a worksheet cell. The function works correctly, but this message appears in the cell.	Since the function works correctly, you may ignore the message. Or, in this special case, remove `MatlabRequest` from the subroutine.

Note When you open an Excel worksheet that contains Excel Link functions, Excel tries to execute the functions from the bottom up and right to left, thus possibly generating cell error messages (#COMMAND!, #NONEXIST!, etc.). Such behavior is usual for Excel. Simply ignore the messages, close any MATLAB figure windows, and re-execute the cell functions one at a time in the correct order by pressing F2, then Enter.

Excel Error Message Boxes

Excel may display one of these error message boxes.

Table A-2: Excel Error Message Boxes
Excel Error Message Box
Meaning
Solution

You entered a formula incorrectly. Common errors include a space between the function name and the left parenthesis; or missing, extra, or mismatched parentheses.
Check entry and correct typing errors.

You tried to execute a macro and the location of excllink.xla is incorrect.
Click OK. The References window opens. Remove the check from MISSING: excllink.xla. Find excllink.xla in its correct location, check its box in the References window, and click OK.

You used MLGetMatrix and the matrix is larger than the space available in the worksheet. This error destabilizes Excel Link and changes worksheet calculation mode to manual.
Click OK. Reset worksheet calculation mode to automatic and save your worksheet (if desired). Close Excel and MATLAB. Restart Excel, Excel Link, and MATLAB.

The license passcode that you entered was invalid.
Check that you entered the license passcode properly. If you used a proper passcode and you are still unable to start Excel Link, contact your MathWorks representative.

**Table A-2: Excel Error Message Boxes**
Excel Error Message Box	Meaning	Solution
	You entered a formula incorrectly. Common errors include a space between the function name and the left parenthesis; or missing, extra, or mismatched parentheses.	Check entry and correct typing errors.
	You tried to execute a macro and the location of `excllink.xla` is incorrect.	Click OK. The References window opens. Remove the check from `MISSING: excllink.xla`. Find `excllink.xla` in its correct location, check its box in the References window, and click OK.
	You used `MLGetMatrix` and the matrix is larger than the space available in the worksheet. This error destabilizes Excel Link and changes worksheet calculation mode to manual.	Click OK. Reset worksheet calculation mode to automatic and save your worksheet (if desired). Close Excel and MATLAB. Restart Excel, Excel Link, and MATLAB.
	The license passcode that you entered was invalid.	Check that you entered the license passcode properly. If you used a proper passcode and you are still unable to start Excel Link, contact your MathWorks representative.

Audible Error Signals

Audible error signals while passing data to MATLAB with MLPutMatrix or MLAppendMatrix usually mean you have insufficient computer memory to carry out the operation. Close other applications or clear unnecessary variables from the MATLAB workspace and try again. If the error signal reoccurs, you probably have insufficient physical memory in your computer for this operation.

Data Errors

Data in the MATLAB or Excel workspaces may exhibit these undesired characteristics.

Table A-3: Data Errors
Data Error
Cause
Solution

MATLAB matrix cells contain zeros (0).
Corresponding Excel worksheet cells are empty.
Excel worksheet cells must contain only numeric or string data.

MATLAB matrix is a 1-by-1 zero matrix.
You used quotes around the data-location argument in MLPutMatrix or MLAppendMatrix.
Correct the syntax to remove quotes.

MATLAB matrix is empty ([]).
You referenced a nonexistent VBA variable in MLPutVar.
Correct the macro; you may have typed the variable name incorrectly.

VBA matrix is empty.
You referenced a nonexistent MATLAB variable in MLGetVar.
Correct the macro; you may have typed the variable name incorrectly.

Table A-3: **Data Errors**
Data Error	Cause	Solution
MATLAB matrix cells contain zeros (0).	Corresponding Excel worksheet cells are empty.	Excel worksheet cells must contain only numeric or string data.
MATLAB matrix is a 1-by-1 zero matrix.	You used quotes around the data-location argument in `MLPutMatrix` or `MLAppendMatrix`.	Correct the syntax to remove quotes.
MATLAB matrix is empty ([]).	You referenced a nonexistent VBA variable in `MLPutVar`.	Correct the macro; you may have typed the variable name incorrectly.
VBA matrix is empty.	You referenced a nonexistent MATLAB variable in `MLGetVar`.	Correct the macro; you may have typed the variable name incorrectly.

MLPutVar Installed Files