Ask a Question related to ASP.NET Security, Design and Development.
-
HBrothers #1
Using ASPNET_SETREG.exe
Can this utility be used for an impersonated user in Web.Config?
I've used it to create the appropriate userName and password keys in the
registry and put the settings in Web.Config like this:
<identity impersonate="true"
userName="registry:HKLM\SOFTWARE\...\ASPNET_SETREG ,userName"
password="registry:HKLM\SOFTWARE\...\ASPNET_SETREG ,password"
/>
However, I keep getting errors saying that the password or userName could
not be read from the registry. I've made sure that the ASPNET account on
the server (Win 2003) has permissions to read the specific key. Is there
anything else I need to do?
Thanks,
-- Hardin
HBrothers Guest
-
ASPNET_SETREG and Framework 1.1
My colleage and I determined that generic error message that is given as a response to *anything* being slightly out of place, when using the... -
Using aspnet_setreg
Hello, I am converting a asp.net web app from using connection string safety in the web.config to using encrypted values using astnet_setreg. I... -
ASPNET_SETREG runs on XP, not 2000
I have a webservice up and running locally on my dev machine (XP) using impersonate like so: Line 5: <identity impersonate="true" Line 6:... -
aspnet_setreg fails
Getting a consistent failure on machines when attempting to run the aspnet_setreg utility. The command line has worked on one or two machines. ... -
Has _ANYONE_ ever got the aspnet_setreg utility to work for them?
Dear Jason, I found the resolution to my problem with a hotfix from MS it is listed as Q329250 and you must requested from the support. You have... -
Keith #2
Using ASPNET_SETREG.exe
Did you follow this step:
Grant Read permissions to the Aspnet_wp.exe process
account.
See [url]http://support.microsoft.com/default.aspx?scid=kb;EN-[/url]
US;329290 for more info.
Web.Config?>-----Original Message-----
>Can this utility be used for an impersonated user inpassword keys in the>I've used it to create the appropriate userName anduserName="registry:HKLM\SOFTWARE\...\ASPNET_SETREG ,userNam>registry and put the settings in Web.Config like this:
> <identity impersonate="true"
>
e"password="registry:HKLM\SOFTWARE\...\ASPNET_SETREG ,passwor>
d"or userName could> />
>However, I keep getting errors saying that the passwordASPNET account on>not be read from the registry. I've made sure that thespecific key. Is there>the server (Win 2003) has permissions to read the>anything else I need to do?
>
> Thanks,
> -- Hardin
>
>
>.
>Keith Guest
-
Marko #3
RE: Using ASPNET_SETREG.exe
Hi!
I have exactly the same problem and I followed those steps Keith mentioned. Problem still exists on my 2003 server but it works with my XP/IIS5.1 !
Is there some fix for this problem that I have with my development environment or maybe some differences with security policys?
Marko Guest
-
Marko #4
RE: Using ASPNET_SETREG.exe
Hi
I have exactly the same problem with my Win2003 server - but wtih XP/IIS5.1 it works!
I have tried to find the difference but haven't figure it out yet.
Does my development environment (framework SDK) have something that my test Win2003 server doesn't? Or..
Is there some fix for Win2003 to resolve this problem? Or..
Can the local security policy be the reason for this
--Marko-
ps It was really hard to get this thru...
Marko Guest
-
Holly Mazerolle #5
RE: Using ASPNET_SETREG.exe
On your Windows 2003 machine keep make sure that you have granted the
permissions needed to the correct account. You will find is you check in
IIS that the process is now running under an account called Network
Service. Also, if this still does not work, you could download regmon from
[url]http://www.sysinternals.com[/url] and reproduce the problem will running that
tool. You can look for any access denieds and it will also show you which
account is attempting to make an access.
This posting is provided "AS IS" with no warranties, and confers no rights.
Hope this Helps
Holly
Holly Mazerolle Guest
-
Marko #6
RE: Using ASPNET_SETREG.exe
Thanks Holly
Granting read permissions to those registry keys (for Network Service account) solved the problem
--Marko--
Marko Guest



Reply With Quote

