License Checkout error in standalone application

I've been given a bunch of p-code that I'd like to compile into a .dll. I used the matlab compiler from the GUI, I added all the p-code to the project, made sure all matlab toolboxes were on the path and built the .dll by pushing build.

Then I proceeded to program something in C++ in Visual Studio 2010 that will call into the shared library. I had to include the auto-generated header and lib file as well as mclmcrrt.lib from the 64-bit MCR in the visual studio compile.

When I run the result visual studio .exe, I get an error from the matlab compiled .dll that says "Unable to checkout license file for pathManager.p" (a file in my code). Why is this? I thought the point of the MCR was to be able to deploy standalone applications?

I did not write the p-code. Is it possible they used a toolbox that I don't have on my path?

Thanks in advance for any insight.

[Aaron]

I should note that I can execute the p-code when it isn't compiled into a .dll so it probably isn't a toolbox problem.

[Walter Roberson]

Note: after a run (from the MATLAB prompt) you can figure out which toolboxes were used by using

license('inuse')

[Aaron]

I also used depfun() to list all dependencies the offending p file used and I do have all of the toolboxes.

[Aaron]

I also have the full version of the matlab compiler, not the demo version.