在Window2003上执行System.Diagnostics.Process.GetProcessesByName等方法失败的原因

最新推荐文章于 2024-02-09 23:05:19 发布

原创最新推荐文章于 2024-02-09 23:05:19 发布 · 4k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#performance #exception #class #windows #system #server

.net相关技术专栏收录该内容

22 篇文章

订阅专栏

从机器上所有进程获取性能数据成本高，操作系统可能加载大量DLL且耗时，获取性能计数器索引时软驱灯会亮。若性能计数器数据损坏，Process类转换信息时可能抛异常，无进程性能计数器的机器无法用该类获取信息，不过Visual Studio 2005已改进。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

在Windows2003上执行 System.Diagnostics.Process.GetProcessesByName等方法会报出Exception:
Couldn't get process information from remote machine.

这个错误的原因是: 获取Process与Performance Counter相关，当前的执行用户不是Administrator 组成员
MSDN的解释：1.Performance information is not available to a non-admin account, which is not in the Performance Counter Users Group on Windows Server 2003. So the Process class could not get process performance information in this case.

2.Getting performance data from all the processes on the machine is pretty expensive. The operating system (OS) might load lots of DLLs and it might take seconds to complete. The floppy drive light will be on when the OS tries to find the index for some performance counter.
3.f the performance counter data was corrupted for any reason, the Process class could throw an exception while trying to convert some raw performance information into DateTime.

4.The Process class could not be used to get process information on machines without the process performance counter. Performance counters can be disabled in Windows. See the following link for details: http://www.microsoft.com/windows2000/techinfo/reskit/en-us/default.asp?url=/windows2000/techinfo/ reskit/en-us/regentry/94214.asp

The good news is that we have changed the implementation of the Process class in Visual Studio 2005 (our next release, code-named Whidbey). The Process class doesn't have a dependency on performance counter information any more (this is only true for local processes).

相关链接：
http://msdn.microsoft.com/netframework/programming/bcl/faq/SystemDiagnosticsProcessFAQ.aspx