This issue occurs 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.To resolve it, please use the method at:
To work around the problem, manually assign Impersonate a client after authentication to the IWAM account. To do so, follow these steps:
- Click Start, point to Programs, point to Administrative Tools, and then click Domain Controller Security Policy.
- Click Security Settings.
- Click Local Policies, and then click User Rights Assignment.
- In the right pane, double-click Impersonate a client after authentication.
- In the Security Policy Setting window, click Define these policy settings.
- Click Add, and then click Browse.
- In the Select Users or Groups window, select the IWAM account name, click Add, and then click OK.
- Click OK, and then click OK again.
- To enforce an update of computer policy, type the following command:
secedit /refreshpolicy machine_policy /enforce
- At a command prompt, type iisreset.In case your server is a Domain Controller
Refer PRB: ‘Catastrophic Failure’ Error Message When You Try to Debug an ASP.NET Application on Windows 2000 Domain Controller