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?