MCR Error While Launching Designer

9 posts / 0 new
Last post
cncjerry
Offline
Last seen: 4 months 1 week ago
Joined: 07/04/2018 - 2:39pm
MCR Error While Launching Designer

I tried installing and keep getting an error about an entry point missing in launchermain.dll.  I've tried different MCRs, path statements, etc.  If I copy launchermain.dll into the directory where awe-designer.exe is installed, I don't get the error but all I get is the splash screen and that's it.  I can start the awe server, don;t know if that is needed or how it is used.

Any help out there?

Thanks,

Jerry

Axel Nilsson
Offline
Last seen: 2 hours 11 min ago
Joined: 12/19/2016 - 2:02pm

Hi Jerry,

Which version of AWE Designer are you using, and which MCR do you have installed? Can you attach a picture of the error you are getting?

Can you also zip up your Bin/Assets/logs folder and email it to me at anilsson@dspconcepts.com?

 

Thanks

-Axel

 

cncjerry
Offline
Last seen: 4 months 1 week ago
Joined: 07/04/2018 - 2:39pm

Axel, I sent an email with the information but for others, the error is:

The procedure entry point

?MLOUT@MLStream@io@services@@2V123@A could not be 

located in the dynamic link library c:\program Files

(x86)MATLAB\MATLAB Compiler

Runtime\v84\bin\win32\launchermain.dll.

 

Thanks

 

And by the way the bin\assets\log directory is empty.

 

Jerry

Axel Nilsson
Offline
Last seen: 2 hours 11 min ago
Joined: 12/19/2016 - 2:02pm

Hi Jerry,

 

I never received an email. 

The fact that the log directory is empty means that the MCR is never getting fully loaded so Designer is never launching. Is there an 'awe_designer_mcr' folder in your install directory?

 

Can you copy that launchermain.dll into your install directory again, but this time launch awe_designer.exe from the command line? To do this, open up a command prompt, then enter 'cd C:\path\to\install', and then 'awe_designer.exe'. This will show any error messages that may be occurring while launching Designer.

 

Thanks

Axel 

cncjerry
Offline
Last seen: 4 months 1 week ago
Joined: 07/04/2018 - 2:39pm

Axel,

I don't have an awe_designer_mcr directory in my install directory.

I copied launchermain.dll into my install directory, ran "awe_designer.exe" in an admin command prompt and received the same error without any additional text in the command prompt window.

I then re-installed awe, it installs and then installs the MCR that was included in the download, no awe_designer_mcr directory was created again and I have the same failure.

 

thanks for jumping in.

Jerry 

 

cncjerry
Offline
Last seen: 4 months 1 week ago
Joined: 07/04/2018 - 2:39pm

one other question, should it be installing the 64bit on my Surface which is a 64bit machine?

Axel Nilsson
Offline
Last seen: 2 hours 11 min ago
Joined: 12/19/2016 - 2:02pm

No, the 32-bit version is correct because it depends on the bitedness of the MATLAB edition used to compile the program, not the machine's OS.

 

We are actually finishing up the testing on a new release of Designer, due out sometime this week. This new version uses a newer edition of MATLAB (64-bit) to compile the program, so it may be that your issue is fixed by weeks end. 

I'm not sure how to debug this further right now since we can't reproduce it here, and it seems to be an issue with the MCR and not Designer. Perhaps you could try installing on a different machine, if you have one available. Otherwise, I would wait until 6.18.02 is available. 

 

cncjerry
Offline
Last seen: 4 months 1 week ago
Joined: 07/04/2018 - 2:39pm

I copied the 64bit version of launchermain.dll into the install directory and then the error was that it couldn't find mclmcrrt8_4.dll.  I copied that as well into the install directory and the same error remains.

Given the surface is a 64 bit machine, should I be installing the 64bit of the MCR?  I assume so, but it doesn't look like the program is trying to use those dlls.

 

Jerry

 

cncjerry
Offline
Last seen: 4 months 1 week ago
Joined: 07/04/2018 - 2:39pm

I have several computers and will give it a shot.  If they have the same problem then I'll wait for the new version.

Thanks.

Jerry