Re: QueryInterface for interface xxx.yyy failed
From: Idael Cardoso (nospam.yetiicb_at_hotmail.com)
Date: 04/24/04
- Next message: Idael Cardoso: "Re: property type BSTR not returned correctly in C#"
- Previous message: Idael Cardoso: "Re: marshal array of structure into a com component"
- In reply to: Chris: "QueryInterface for interface xxx.yyy failed"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 24 Apr 2004 13:48:30 +0200
That error could happen when there is a Threading problem. Look at AspCompat
attribute of the @Page directive, maybe can help.
Idael.
"Chris" <chrisb@REMOVE_SPAM_CAPSpapex.com.REMOVE_THESE_CAPS> wrote in
message news:0EF08A0F-DD5D-43D0-839E-2E14BE81F7D2@microsoft.com...
> 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".
> 3. Attempted to give full trust the the RCW interop assembly.
>
> None of these steps have solved the problem. If anyone knows what we are
missing here, or can point us in the right direction, please let me know.
>
> Thanks,
>
> Chris...
- Next message: Idael Cardoso: "Re: property type BSTR not returned correctly in C#"
- Previous message: Idael Cardoso: "Re: marshal array of structure into a com component"
- In reply to: Chris: "QueryInterface for interface xxx.yyy failed"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
