Re: Debugger not working in Vs.net 2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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

  • Cannot change "Impersonate a client after authentication" settings
    ... I need to add some accounts to "Impersonate ... a client after authentication" Local security policy. ...
    (microsoft.public.windows.server.security)
  • Re: Accessing Local Security Policy Programatically
    ... example the User Rights. ... I am NOT finding a way to access Local Security Policy settings ... The Local Security Policy setting which I'm trying to access is: ...
    (microsoft.public.windows.server.security)
  • Re: 401.1 & MOSS
    ... Enable "logon" failure auditing in the local security policy, then look in the Windows Security event log to get an idea of why authentication is failing. ... When external users try to access the site, ... I changed the anonymous login ID to the local admin and password-no good. ...
    (microsoft.public.inetserver.iis.security)
  • RE: Local security policy Settings
    ... this happens when a trust have disappeared, is corrupted or when group or user have been deleted in an another container with which the box have an implicit trust. ... Under the local security Policy settings I was seeting up a user and I found these ...
    (Focus-Microsoft)
  • Accessing Local Security Policy Programatically
    ... I am NOT finding a way to access Local Security Policy settings ... The Local Security Policy setting which I'm trying to access is: ... Does anybody have an idea about accessing this settting ...
    (microsoft.public.windows.server.security)