Troubleshooting

This appendix provides a table showing errors you may encounter using MATLAB Builder EX, probable causes for these errors, and suggested solutions.

Note MATLAB Builder EX uses MATLAB Compiler to generate components. This means that you might see diagnostic messages from MATLAB Compiler. See the MATLAB Compiler documentation for more information about those messages.

MATLAB Builder EX Errors and Suggested Solutions

Message	Probable Cause	Suggested Solution
`MBUILD.BAT: Error: The chosen compiler does not support building COM objects.`	The chosen compiler does not support building COM objects.	Rerun `mbuild -setup` and choose a supported compiler.
`Error in component_name.class_name: Error getting data conversion flags.`	Usually caused by `mwcomutil.dll` not being registered.	Open a DOS window, change folders to `matlabroot\runtime\win32` (matlabroot represents the location of MATLAB on your system), and run the command `mwregsvr mwcomutil.dll`. See Add-in and COM Component Registration for full details.
`Error in VBAProject: ActiveX component can't create object.`	Project DLL is not registered. An incompatible MATLAB DLL exists somewhere on the system path.	If the DLL is not registered, open a DOS window, change folders to `<projectdir>\distrib` (`<projectdir>` represents the location of your project files), and run the command: `mwregsvr <projectdll>.dll`. See Add-in and COM Component Registration for full details.
`Error in VBAProject: Automation error The specified module could not be found.`	This usually occurs if MATLAB is not on the system path. This error message occurs if you have more than one version of MATLAB on your system path.	Anytime you have multiple versions of MATLAB, ensure that the newest version of MATLAB appears on your path first. You can verify that the newest version of MATLAB is on the path first by typing `path` at the DOS prompt. See the table Required Locations to Develop and Use Components.
`LoadLibrary ("component_name.dll") failed - The specified module could not be found.`	You may get this error message while registering the project DLL from the DOS prompt. This usually occurs if MATLAB is not on the system path.	See the table Required Locations to Develop and Use Components.
`Cannot recompile the M file xxxx because it is already in the library libmmfile.mlib.`	The name you have chosen for your MATLAB file duplicates the name of a MATLAB file already in the library of precompiled MATLAB files.	Rename the MATLAB file, choosing a name that does not duplicate the name of a MATLAB file already in the library of precompiled MATLAB files.
`Arguments may only be defaulted at the end of an argument list.`	You have modified the VB script generated for MATLAB Builder EX and have not provided one or more arguments used in the modified script.	Provide a value for any argument that requires an explicit value. Arguments that accept defaults appear at the end of the argument list.
Unable to use accessibility screen-readers or assistive technologies, such as JAWS^®,	Required files `JavaAccessBridge.dll` and `WindowsAccessBridge.dll` no longer added automatically to your Windows path.	Add the following DLLs to your Windows path: JavaAccessBridge.dll WindowsAccessBridge.dll
`Error in class.method.version`	This is a generic message, but is sometimes seen when there are conflicts in architecture versions of MATLAB and Microsoft Excel.	See Deployment Target Architectures and Compatibility for detailed information.

Required Locations to Develop and Use Components

Component	Development Machine	Target Machine
MCR	Make sure that `matlabroot``\runtime\win32` appears on your system path ahead of any other MATLAB installations. (`matlabroot` is your root MATLAB folder.)	Verify that `mcr_root`\`ver``\runtime\win32` appears on your system path. (`mcr_root` is your root MCR folder.)

Microsoft Excel Errors and Suggested Solutions

Message Probable Cause Suggested Solution

Message	Probable Cause	Suggested Solution
The macros in this project are disabled. Please refer to the online help or documentation of the host application to determine how to enable macros. Note: Wording may vary depending upon the version of Excel you are running.	The macro security for Excel is set to `High`.	Set Excel macro security to `Medium` on the Security Level tab by doing the following: For Microsoft Office 2003: Click Tools > Macro > Security. For Security Level, select Medium. For Microsoft Office 2007: Click the 2007 Office button on the Microsoft Office ribbon ( ). Click Excel Options > Trust Center > Trust Center Settings > Macro Settings. In Developer Macro Settings, select Trust access to the VBA project object model. For Microsoft Office 2010: Click File > Options > Trust Center > Trust Center Settings > Macro Settings. In Developer Macro Settings, select Trust access to the VBA project object model.

The macros in this project are disabled. Please refer to the online help or documentation of the host application to determine how to enable macros.
Note: Wording may vary depending upon the version of Excel you are running.

The macro security for Excel is set to High.

Set Excel macro security to Medium on the Security Level tab by doing the following:

For Microsoft Office 2003:
1. Click
  Tools > Macro > Security.
2. For Security Level, select Medium.
For Microsoft Office 2007:
1. Click the 2007 Office button on the Microsoft Office ribbon ( ).
2. Click Excel Options > Trust Center > Trust Center Settings > Macro Settings.
3. In Developer Macro Settings, select Trust access to the VBA project object model.
For Microsoft Office 2010:
1. Click File > Options > Trust Center > Trust Center Settings > Macro Settings.
2. In Developer Macro Settings, select Trust access to the VBA project object model.

Function Wizard Problems

Problem Probable Cause Suggested Solution

The Function Wizard Help does not appear.

The Function Wizard Help file (mlfunction.chm) is not in the same folder as the Function Wizard add-in (mlfunction.xla).

Copy the Help file (mlfunction.chm) into the same folder as the add-in.

The Function Wizard did not automatically import your .bas file, and you have to create your macro manually

The Function Wizard has malfunctioned with an unspecified error

Open Excel

Do one of the following:

If you use Microsoft Office 2007 or 2010, click Developer > Macros.
If you use Microsoft Office 2003, click Tools > Macros > Macro.

Tip You may need to enable the Developer menu item before performing this step. To do this:

Click the 2007 Office button on the Microsoft Office ribbon ( ) or, in Office 2010, click File to display the Office Backstage View.
Click Excel Options.
In the Top Options for Working With Excel area, select Show Developer tab in the Ribbon.

From the Visual Basic Editor, select File > Import and select the created VBA file from the <project_dir>\distrib folder.

You get an error when trying to create a macro with the Function Wizard

The message Failed to start MATLAB appears instead of Starting MATLAB... when MATLAB is invoked by the Function Wizard.

This message may appear if you manually terminate the MATLAB session that is invoked from the Function Wizard. As a result, you can no longer use the wizard's MATLAB-related features in your current Excel session.

Save your work and restart Microsoft Excel.

When I use CTRL + arrow keys to select ranges with the Function Wizard, once I select a function and begin to select the function inputs, keyboard navigation no longer works in excel.

This behavior results from a bug in Microsoft Excel.

If you must use arrow keys to select ranges, apply the following fix from the Microsoft Web site: http://support.microsoft.com/kb/291110 .

Data Conversion Flags

Application Deployment Terms

Recommended Products

Get MATLAB trial software

Includes the most popular MATLAB recorded presentations with Q&A sessions led by MATLAB experts.

Get the Interactive Kit

Search MATLAB Documentation
R2012a Documentation → MATLAB Builder EX
View documentation for other releases	Learn more about MATLAB Builder EX