IIS APPPOOL\ASP.NET v4.0 Classic user not able to access HKLM\...\CurrentVersion\Perflib registry key on some Windows 2008 R2 systems


i looking using process monitor , came across these:


9:18:50.7032220 am 0.0000217 w3wp.exe regopenkey hklm\software\microsoft\windows nt\currentversion\perflib access denied desired access: read/write c:\windows\system32\inetsrv\w3wp.exe -ap "asp.net v4.0 classic" -v "v4.0" -l "webengine4.dll" -a \\.\pipe\iisipmfe2ae280-15c9-4c86-a961-4f6243eb44e0 -h "c:\inetpub\temp\apppools\asp.net v4.0 classic\asp.net v4.0 classic.config" -w "" -m 1

9:18:50.7032740 am 0.0000099 w3wp.exe regopenkey hklm\software\microsoft\windows nt\currentversion\perflib access denied desired access: read c:\windows\system32\inetsrv\w3wp.exe -ap "asp.net v4.0 classic" -v "v4.0" -l "webengine4.dll" -a \\.\pipe\iisipmfe2ae280-15c9-4c86-a961-4f6243eb44e0 -h "c:\inetpub\temp\apppools\asp.net v4.0 classic\asp.net v4.0 classic.config" -w "" -m 1

from server:

5:30:57.1296327 am 0.0000075 w3wp.exe regopenkey hklm\software\microsoft\windows nt\currentversion\perflib success desired access: read c:\windows\system32\inetsrv\w3wp.exe -ap "asp.net v4.0 classic" -v "v4.0" -l "webengine4.dll" -a \\.\pipe\iisipm3b4fae66-504e-4a35-80da-1938d7d3125f -h "c:\inetpub\temp\apppools\asp.net v4.0 classic\asp.net v4.0 classic.config" -w "" -m 1

the user account "iis apppool\asp.net v4.0 classic". same keys on other servers can access account. trust setting in web.config , other permissions same on servers.

the registry key perflib has read permission interactive, network service, local service, performance log user & performance monitor user accounts. administrators , system account has full control.

how find out why access denied?

thanks


asp.net moderator advised me post question on iis.net forum.

same question on iis.net forum



Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file