We are getting this evenID 1202 warning on the windows logs every five minutes. I have checked many forums to try to get rid of this warning, but without success. some of the things I have done - Cannot find WdiServiceHost http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/7bfe1f02-bb8b-472f-9c27-90d3481f2c53 Cannot find Classic .NET AppPool http://forums.iis.net/t/1174840.aspx http://community.spiceworks.com/topic/100953 Hotfix http://support.microsoft.com/kb/977695 what else can i do to so that the warning will not appear again on the windows log?

its running on windows 2008 R2 standard 64 bits. i have IIS running on the server.

Hi, Please let us know the error code in the event, such as 0x534, 0x6fc, 0x2. You can paste the whole event here for research. First, please go through the following support article: Troubleshooting SCECLI 1202 Events http://support.microsoft.com/kb/324383 Although the article is for Windows 2000 Server, most steps are similar in Windows Server 2008. To determine the account that is causing the failure. We can enable debug logging for the Security Configuration client-side extension. Refer to: a. Start Registry Editor. b. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions\{827D319E-6EAC-11D2-A4EA-00C04F7 9F83A} c. Set the following registry value: Value name: ExtensionDebugLevel Data type: DWORD Value data: 2 d. Quit Registry Editor. 2. Refresh the policy settings to reproduce the failure. Type the following at the command prompt, and then press ENTER: Gpupdate /force This creates a file that is named Winlogon.log in the %SYSTEMROOT%\Security\Logs folder. 3. Find the problem account. To do this, type the following at the command prompt, and then press ENTER: find /i "cannot find" %SYSTEMROOT%\security\logs\winlogon.log The Find output identifies the problem account names. Then, determine why this account cannot be resolved. For example, look for typographical errors, a deleted account, the wrong policy applying to this computer, or a trust problem. You can also paste the output here for research. If anything is unclear, please let us know. Thanks. NinaPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.