locked
ASP to COM to .NET Interoperability Problem RRS feed

  • Question

  • We have an ASP application which needs to access a .NET application

    through COM. We have implemented this interface with a multithreaded

    COM object written in C++ which accesses a .NET dll written in C#

    through a COM interface. The .NET dll contains interface code to the

    .NET application to be accessed by ASP application. We found

    everything works fine with this implementation until we ran load

    stress tests where we find the ASP application fails fairly quickly

    with type mismatch(13) error. From our debugging on the problem so

    far we find that when the failure occurs the ASP application is

    failing on CoCreate of the COM object. All further access to COM

    fails in same way. We have tried running the C++ COM object under VS

    debugger where we find a memory access violation error. The failure

    appears to be in the ASP to COM interface. We have not been able to

    learn any more than that.

     

    Does anyone have any insight in what may be wrong?

     

    The application we have designed involves unmanaged C++ code in COM

    object and managed C# code in .NET dll. Is there anything involving

    memory access that we need to look into?

    Thursday, May 29, 2008 3:47 PM

Answers

  • We found the problem. We discovered a memory leak in C++ COM component.

     

    • Proposed as answer by orcmid Tuesday, June 24, 2008 12:06 AM
    Monday, June 2, 2008 1:52 PM

All replies

  • Thank you for using the Interoperability Forum.  Your request has been routed to a Subject Matter Expert and a response is expected to be generated by Monday, June 2, 2008.  By then you should receive a response or your post may be moved to a more appropriate location that is better suited to answer your specific question.

     

     

    Saturday, May 31, 2008 2:43 AM
  • We found the problem. We discovered a memory leak in C++ COM component.

     

    • Proposed as answer by orcmid Tuesday, June 24, 2008 12:06 AM
    Monday, June 2, 2008 1:52 PM