Craig,
Yes and yes. Have you done this sort of a setup before? I tried including everything( mtdll.,.vbr, and .tlb in addition to the .msi) just to see if it would work, but it didn't. Is it possible it's looking for something in a specific path on the target machine?

My end goal is to create a .msi setup for a web COM+ app that I can just distribute without the end-user having to do any tweaking. The key thing is that the .msi setup uses the Interactive account in order to give the app enough security to write to DBFs..... That's why I need to do it this way. A previous solution for NT was to use the RevertToSelf() API, but, that doesn't work on 2000 any more in the default web server config. (sorry that this is kind of complicated!)

>Did you create a server export? Is the VFP runtime installed on the target machine?
>
>
>>I've created a COM+/MTS web App that I'm trying to export it so I can run the resulting .msi installation of the MTDLL component on another computer(that computer will run this MTS app with their web server). Has anybody successfully done this on Windows 2000?? When I copy the .msi to the new machine and click it, it says 'Error registering COM+ Application' with no additional info....
>>
>>I know this can be done manually, but, I'm trying to create a COM+ web server App I can distribute. There's even an article on the MS site ( http://support.microsoft.com/support/kb/articles/Q191/6/23.ASP ), but, it's for NT/MTS. Everything seems to indicate that it should be easily done....
>>
>>Also, this is not a client app - it's a web server app that people will access thru a web browser...