Skip to Main Content Skip to Search
Product Documentation

Deployed Applications

Failed to decrypt file. The MATLAB file "<ctf_root>\toolbox\compiler\deploy\matlabrc.m" cannot be executed.  The application is trying to use a CTF archive that does not belong to it. Applications and CTF archives are tied together at compilation time by a unique cryptographic key, which is recorded in both the application and the CTF archive. The keys must match at run time. If they don't match, you will get this error.

To work around this, delete the *_mcr folder corresponding to the CTF archive and then rerun the application. If the same failure occurs, you will likely need to recompile the application using MATLAB Compiler and copy both the application binary and the CTF archive into the installation folder.

This application has requested the run time to terminate in an unusual way.  This indicates a segmentation fault or other fatal error. There are too many possible causes for this message to list them all.

To try to resolve this problem, run the application in the debugger and try to get a stack trace or locate the line on which the error occurs. Fix the offending code, or, if the error occurs in a MathWorks library or generated code, contact MathWorks technical support.

Checking access to X display <IP-address>:0.0 . . .
If no response hit ^C and fix host or access control to host.
Otherwise, checkout any error messages that follow and fix . . .
Successful. . . . .  This message can be ignored.

??? Error: File: /home/username/<MATLAB file_name>
Line: 1651 Column: 8
Arguments to IMPORT must either end with ".*"
or else specify a fully qualified class name:
"<class_name>" fails this test.  The import statement is referencing a Java class (<class_name>) that MATLAB Compiler (if the error occurs at compile time) or the MCR (if the error occurs at run time) cannot find.

To work around this, ensure that the JAR file that contains the Java class is stored in a folder that is on the Java class path. (See matlabroot/toolbox/local/classpath.txt for the class path.) If the error occurs at run time, the classpath is stored in matlabroot/toolbox/local/classpath.txt when running on the development machine. It is stored in <mcr_root>/toolbox/local/classpath.txt when running on a target machine.

Warning: Unable to find Java library:
matlabroot\sys\java\jre\win32|win64\jre<version>\bin\client\jvm.dll
Warning: Disabling Java support.  This warning indicates that a compiled application can not find the Java virtual machine, and therefore, the compiled application cannot run any Java code. This will affect your ability to display graphics.

To resolve this, ensure that jvm.dll is in the matlabroot\sys\java\jre\win32|win64\jre<version>\bin\client folder and that this folder is on your system path.

Warning: matlabroot\toolbox\local\pathdef.m not found.
Toolbox Path Cache is not being used. Type 'help toolbox_path_cache' for more info.  The pathdef.m file defines the MATLAB startup path. MATLAB Compiler does not include this file in the generated CTF archive because the MCR path is a subset of the full MATLAB path.
This message can be ignored.

Undefined function or variable 'matlabrc'.  When MATLAB or the MCR starts, they attempt to execute the MATLAB file matlabrc.m. This message means that this file cannot be found.
To work around this, try each of these suggestions in this order:

This MATLAB file does not have proper version information and may be corrupt. Please delete the extraction directory and rerun the application. The MATLAB file <MATLAB file> cannot be executed. MATLAB:err_parse_cannot_run_m_file.  This message is an indication that the MCR has found nonencrypted MATLAB files on its path and has attempted to execute them. This error is often caused by the use of addpath, either explicitly in your application, or implicitly in a startup.m file. If you use addpath in a compiled application, you must ensure that the added folders contain only data files. (They cannot contain MATLAB files, or you'll get this error.)

To work around this, protect your calls to addpath with the isdeployed function.

This application has failed to start because mclmcrrt7x.dll was not found. Re-installing the application may fix this problem.  mclmcrrt7x.dll contains the public interface to the MCR. This library must be present on all machines that run applications generated by MATLAB Compiler. Typically, this means that either the MCR is not installed on this machine, or that the PATH does not contain the folder where this DLL is located.

To work around this, install the MCR or modify the path appropriately. The path must contain <mcr_root>/<version>/runtime/<arch>, for example: c:\mcr\v73\runtime\win32|win64.

Linker cannot find library and fails to create standalone application (win32 and win64).  If you try building your standalone application without mbuild, you must link to the following dynamic library:

mclmcrrt.lib

This library is found in one of the following locations, depending on your architecture:

matlabroot\extern\lib\win32\arch
matlabroot\extern\lib\win64\arch

where arch is microsoft, watcom, or lcc.

Version 'GCC_4.2.0' not found.  When running on Linux platforms, users may report that a run time error occurs that states that the GCC_4.2.0 library is not found by applications built with MATLAB Compiler.

To resolve this error, do the following:

  1. Navigate to matlabroot/sys/os/glnx86.

  2. Rename the following files with a prefix of old_:

    • libgcc_s.so.1

    • libstdc++.so.6.0.8

    • libgfortran.so.1.0.0

    For example, rename libgcc_s.so.1 to old_libgcc_s.so.1. you must rename all three of the above files. Alternately, you can create a subfolder named old and move the files there.

Error: library mclmcrrt76.dll not found.  This error can occur for the following reasons:

To solve this problem, on the deployment machine, install the version of MATLAB you used to build the application.

Invalid .NET Framework.\n Either the specified framework was not found or is not currently supported.  This error occurs when the .NET Framework version your application is specifying (represented by n) is not supported by the current version of MATLAB Compiler. See the Product Overview in the MATLAB Builder NE documentation for a list of supported .NET Framework versions.

MATLAB:I18n:InconsistentLocale.  The warning message

MATLAB:I18n:InconsistentLocale - The system locale setting, 
system_locale_name, is different from the user locale 
setting, user_locale_name
indicates a mismatch between locale setting on Microsoft Windows systems. This may affect your ability to display certain characters. For information about changing the locale settings, see your operating system Help.

System.AccessViolationException: Attempted to read or write protected memory.  The message:

System.ArgumentException: Generate Queries 
                               threw General Exception:
System.AccessViolationException: Attempted to 
                         read or write protected memory.
 This is often an indication that other memory is corrupt.
indicates a library initialization error caused by a Microsoft Visual Studio project linked against a MCLMCRRT7XX.DLL placed outside install_root.

Unhandled exception at 0x0002d580 in clientApp.exe: 0xC0000005: Access violation reading location 0x0002d580.  This message may be due to compiling the DLL library in the lcc compiler while linking with a Microsoft linker. The Microsoft linker may not be able to read an lcc-produced DLL.

  

MATLAB CompilerMATLAB Compiler Limitations and RestrictionsLimitations and Restrictions

Free MATLAB Compiler Interactive Kit

Learn how to build standalone executables and C/C++ shared libraries from MATLAB code.


Get free kit

Trials Available

Try the latest version of MATLAB Compiler.


Get trial software
 © 1984-2012- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS