COM Interop Reference Problem

[mdwg2020]

Guys,

Quick question. I'm writing a quick .NET application that will have to call an API from a COM component. So it is pretty simple to setup on the development machine. Running and compiling on the DEV machine, everything works well.

Once I move the code to a QA region it does not work. Now my thinking is that the difference between the two is that between the two boxes, the COM component has a different path. PROD machine is also a 2000 server vs. an XP box for development (I tried adding aspcompat="true" and that didn't work).

My question would be first, if this would cause a problem? If so, how do you handle this if you don't have access to VS on a PROD box to compile with the correct COM Reference path?

Thanks,

Brooks Yates

 

[mdwg2020]

For anyone who can help. Here is the error I get on the Web Server:

Unable to cast COM object of type 'WSOPTIMIZERAGENTLib.OptimizerAgentClass' to interface type 'WSOPTIMIZERAGENTLib.IOptimizerAgent'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{FC09D202-8786-11D6-9C72-0050047492AD}' failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)).

I do not get this on my development machine which is running XP. I copied the entire web directory from that machine over to the box that is having a problem. Then I used INETMGR to set it up as a .NET application, but nothing seems to work.

I'm still woried it has something to do with the COM Reference.

Thanks,

Brooks Yates

 

[mdwg2020]

This happened to be a security permission for everyone else. It looks like I had to beef up the permissions to the IWAM account for it to be able to load the .dll.

Thanks,

Brooks Yates