Application deployment R2012a vs. R2014b

I am attempting to update from R2012a to R2014b but have been unable to get 64bit stand-alone Windows applications to show anything other than the splashscreen for R2014b compiled code.

Here is the (simple) function

function deploytest
n = 1000;
v = zeros(1,n);
h = waitbar(0,'Please wait...');
for i=1:n,
    v(1,i) = rand;
    waitbar(i/n,h)
end
plot(v)

Compiled using "deploytool" from the MATLAB command line and then respective GUI/APP in 2012a and 2014b. Compiled on the same 64bit Windows workstation. No problems apparent in creation of executables. Transfer files by USB thumb drive as the deployed workstation is not on a network. Both MCR versions are installed on the deployed workstation. Runs just fine in 2012a.

Any ideas on what I am doing incorrectly or what I might be missing? - Andre Weinstock

[Dasharath Gulvady]

I deployed your sample code with R2014b, and it runs fine for me.

1. Check if R2014b MATLAB Compiler Runtime(MCR) location has been added to Windows PATH, just like R2012a(MCR).

2. Is this issue reproducible for any application? Try with the following:

function deploytest
  disp('Hello World');
end

3. Does the compiled application run fine on the machine where the standalone application was built?

[André]

Hi Dasharath,

1. Yes. Both v717 and v84 are in C:\programfiles\MATLAB\MCR

2. I get the same result. just the splash screen and then closes. I run with the Task Manager running and nothing appears there as well.

3. Yes

Another idea: because I have to deploy and maintain stand-alone's on both 32 bit and 64 bit Windows systems my main worstation has 4 copies of MATLAB on it: R2012a 32bit, R2012a 64bit, R2014b 32bit, R2014 64bit. Could there be a conflict there? Unfortunately I have to continue maintenance on several 2012a stand-alone applications and cannot un-install these versions or MCRs without a lot of time and effort.

[André]

Hi again,

I have been able to succesfully use R2014b 32bit.

Now thinking it might be something funny about my install of R2014b 64bit concurrently with other versions on my compiling workstation. Am trying a fresh install of R2015a 64bit and will see if that works.

Stay tuned...

[André]

Resloved by doing a clean install of R2015a 64bit and R2015a 32bit on the compiling workstation. Either there was a problem with the pathname of the 64bit R2014b or a bug in R2014b which I could not detemrine.

Answer 1

[André]

This problem was resolved when I upgraded to R2015a (64bit and 32bit) on the compiling workstation. - Andre

Answer 2

[Dasharath Gulvady]

Check if "C:\Program Files\MATLAB\MATLAB Compiler Runtime\v84\runtime\win64" is added in Windows PATH environment variable. If it is present, make sure it is above all the other releases.

The best way to analyze such issues is by using Process Monitor.

http://www.mathworks.com/matlabcentral/answers/92515-how-can-i-use-process-monitor-to-troubleshoot-the-execution-of-my-program