Invalid MEX-file: The specified module could not be found. For PolygonClip.mexw64

I get this error message when trying to run a .m file that referes to PolygonClip.mexw64. The mex-file is present in the current path.

I tried 2012a and 2012b, I reinstalled both versions, I run Matlab as an administrator, I have replaced the mex file, ran dependency walker(I get identical dependencies compared with a pc on which the calculation runs), placed libmx.dll and libmex.dll in the current path,...

I have replaced the "appdata", 'bin', 'etc', 'extern', "resources' folders that are located in Program Files\Matlab\2012a\** from another computer on which the .m file and calculation run without any problems but to no avail.

We are currently out of ideas.

Thank you for the assistance.

[Walter Roberson]

http://www.dependencywalker.com/help/html/application_profiling.htm

https://github.com/lucasg/Dependencies

Answer 1

[Jan]

The DependencyWalker sounds like the best option to solve the problem. Of course you get the same dependencies for the same file. But do these dependencies exist on both computers? I guess a redistributable is missing. Do you have the source codes? Then recompile the C file.

Does this concern this file: https://github.com/davheld/GOTURN/blob/master/scripts/Fscore_v1.0/polygonClipper/PolygonClip.mexw64 ?

It needs e.g. the MSVCR100.DLL. This library belongs to the MSVC 2010 compiler. Compiled Mex files are not backward compatible in general with older Matlab versions. Compiling a C function in R2016b let my Matlab 2009a crash. So maybe the core of the problem is contained in "R2012a and R2012b". An upgrade of Matlab might solve the problem, or a recompilation on your machine.

[Steven Deckers]

Thank you for the answer. I have some things that I need to clarify:

A colleague had the exact same Matlab version installed on his own pc and he does exactly the same things and uses the same files, but without experiencing any problems or error messages.

Running dependency walker on his pc triggers the same messages. Therefore I do not think dependency walker can lead to the cause, since everything is working on his machine.

I'll try the compiling somehow.

I cannot find the MSVCR100.DLL

(I just saw another message was given while i was typing)

[Steven Deckers]

We do not have any source code so recompiling is not possible, so we are stuck.

Is a workaround possible by placing the MSVCR100.DLL in the search path? Not that I have the file, I am just speculating.

[Jan]

@Steven: It is still not clear, if you have used the DependencyWalker correctly. Of course it displays the same dependencies on all computers, because this is a property of the MEX file. The question is, if these dependencies exist on the failing computer. If you mention, that you cannot find the MSVCR100.DLL, this seems to be the problem. Then simply install the MSVC 2010 redistributables:

https://www.microsoft.com/en-us/download/details.aspx?id=14632 (64 bit)

You can install the MSVC 2010 compilers also.

Does this solve the problem?

It would be useful if you mention, where the failing mex file is coming from. This is more efficient then letting the readers search.

[Steven Deckers]

Hi Jan,

Installing the MSVC 2010 redistributables solved the problem.

Thank you very much!