NET Framework问题(不允许附加探查器) [英] NET Framework problem(not allow a profiler to attach)

查看:323
本文介绍了NET Framework问题(不允许附加探查器)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

1201-时间:5/17/2012 8:34:32 PM
1202-来源:.NET运行时
1203-说明:.NET运行时版本4.0.30319.269-初始化分析API附加基础结构失败.此过程将不允许附加探查器. 结果:0x80004005.进程ID(十进制):4116.消息ID:[0x2509].

1201 - Time                     : 5/17/2012 8:34:32 PM
1202 - Source                   : .NET Runtime
1203 - Description              : .NET Runtime version 4.0.30319.269 - There was a failure initializing profiling API attach infrastructure.  This process will not allow a profiler to attach.  HRESULT: 0x80004005.  Process ID (decimal): 4116.  Message ID: [0x2509].

我在事件日志中得到了这个.这是什么意思,我该怎么办?(我是新手)

                   I'm getting this in Event Log. What does it mean and what can I do?(I'm a novice)

推荐答案

denautn,

Hi denautn,

当您附加到某个进程时,该进程本身不知道事件探查器,并且.NET Memory Profiler API方法未处于活动状态(即MemProfiler.IsProfiling将返回false).若要使用MemProfiler和MemAssertion方法,必须启动已配置的 通过分析器进行处理(例如,通过使用Profile Application,Profile ASP.NET或Profile Service).由于没有提及该文档,因此显然缺少该文档.但是,此信息将在以后的版本中添加.

When you attach to a process, the process itself is not aware of the profiler, and the .NET Memory Profiler API methods are not active (i.e. MemProfiler.IsProfiling will return false). To use the MemProfiler and MemAssertion methods, you must start the profiled process from the profiler (e.g. by using Profile Application, Profile ASP.NET or Profile Service). The documentation is apparantly lacking since it does not mention this. But this information will be added in a future release.

有关此的更多信息,您可以参考-  http://memprofiler.com/forum/viewtopic .php?t = 883

For more information on this, you can refer - http://memprofiler.com/forum/viewtopic.php?t=883


这篇关于NET Framework问题(不允许附加探查器)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆