The problem that this article discusses occurs when an MTS component is opened as a Server Package. In this case, the component is created in the Mtx.exe isolated process space. By default, Mtx.exe is located in the %SystemRoot%\System32. Therefore, Mtx.exe cannot find your DLL unless your DLL is in the search path.
When you create a DLL that is called from an MTS component that is opened as a Server Package, you are supposed to deploy your DLL in the %SystemRoot%\System32 folder. You want to do this so that this problem does not occur.
Note When you open an MTS component, you have the following packages to select between:
- Library Package
Components are opened in the creators process.
- Server Package
Components are opened in a dedicated server process.
Article ID: 240416 - Last Review: Oct 11, 2005 - Revision: 1