blocks|key|235167|text|经过多次搜索，我发现有人之前安装了dotTrace，然后卸载了它，但是卸载并不是很干净，导致注册表中到处都是条目，尽管我们已经删除了一些我们认为可以解决问题的条目，但更多的条目是针对该分析器的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|235168|删除所有与dottrace相关的注册表项和它显示的CSID后，错误不再出现在事件查看器中。|235169|有关帮助查找此类条目的脚本，请参阅以下答案：https://stackoverflow.com/a/36129656/361842|offset|length|235170|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/36129656/361842^0|0|0|M|17|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

After much searching I found that someone had previously installed dotTrace, then uninstalled it, however the uninstall wasn't very clean and had left the registry littered with entries, though we'd removed some entries we thought could stop the problem there were more specific to that profiler.

After removing all registry entries related to dottrace and the CSID it presented we no longer have the error appearing in the event viewer.

See this answer for a script to aid in hunting down such entries: <a href="https://stackoverflow.com/a/36129656/361842">https://stackoverflow.com/a/36129656/361842</a>

blocks|key|3107458|text|从用户变量(控制面板>系统>高级系统设置>环境变量)中删除环境变量COR_ENABLE_PROFILING+(或将其设置为0)解决了我的问题(无法启动MongoVUE)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3107459|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Removing Environment variable COR_ENABLE_PROFILING (or set it to 0) from User variables (Control panel > System > Advanced system settings > Environment variables) solved my problem (Could not start MongoVUE)

blocks|key|229739|text|虽然在注册表中删除对分析器的CLSID的所有引用并不是一件坏事，但是您也可以选择通过将注册表项HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\COR_ENABLE_PROFILING设置为0来禁用分析|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|229740|entityMap^0|1B|20|3E|1|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

While removing all the references to the profiler's CLSID in the registry can't be a bad thing, you can also choose to just disable profiling by setting the registry key <code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\COR_ENABLE_PROFILING</code> to <code>0</code>

blocks|key|229786|text|为了帮助查找可能使用此工具的位置，可以使用以下PowerShell代码来帮助检测与探查器相关的环境变量和注册表项：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|229787|clear-host
if+(-not+(get-psdrive+HKU))+{
++++New-PSDrive+HKU+Registry+HKEY_USERS
++++Set-Location+HKU:
}
"COR_ENABLE_PROFILING:+$env:COR_ENABLE_PROFILING+"
"COR_PROFILER:+$env:COR_PROFILER"
$GUID+=+$env:COR_PROFILER
@(
++++"HKLM:\Software\Classes\CLSID\$GUID",
++++"HKLM:\SOFTWARE\Classes\Wow6432Node\CLSID\$GUID",
++++"HKLM:\SOFTWARE\Wow6432Node\Classes\CLSID\$GUID",
++++"HKU:\*\Software\Classes\CLSID\$GUID"
)+%7C
++++get-item++%7C+
++++%25{$p+=+$_.Name;Get-ItemProperty+$_.PSPath+''}+%7C+
++++select+@{N='Path';E={$p}},+'(default)'

get-itemproperty+'HKLM:\SYSTEM\CurrentControlSet\Services\*\'+'Environment'+-ea+SilentlyContinue+%7C+
++++%25{
++++++++$serviceName+=+$_.PSChildName
++++++++$x+=+new-object+PSObject+-Property+@{ServiceName=$serviceName}
++++++++$_+%7C+select+-expand+Environment+%7C+
++++++++++++%25{if($_+-match+'%5E(?<Name>[%5E=]%2B)(=)?(?<Value>.*)$'){$x+%7C+Add-Member+-MemberType+NoteProperty+-Name+$matches['Name']+-Value+$matches['Value']}}
++++++++$x
++++}+%7C
++++?{$_.COR_ENABLE_PROFILING+-eq+1}+%7C+
++++ft+ServiceName,+COR_ENABLE_PROFILING,+COR_PROFILER,+NEWRELIC_INSTALL_PATH+-AutoSize|code-block|syntax|javascript|229788|希望将来能帮助到其他人。|229789|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

To help find where this tool may be used, the below PowerShell code can be used to help detect environment variables and registry entries relating to the profiler:

<pre><code>clear-host
if (-not (get-psdrive HKU)) {
 New-PSDrive HKU Registry HKEY_USERS
 Set-Location HKU:
}
"COR_ENABLE_PROFILING: $env:COR_ENABLE_PROFILING "
"COR_PROFILER: $env:COR_PROFILER"
$GUID = $env:COR_PROFILER
@(
 "HKLM:\Software\Classes\CLSID\$GUID",
 "HKLM:\SOFTWARE\Classes\Wow6432Node\CLSID\$GUID",
 "HKLM:\SOFTWARE\Wow6432Node\Classes\CLSID\$GUID",
 "HKU:\*\Software\Classes\CLSID\$GUID"
) |
 get-item | 
 %{$p = $_.Name;Get-ItemProperty $_.PSPath ''} | 
 select @{N='Path';E={$p}}, '(default)'

get-itemproperty 'HKLM:\SYSTEM\CurrentControlSet\Services\*\' 'Environment' -ea SilentlyContinue | 
 %{
 $serviceName = $_.PSChildName
 $x = new-object PSObject -Property @{ServiceName=$serviceName}
 $_ | select -expand Environment | 
 %{if($_ -match '^(?&lt;Name&gt;[^=]+)(=)?(?&lt;Value&gt;.*)$'){$x | Add-Member -MemberType NoteProperty -Name $matches['Name'] -Value $matches['Value']}}
 $x
 } |
 ?{$_.COR_ENABLE_PROFILING -eq 1} | 
 ft ServiceName, COR_ENABLE_PROFILING, COR_PROFILER, NEWRELIC_INSTALL_PATH -AutoSize
</code></pre>

Hope that helps others in future.

blocks|key|2893775|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2893776|📷|atomic|offset|length|2893777|2893778|使用HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\IISADMI‌​N+|2893779|在错误日志中搜索|ordered-list-item|2893780|+COR_PROFILER及其值|2893781|+Cor_Enable_Profiling=1+to++Cor_Enable_Profiling+|2893782|COR_PROFILER|2893783|Cor_Enable_Profiling=1+to+regedit+删除以下任一设置:Cor_Enable_Profiling+HKEY_LOCAL_MACHINE\SYSTEM\Services\W3SVC+regedit|2893784|2893785|这样做可能会导致IIS无法启动。有关更多详细信息，请参阅this+question。|2893786|您可能还需要删除/禁用其他用户和系统变量。尝试先禁用(COR_ENABLE_PROFILING+=+0)+delete+if+error+disabling。希望这能有所帮助。感谢@Andreas和@Mike-Monkey的初步指导。|unordered-list-item|2893787|2893788|2893789|2893790|2893791|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/872850373084a89c51df7e78ba4e79e2.png|imageAlt|1|LINK|MUTABLE|url|https://serverfault.com/questions/210903/windows-process-activation-service-wont-start-parameter-is-incorrect-visual/210912|2|https://ask.qcloudimg.com/http-save/yehe-900000/1515e4f5c0d20dc71dec220a26cab122.png^0|0|0|1|0|0|0|0|0|0|0|0|0|0|S|D|1|0|0|0|0|0|1|2|0|0^^$0|@$1|2|3|4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1L|8|@]|9|@$E|1M|F|1N|1|1O]]|A|$]]|$1|G|3|4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1R|8|@]|9|@]|A|$]]|$1|M|3|N|5|L|7|1S|8|@]|9|@]|A|$]]|$1|O|3|P|5|L|7|1T|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1U|8|@]|9|@]|A|$]]|$1|S|3|T|5|L|7|1V|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1X|8|@]|9|@$E|1Y|F|1Z|1|20]]|A|$]]|$1|X|3|Y|5|Z|7|21|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|22|8|@]|9|@]|A|$]]|$1|11|3|4|5|6|7|23|8|@]|9|@]|A|$]]|$1|12|3|C|5|D|7|24|8|@]|9|@$E|25|F|26|1|27]]|A|$]]|$1|13|3|4|5|6|7|28|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|29|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|1B|1C|-4]]|1D|$5|1E|18|1F|A|$1G|1H]]|1I|$5|17|18|19|A|$1A|1J|1C|-4]]]]

<a href="https://i.stack.imgur.com/jjcTp.png" rel="noreferrer"><img src="https://i.stack.imgur.com/jjcTp.png" alt="regedit"></a>

<ol>
<li>Use regedit do a Data search for the CLSID value in the error log</li>
<li>Remove COR_PROFILER and its value</li>
<li>Change Cor_Enable_Profiling=1 to Cor_Enable_Profiling=0</li>
<li>Do not remove the Cor_Enable_Profiling setting for any of the following:

<pre><code> HKEY_LOCAL_MACHINE\SYSTEM\Services\WAS
 HKEY_LOCAL_MACHINE\SYSTEM\Services\W3SVC
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\IISADMI‌​N
</code></pre>

Doing so may cause IIS to fail to start. See <a href="https://serverfault.com/questions/210903/windows-process-activation-service-wont-start-parameter-is-incorrect-visual/210912">this question</a> for more details. </li>
<li>You may also need to remove/disable additional User and System variables. Try disabling first (COR_ENABLE_PROFILING = 0) delete if error persist. Hope that helps. Thank you @Andreas and @Mike-Monkey for the initial guidance.</li>
</ol>

<a href="https://i.stack.imgur.com/ilpBC.png" rel="noreferrer"><img src="https://i.stack.imgur.com/ilpBC.png" alt="Environment Variables"></a>

blocks|key|2893719|text|对我们来说，COR_ENABLE_PROFILING在多个地方|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2893720|HKEY_LOCAL_MACHINE\SYSTEM\Services\W3SVC和HKEY_LOCAL_MACHINE\SYSTEM\Services\WAS|2893721|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

For us COR_ENABLE_PROFILING was at multiple places 

HKEY_LOCAL_MACHINE\SYSTEM\\Services\W3SVC and HKEY_LOCAL_MACHINE\SYSTEM\\Services\WAS

blocks|key|229791|text|Stackify+Profiler也会对你做同样的事情。:(，我发现很难从注册表中删除。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|229792|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Stackify Profiler Will also do the same thing to you. :(, I am finding it difficult to remove from the registry.

blocks|key|233785|text|在尝试启动Windows服务时，我们会时不时地看到此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|233786|这个问题总是导致可执行文件的app.config损坏(无效的xml)。|233787|在开始编辑注册表设置之前，仔细检查您的app.config是否有效是一件快速、简单的事情。|233788|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

We see this problem from time to time when trying to start Windows Services. 
This issue is invariably that the app.config for the executable is corrupt (not valid xml). 
Double checking that your app.config is valid xml is a quick easy thing to check before heading of to edit registry settings..

blocks|key|2893823|text|即使在做了Agnes在Answer中提到的事情之后，事情仍然不起作用。在我的例子中，我将我的应用程序池设置为一个帐户，而它的密码已过期……|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2893824|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/22373643/740756^0|B|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Things did not work even after doing what mentioned in <a href="https://stackoverflow.com/a/22373643/740756">Answer</a> from Agnes. In my case, I had my application pool set to an account and it's password was expired...

We're getting a:

<blockquote>
 .NET Runtime version 2.0.50727.5448 - Failed to CoCreate profiler
</blockquote>

message in the Event Viewer on our webserver, along with an accompanying:

<blockquote>
 .NET Runtime version 4.0.30319.239 - Loading profiler failed during CoCreateInstance. Profiler CLSID: '{d37a1b78-6dc5-46fc-bc31-f7c4d5a11c9c}'. HRESULT: 0x8007007e. Process ID (decimal): 224. Message ID: [0x2504].
</blockquote>

The thing is, we're not trying to use a profiler, there are no profiler's running or installed on the server and the code makes no reference to profilers anywhere...

We've tried removing the registry keys that other's have pointed out are related to these messages but to no avail; it would seem that two of our websites/webapps are firing off the error, one using .Net2 and the other using 4, but I'm not sure where to look.

Failed to CoCreate Profiler error - but not using a profiler

服务器

Windows

我们得到了一个： .NET运行时版本2.0.50727.5448 -无法CoCreate探查器在我们的our服务器上的事件查看器中的消息，以及随附的： .NET运行时版本4.0.30319.239 -在CoCreateInstance期间加载探查器失败。探查器CLSID：'{d37a1b78-6dc5-46fc-bc31-f7c4d5a11c9c}‘。HRESULT: 0x8007007e。进程I

问无法CoCreate事件探查器错误-但未使用事件探查器
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法CoCreate事件探查器错误-但未使用事件探查器EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法CoCreate事件探查器错误-但未使用事件探查器
EN