That error could happen when there is a Threading problem. Look at AspCompat
attribute of the @Page directive, maybe can help.
Idael.
> Hi everyone,
>
> We are trying to access a remote COM object in our asp.net application and are running into difficulties. We keep receiving the error: QueryInterface
for interface "dll.className" failed. This error occurred when we deployed
the application to our test servers. During our development cycle, we
performed the following steps to work around this problem:
> 1. Exported the COM object and installed it on the client.
> 2. Imported the COM object into our project using VS.NET studio 2002. Studio automatically created the RCW wrapper called "interop.COM".
> 3. Change the account that the Aspnet_wp.exe process runs under to the System account in the <processModel> configuration section of the
application host's Machine.config file.
> This seemed to correct the problem. All calls to COM object through the RCW wrapper worked successfully, and development continued.
>
> Now, however, upon deploying the application to our test server which has a different operating system, and runs under a different network domain, we
are again receiving this error. We have tried the following steps to solve
the problem (or to get the application to just work):
> 1. Attempted to impersonate an domain administrator account that has full security and access privleges.
> 2. Granted both the ASP.NET and Administrators accounts to "act as part of the operating system".
[quoted text clipped - 5 lines]
>
> Chris...