>Ok, I'm stumped.
>
>Years ago, I created a COM EXE which is called from my ASP.NET app to generate documents to PDF files. The COM object has been working perfectly for years, and still does. Recently the company was acquired and we're trying to move the web site to a different server. On the new server, the COM object can be initialized from my code-behind, but calls to any of it's methods results in a COM exception error:
>
> Exception type: COMException
> Exception message: The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))
>
>I'm able to instantiate the object and generate the PDF files on the same box using a simple CreateObject(). I'm also able to generate them directly from a simple ASP page using:
>
>
>The credentials the object runs under are the same as the rest of the web site. It's as if the COM wrapper referenced in the code behind does not know how to handle the method calls. Does anyone have an idea of why method calls would just stop working?
>
>Any ideas would be GREATLY appreciated - I'm stuck!

I'd suggesting checking a few things. First, make sure the user the web server runs under has permission to access the files/tables used by the COM component. Also, If the COM server creates a physical PDF file, check to make sure this user has permission to write to this folder. If you've changed versions of IIS between servers, keep in mind that the newer version of IIS runs the COM component under the same user as the AppPool is run under.