Profiling a medium-trust ASP.NET application - get CoCreateInstance failure

Question

My profiler (using the ICorProfiler* implementation) cannot run against an ASP.NET application running in medium-trust level. The error is

 .NET Runtime version 4.0.30319.269 - Loading profiler failed during CoCreateInstance.  Profiler CLSID: '{FF68FEB9-E58A-4B75-A2B8-90CE7D915A26}'.  HRESULT: 0x8007007e.  Process ID (decimal): 772.  Message ID: [0x2504].

I've looked at creating a custom .NET trust configuration file but cannot find any way to get around this problem. Does anyone know if there is a way to do this?

Thanks,

 Bob

Answer 1

Hi Bob-Uva,

Welcome to the MSDN Forum.

How about this thread: http://social.msdn.microsoft.com/Forums/pl-PL/netfxtoolsdev/thread/01b48127-d955-4fbb-a08f-82ac6ead67e6 

Please take a look at Shaun's answer, I hope it will be helpful.

Best regards,

---

Mike Feng
MSDN Community Support | Feedback to us
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 2

Hi Mike,

I read through that post and I'm fully-compliant with all of the COM registration for x86 and x64. In fact, we've been using our profiler successfully in both environments on a 64-bit OS as well as x86 on x86 OS. 

I purposely set the trust level of a test application to medium trust and that's when I get the CoCreateInstance failure.

Bob

Answer 3

Try this tool to find the root cause: http://ncover.com/support/docs/v3/kb/how-to-track-down-failed-to-cocreate-profiler

---

Ghost,
Call me ghost for short, Thanks
To get the better answer, it should be a better question.