Error code: 14001 when loading plugin with 3ds Max 9

[Anonymous]

I'm compiling a plugin for other people, and the plugin loads fine in 3ds Max 9 for me. But when other people try using the plugin, they get this error:

DLL <C:\Program Files\Autodesk\3ds Max 9\PlugIns\aaaaaaa.dle> failed to initialize.

Error code: 14001 - This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.

I have Windows XP 32bit installed, and I use Visual Studio 2005 to compile the plugin.
The people who cannot run the plugin also have Windows XP 32bit, but do not have Visual Studio 2005 installed.

What could be causing this issue?

[PAMD76]

Sounds like your plugin could be trying to find a .dll, if you drop your plugin into Dependency Walker you'll be able to see what dll's it requires.

You can download it here: http://support.microsoft.com/kb/256872

[Anonymous]

According to that program, the plugin is missing the following DLL's:

ATL80.DLL
DWMAPI.DLL
MFC80.DLL
MSVCP80.DLL
MSVCR80.DLL

I downloaded the above DLL's and placed them into C:\Windows\system32 on the machine that is having this error. Dependency Walker then gives no errors. However, Max 9 still displays the same error when loading the plugin. What exactly does the error mean? Could there be other dependencies?

[PAMD76]

Ah ok, in that case it sounds like you need the VS2005 run time installing on the machine you're trying to run it on.

Download: http://www.microsoft.com/downloads/details.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647&displa...

...that should fix it.

[Anonymous]

ok, thanks. I just tried that on the target machines and they get the same error. This is a REALLY old plugin that I am trying to update. Is it possible that it's using some outdated libs?

From
Configuration Properties->Linker->Input->Additional Dependencies:

d3d9.lib
d3dx9.lib
dinput8.lib
dxguid.lib
bmm.lib
winmm.lib
dsound.lib
MNMath.lib
msacm32.lib
odbc32.lib
odbccp32.lib
comctl32.lib
core.lib
geom.lib
gfx.lib
mesh.lib
maxutil.lib
maxscrpt.lib
paramblk2.lib

[PAMD76]

Ok, try installing the DirectX SDK (same version you built with) onto the target machines, you won't need to install all of it just the runtime, I had an issue like this a while ago and this fixed it...I can't remember but it could have been a debug build so it was probably looking for debug .dll's, anyway it's well worth a go.

[PAMD76]

...oh and make sure you've got the .NET framework runtime installed on the targets as well.

[Anonymous]

ok, I think I am getting closer to the problem. I installed the redistributable packs for the same version of DirectX (June 2008) that I used to compile as well as the .NET Framework on the target machines, and I still got the same error. HOWEVER, as a test, I installed Visual Studio 2005 (plus SP1) on one of the problem computers, and THEN it worked fine.

So, the question now is --- what are the differences between the redistributable packs and actual Visual Studio that would cause such errors? Debug DLL's perhaps?

[PAMD76]

Ah ok, if the plugin is a debug build then yes, thats the problem or if you've linked with any debug libs in the release build (which I imagine isn't likely, worth a check though).

Also, in your solution go to properties->Manifest Tool->Input and Output->Embed Manifest needs to be YES.

[PAMD76]

For another test you could copy the .dll's from "C:\Program Files\Microsoft Visual Studio 8\VC\redist" to the same directory as your plugin. In this folder you'll find the debug versions as well. This should be all the .NET stuff you'll need...I think.

[Anonymous]

It's finally working 🙂 You were right -- since the plugin is a Hybrid, I had to copy over some of the stuff in C:\Program Files\Microsoft Visual Studio 8\VC\redist\Debug_NonRedist directory into the plugins directory. Thanks for your help!

[PAMD76]

Great news, as I was running out of ideas!

[Anonymous]

Out of curiosity, did you build the plugin with VC 2005 RTM (the stock version), or VC 2005 SP1?

[Anonymous]

I'm aware this is not the most recent thread, but I#m running out of ideas to solve the same problem. The only difference is that
- I'm not running a debug build or link to any debug libs
- tried installing latest Direct X redistr
- tried installing latest .Net redistr
- tried installing latest VS redistr
- Dependency walker shows no other unfamiliar libs
- I will kill my pet if this doesn't work by tomorrow. Grrrrrrr

Working with Max 9 SP1 and visual studio 2005 SP1 with the according SDK.
Any ideas anyone?
Cheers,
Gunnar

[Anonymous]

Well, all my cockroaches survived thanks to finding this thread:
http://channel9.msdn.com/forums/TechOff/22266-Side-by-side-screwup/
The problem was solved by setting the flag for the generation of the manifest file to "No" in the project settings.
Might help someone one day. =&#41;