Hi Jeff.

Your approach is pretty smart, and here and your post is the first time I see anybody talk about component permissions (after 2 days of pretty intensive research on this issue.)

Anyway, in my case the problem is also a security/permission issue. I am working on a website that uses Google Desktop Query API to query my Google Desktop and show results in the web browser.

Interestingly, when I create the website on the location "File system", ASP.NET does not have any problem, whatsoever, to access, read, execute, launch, or whatever it needs to do to this dll. The whole thing runs smoothly and perfectly. As soon as I copy my website to another folder and direct IIS to serve that folder (as a virtual directory), the application fails:

Retrieving the COM class factory for component with CLSID {F4CADDD3-B30C-4D9C-97E4-AE92F1A6D340} failed due to the following error: 80040154.

I have checked out that Component Services section you have talked about. In my case, this CLSID does not exist there, and the reason, probably, is that this reference I have in my website is to one of the DLLs of Google Desktop. In Component Services there is a Google Desktop entry, whose security settings I already changed to allow ASPNET user launch and access and activate it... But that hasn't taken care of the problem.

I wonder what I need to do to make this COM referencing possible. I know if my problem was due to an unregistered or non-existing DLL, then my "FILE SERVER" hosted website would fail too. But, here, then only thing I suspect is the security settings.

I greatly appreciate any help anybody can provide to solve this situation :)