Retrieving the COM class factory for component with CLSID failed due t

[Daff]

I have a simple code which creates object of the ApplicationClass from the Microsoft.Office.Interop.PowerPoint. I reference Microsoft.Office.Interop.PowerPoint dll ver. 11 from the local folder. This code runs on the machines with different set of the installed versions of the Power Point (2003, 2007 and 2010 in all possible combinations). On all machines everything is OK. But on the machine with installed Power Point 2007 and 2010 constructor of the ApplicationClass throws COM exception with next message "Retrieving the COM class factory for component with CLSID "[some CLSID]" failed due to the following error: 80010100". Google keep silent concerning this error. There is a lot of information concerning "Retrieving the COM class factory for component with CLSID "[some CLSID]" failed due to the following error" and "80010100" separately. But it doesn't answer my question. I have only found that "80010100" error means " System call failed". Also I have tried to mark thread entry point with STAThread attribute and use another versions of the interop dlls . I haven't any thoughts how to solve this problem. Help, please!

Now code is extremely simple:

using Microsoft.Office.Interop.PowerPoint;

class Program

    {

        static void Main(string[] args)

        {

            var app = new ApplicationClass();

        }

    }

[cluberti]

For what it's worth, that error is:

# for hex 0x80010100 / decimal -2147417856 :
  RPC_E_SYS_CALL_FAILED                                         winerror.h
# System call failed.

Given making a call to the interop gives that error, I am guessing you are doing this from an asp.net app or inside a COM application itself - I may be wrong, but I can't think of how you'd run into this from an actual user session in a .net app. You might want to take a look at this KB, and make sure you're OK with where you are. My guess is this is failing with a user permissions error, rather than the generic error that bubbles up. You could run procmon on the client and see what you might see, but it's worth noting Microsoft doesn't support what you're doing, so you're on your own at this point. Again, given the fail, it's either a problem running it inside a service and breaking out to COM, or a permissions issue (or both) likely.