RE: "Requested registry access is not allowed." and performance co
- From: Peter Ritchie <PRSoCo@xxxxxxxxxxxxxxxxx>
- Date: Fri, 23 Jun 2006 08:39:01 -0700
Hi Luke.
I switched the aspnet_wp.exe user from ASPNET to administrator and re-tried
the code. There were no exceptions (i.e. no Win32Exception with message ==
"invalid handle").
There were also no ACCESS DENIED reported by regmon or filemon with the
aspnet_wp.exe user being ASPNET or administrator.
There are a few BUFFER OVERFLOW results from some of the performance counter
registry entries though, with either user.
--
http://www.peterRitchie.com/
"Peter Ritchie" wrote:
Hi Steven. Thanks for the reply. Had a server-down situation, so it took me.
a couple of days to get back to this...
After some inspection with RegMon it would appear that the ASPNET account
also needs full control over HKLM\System\CurrentControlSet\Services. I tried
several advanced permissions options, like "this key only" and "Set Value"
and "Create Subkey"; but could only get it to work if I can the ASPNET
account full control over HKLM\System\CurrentControlSet\Services--which
doesn't give me a warm-and-fuzzy.
Doing that gets rid of the "Requested registry access is not allowed"
exception text. The process gets further, by creating the
Performance-counter--related sub-keys in
HKLM\System\CurrentControlSet\Services; but,
PerformanceCounterCategory.Create now raises a Win32Exception with Message
property equal to "The handle is invalid" or ErrorCode == 0x80004005.
--
http://www.peterRitchie.com/
"Steven Cheng[MSFT]" wrote:
Hi Peter,
Thank you for posting here.
From your description, you're dynamically creating
PerformanceCounter/Category in your ASP.NET webservice's code, however,
you're euncountering smoe security exception against the registry accessing
at runtime, correct?
Based on my experience, there does exists some issues regarding on the
ASP.NET idenitity doesn't have sufficient permission for accessing certain
registry entry. For your scenario, your ASP.NET application is running on
XP box, by default the ASP.NET process idenitity is the machine\ASPNET
account, however, I'm wondering whether you've used any other security
related setting in IIS or ASP.NET such as impersonation which could change
the default process idenitity of ASP.NET. You can verify this in your web
application, and here is a kb article introduce the ASP.NET process
identity:
#Process and request identity in ASP.NET
http://support.microsoft.com/?id=317012
Also, since the security exception is still complaining about the registry,
I suggest you use the regmon tool to trace the registry accessing failure,
this tool is very good at capturing reigstry access problem:
http://www.sysinternals.com/utilities/regmon.html
BTW, to help make the troubleshooting simplifed, I suggest you keep your
ASP.NET application running as "Fulltrust" mode(this is the default mode if
you haven't explicitly change the Trust level in your machine.config or
web.config).
Hope this helps.
Regards,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights
- Follow-Ups:
- RE: "Requested registry access is not allowed." and performance co
- From: Luke Zhang [MSFT]
- RE: "Requested registry access is not allowed." and performance co
- References:
- RE: "Requested registry access is not allowed." and performance counte
- From: Steven Cheng[MSFT]
- RE: "Requested registry access is not allowed." and performance co
- From: Peter Ritchie
- RE: "Requested registry access is not allowed." and performance counte
- Prev by Date: RE: .NET based SOAP proxy and HTTP Basic Authentication
- Next by Date: Re: web service method calls over http get protocol
- Previous by thread: RE: "Requested registry access is not allowed." and performance co
- Next by thread: RE: "Requested registry access is not allowed." and performance co
- Index(es):
Relevant Pages
|