Set COR_PROFILER_PATH env variable but no start my profiler

linq.x 6

I setup a profiling environment by set environment variables: COR_ENABLE_PROFILING, COR_PROFILER, COR_PROFILER_PATH on .net 4.0+ without my profiler being registered.

I found my profiler dll is not loaded by clr, why?

Xingyu Zhao-MSFT 5,361 Reputation points

2021-05-17T01:38:39.33+00:00
Hi @linq.x ,
Take a look at the following references:

Setting Up a Profiling Environment

.NET Profiling API initialization

Hope them could be helpful.
linq.x 6 Reputation points

2021-05-17T03:00:55.433+00:00

Hi, thanks for your anwser. COR_PROFILER_PATH env is set, but according to eventlog, it got the message(0x80040154 may means COR_E_BADEXEFORMAT):

.NET Runtime version 4.0.30319.0 - 在 CoCreateInstance 期间加载探查器失败。探查器 CLSID:“{22B677AD-2950-4169-B330-633D8DBBDE9F}”。HRESULT: 0x80040154。进程 ID (十进制): 2648。消息 ID: [0x2504]。
linq.x 6 Reputation points

2021-05-17T03:29:01.747+00:00

sorry, 0x80040154 is REGDB_E_CLASSNOTREG, I think is that setting env COMPLUS_ProfAPI_ProfilerCompatibilitySetting to EnableV2Profiler makes REGDB_E_CLASSNOTREG. When I remove env COMPLUS_ProfAPI_ProfilerCompatibilitySetting, it got another HRESULT 0x800700c1, which means COR_E_BADEXEFORMAT
Xingyu Zhao-MSFT 5,361 Reputation points

2021-05-18T01:39:13.06+00:00

Hi @linq.x ,

0x80040154 is REGDB_E_CLASSNOTREG

It seems that you need to register your com object under 'Wow6432Node'.
See : .Net Profiler - CoCreateInstance Failed
Another reference you may need:
How to solve COM Exception Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))?

Share via

Set COR_PROFILER_PATH env variable but no start my profiler