1. Try following the steps mentioned in http://questsupportlink.quest.com/eSupport/Solution.asp?WAid=268450948&itemID=9830
2. If the issue still exists after applying solution #9830, then try the following Microsoft KB article even if MessageStats is not installed on a DC. It has resolved this issue in the past for W2K/W2K3 Servers.
BUG: IWAM Account Is Not Granted the Impersonate Privilege for ASP.NET 1.1 on a Windows 2000 Domain Controller with SP4
Article ID : 824308
Last Review : August 13, 2003
Revision : 2.0
3. If the issue is still not resolved then try the following: By default, ASP.NET functionality is enabled for IIS virtual servers after the .NET Framework is installed. However, if ASP.NET is disabled, please re-enable it. Or, enable ASP.NET for a virtual folder on a virtual server that has ASP.NET disabled. To enable ASP.NET functionality, follow these steps:
1. On the task bar click start. Point to Settings and then click Control Panel.
2. Double-click to open the Administrative Tools folder and then double-click Internet Services Manager.
3. Right-click the virtual server or the virtual folder and then select Properties.
4. Select the Home Directory tab or the Directory tab.
5. If an application has not been created for the virtual folder, click Create under Application Settings.
6. Under Application Settings, click Configuration.
7. Click Add to add an application extension mapping.
By default, ASP.NET associates 18 extension mappings with the %SystemRoot%\Microsoft.NET\Framework\%VersionNumber%\Aspnet_isapi.dll file. These extensions are: .ASAX, .ASCX, .ASHX, .ASMX, .ASPX, .AXD, .VSDISCO, .REM, .SOAP, .CONFIG, .CS, .CSPROJ, .VB, .VBPROJ, .WEBINFO, .LICX, .RESX, and .RESOURCES.
8. For each extension mapping, click Browse and then select the Aspnet_isapi.dll file. Type the extension in the
9. In the Verbs dialog box, click Limit To and then type GET, HEAD, POST, DEBUG in the Limit To text box. Click
10 Click OK until you return to Internet Services Manager and then close Internet Services Manager.
4. If it still does not work, try uninstalling and then reinstall Messagestats. If a custom install of Messagestats is used, only the Reports component needs to be uninstalled
No settings would be lost and if the database is local, just remember that dialog box will appear asking to keep current data or clear database so please click on keep current data.
You would need to follow these steps to uninstall Messagestats from your console:
1. Start -->Settings -->Control Panel -->Add remove programs
2. Select Quest Messagestats from the program list and click remove
3. Verify that you want to remove Quest Messagestats
4. Repeat steps 1 through 3 on the remaining computers
5. If the error is still not resolved, the try this link http://support.microsoft.com/default.aspx?scid=kb;en-us;317012
6. If the error is still not resolved, the try to check permission problems running on a domain controller, or an unexpected interaction with Net Tracker 7.0 Professional (web monitoring). If the IIS server is a domain controller, then it would indicate permission problems with the ASP.NET service accounts (an IIS configuration issue). If it is at all possible, it would a good idea to try disabling Net Tracker 7.0 temporarily to see if that makes a difference
7. If the error is still not resolved, try the following steps:
a. Logon to the server with local admin rights
b. Uninstall Quest messagestats
c. Remove all Software related to .NET framework
d. Restart the server
e. Login again, reinstall .NET framework
f. Restart again
g. Installed Quest Messagestats again