Re: Debugger not working in Vs.net 2003

Hi Gary,

I check The "Impersonate a client after authentication" user right, aspnet
already there, I try to add again, then run the web project, still got
"Unable to run debugging on the web ..." msg. Also I change user name from
machine to system, same msg popup. Thanks.


Jason

"Gary Chang[MSFT]" <v-garych@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:jsfnP0WRFHA.1560@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Jason,
>
> >I tried Leo's method, It's not working for my case. I have been
> >checked the installation list from the "Add or Remove Programs"
> >of Control Panel, It's a long list but no time stamp associate with.
>
> On this situation, I suggest you perform the following steps to trouble
> shoot the problem:
>
> Firstly, you can run the following command at a command prompt.
>
> C:\WINNT\Microsoft.NET\Framewo-rk\v1.0.3705\aspnet_regiis.exe -i
>
> Then, restart IIS by running the iisreset command. For details, you could
> refer to
> http://support.microsoft.com/?-id=306005.
>
> Since your machine is Windows 2000 SP4, the problem would occur if the
> account that is used to run the ASP.NET Worker process (by default, the
> ASPNET user account) is not assigned the "Impersonate a client after
> authentication" user right in the Local Security Policy settings. This
> issue may occur when you install Microsoft Visual Studio .NET after you
> install Windows 2000 Service Pack 4 (SP4) on the computer. In this
> situation, the ASPNET account is not assigned the "Impersonate a client
> after authentication" user right in the Local Security Policy settings.
>
> The "Impersonate a client after authentication" user right (also named
> SeImpersonatePrivilege) is a new Windows 2000
> security setting that was first included in Windows 2000 SP4.
>
> To work around this issue, please assign the "Impersonate a client after
> authentication" user right to the ASPNET account in the Local Security
> Policy settings:
> 1. Click Start, point to Programs, point to Administrative Tools, and
> then click Local Security Policy.
> 2. Double-click Local Policies, and then click User Rights
Assignment.
> 3. In the right pane, double-click Impersonate a client after
> authentication.
> 4. In the Local Security Policy Setting dialog box, click Add.
> 5. In the Select Users or Group dialog box, click ASPNET, click Add,
> and then click OK.
> 6. Click OK.
>
> If the above suggestions don't help, please try the following.
>
> 1. Open
> C:\WINDOWS\Microsoft.NET\Frame-work\v1.0.3705\CONFIG\machine.-config in
> Notepad.
> 2. Locate the processModel section. It looks like:
> <processModel
> ......
> userName="machine"
> password="AutoGenerate"
> ......
> />
> 3. Change the userName from "machine" to "system". This section will
> look like:
> <processModel
> ......
> userName="system"
> password="AutoGenerate"
> ......
> />
> 4. Save the file.
> 5. Run the command "iisreset".
>
>
> These trouble shooting steps will help us get closer to resolving your
> issue, so I appreciate your time in performing them. Let me know the
> results at your earliest convenience. If you have any questions or
> concerns, please let me know. I am standing by to help you.
>
> Thanks!
>
> Best regards,
>
> Gary Chang
> Microsoft Community Support
> --------------------
> Get Secure! ¡§C www.microsoft.com/security
> Register to Access MSDN Managed Newsgroups!
>
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
> &SD=msdn
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>


.

Relevant Pages

  • Re: Installshield wizard was Interrupted on XP Home Edition
    ... Grants/Revokes NT-Rights to a user/group ... change the 'Impersonate a client after authentication' setting and thus can ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Problem running ASP.NET 2.0 on Win2K domain controller
    ... Domain Controllers policy and added system to the Impersonate a Client ... After Authentication right and rebooted the box. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: THIS FIXES 0x800a0046
    ... Are you trying to access the client remotely, and then connect it to Windows Update? ... ""Impersonate a client after authentication"" security policy. ... Choose Local Security Policy ...
    (microsoft.public.windowsupdate)
  • Re: Network Connections not displayed
    ... This is caused by the "Group Policy" setting "Impersonate a client ... "Impersonate a client after authentication" set wrong. ...
    (microsoft.public.windows.server.networking)
  • Re: <identity impersonate="true"> question
    ... The default setup used to be to run the ASPNET worker ... Does your app actually need to create categories? ... Windows authentication, and impersonate the authenticating user? ...
    (microsoft.public.dotnet.framework.aspnet.security)