Can't load my Plug-In: The specified module could not be found.

[Anonymous]

Hello,

I'm currently working on getting a simple dependency node into Maya 2017 in C++.

When I finally build the solution in Visual Studio 2017 on my laptop, I was able to load the plugin into Maya 2017 and it worked just fine.

Now I wanted to use it at school and I got the following error message.

// Error: Unable to dynamically load : C:/Program Files/Autodesk/Maya2017/bin/plug-ins/MathNodes.mll
The specified module could not be found.
// 
// Error: The specified module could not be found.
(MathNodes)//

I used Dependency Walker to check what is missing and this is what I got:

FOUNDATION.DLL

OPENMAYA.DLL

UCRTBASED.DLL

VCRUNTIME140D.DLL

Error opening file. System can not find the file.

It is strange that it works on my laptop but on other PC's it does not.

PS:

I was using this blog post to set up my Visual Studio for Maya maybe there is something I set wrong for Maya 2017 ?

http://blog.josephkider.com/2015/08/20/creating-your-first-maya-plug-in-in-visual-studio/

[cheng_xi_li · Accepted solution]

Hi,

Maya 2017 is compiled with VS2012 so please stick with VS2012 compiling environment. On other computer probably missing VC2015 and Universal CRT runtime library.

If you want to run it on a computer with only Maya 2017 installed. The plugin should be compiled with VS2012 and a Release configuration.

Yours,

Li

[Anonymous]

Sorry ,The plugin should be compiled with VS2012 and a Release configuration.I don't understand this.Can you tell me more about this.

[cheng_xi_li]

Hi,

Maya 2017 was built with VS2012 and it is shipped with VC2012 runtime library(release). 

If you wanted your plugin has no issue when running with Maya 2017, it'd be better to compile with VS2012. There are two reasons for it.

1. Mixing 2012 with other vcruntime is a bad idea as this article suggests.  Microsoft had also published a blog about mixing binaries built with different VC runtime. Mixing release and debug runtime in production could also lead to unpredictable result. Some libraries will provide runtime for debug/release settings(e.g. Qt/VC has a d suffix for debug libraries).

2. Maya 2017 is shipped with VC2012 runtime(without debug), so you won't have to install another runtime library on client machine.(VC2015 for Maya 2018, 2019)

Yours,

Li