>>>Hey JCF,
>>>
>>>I'm working with Tom on this one. The instance of the remote object is not even created. When he tries to do the CREATEOBJECT() the error message is returned. The .SetComplete and .SetAbort have nothing to do with the error because the object doesn't even instantiate. The class is set to nultiuse and compiled into a multithreaded DLL.
>>>
>>>>
>>>>- Are your classes set to multiuse?
>>>>- Did you compiled into multithreaded DLL?
>>>>- Are you doing .SetComplete and .SetAbort?
>>>>
>>>>Normally abscence of SetComplete and SetAbort does not necessarily give this error, but you're supposed to do it to take full advantage of MTS.
>>
>>Other things to check out (on MTS package properties):
>>- Activation set to Server package.
>>- Have you added roles to the package?
>>- Do the users on other machines have permissions to the package?
>>- What is the setting on the identity tab for the component?
>>
>>For testing, you might want to uncheck the "Enable authorization checking" on the Authorization tab. Other than the exported package that you install on client computers, you don't need anything additional.
>
>I've logged into the client machines as myself (administrative rights) and can actively browse the MTS box. We've unchecked all the authorization settings on the MTS box. Craig and I are certain that it's not a setting inside MTS because we can run it from our development machines.
>
>The activation is Server
>There are no roles
>I've logged in as myself on the machine
>We have tried both Interactive User and an administrative user
>
>Thanks,
>
>Tom

I don't have anything else to add, other than to see some KB articles: Q197814, Q186818.
If it was a security thing, the administrative user account should have taken care of that. If it is something on MTS hosted object code, try writing a text file with error info in the Error event of the class. Check if the MTS component being called becomes active at all on the MTS Explorer.