Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 952262 - Last Review: April 28, 2008 - Revision: 1.0
Process.ProcessName fails with "access denied"
Source: Microsoft Support
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Obtaining process name using Process.ProcessName fails with the following exception:
InnerException:
Message: Access is denied
Source: System
StackTrace: at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited)
at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId)
at System.Diagnostics.Process.get_Modules()
at System.Diagnostics.Process.get_MainModule()
at System.Diagnostics.Process.get_ProcessName()
at EnumProc.Class1.Main(String[] args)
You are unable to obtain the process name.
The Process Object uses performance counters to enumerate processes and obtain information about the processes like its name. If the process name was 15 characters or greater the process name was truncated. A bug was discovered that when you were seeking a process with a name that contained 15 or more characters, the process wasn’t found because the comparison was made between the full name and the truncated name. To address this issue in the .NET 1.1 Framework, if they found a process name (ProcessName property) that was 15 characters or greater, the class would attempt to find the true process name by obtaining it from the process module information. This requires a process handle where the caller must have PROCESS_QUERY_INFORMATION | PROCESS_VM_READ to the process.
The Process objects assumes the caller has the above permissions to all processes on the system which may not be true.
The following solutions are available:
1. Use the .NET Framework 2.0.
2. Find the process and grant the caller the PROCESS_QUERY_INFORMATION | PROCESS_VM_READ permissions.
3. Rename the process name to 15 characters or less.
4. Terminate the offending process.
5. Ignore the exception if the name is not required.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALSâ€) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
APPLIES TO
- Microsoft .NET Framework 1.1
- Microsoft .NET Framework 1.1 Service Pack 1
| kbnomt kbrapidpub KB952262 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please