Link to home
Start Free TrialLog in
Avatar of NewbieITGal
NewbieITGalFlag for Afghanistan

asked on

Event Id 1202 SceCli

Hi Everyone,

I have a Windows Server 2008 environment with two domain controllers.  Every 5 minutes
in Event Viewer I am getting an Event id 1202 SceCli.  I followed the steps below to find the account. The results came back with ......Cannot Find DefaultAppPool     Has anyone else had this problem on Win 2008 if so how did you resolve he problem?

Thanks for any help.

Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done.

Advanced help for this problem is available on http://support.microsoft.com. Query for "troubleshooting 1202 events".

Error 0x534 occurs when a user account in one or more Group Policy objects (GPOs) could not be resolved to a SID.  This error is possibly caused by a mistyped or deleted user account referenced in either the User Rights or Restricted Groups branch of a GPO.  To resolve this event, contact an administrator in the domain to perform the following actions:

1. Identify accounts that could not be resolved to a SID:

From the command prompt, type: FIND /I "Cannot find"  %SYSTEMROOT%\Security\Logs\winlogon.log

The string following "Cannot find" in the FIND output identifies the problem account names.

Example: Cannot find JohnDough.

In this case, the SID for username "JohnDough" could not be determined. This most likely occurs because the account was deleted, renamed, or is spelled differently (e.g. "JohnDoe").

2. Use RSoP to identify the specific User Rights, Restricted Groups, and Source GPOs that contain the problem accounts:

a. Start -> Run -> RSoP.msc
b. Review the results for Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment and Computer Configuration\Windows Settings\Security Settings\Local Policies\Restricted Groups for any errors flagged with a red X.
c. For any User Right or Restricted Group marked with a red X, the corresponding GPO that contains the problem policy setting is listed under the column entitled "Source GPO". Note the specific User Rights, Restricted Groups and containing Source GPOs that are generating errors.

3. Remove unresolved accounts from Group Policy

a. Start -> Run -> MMC.EXE
b. From the File menu select "Add/Remove Snap-in..."
c. From the "Add/Remove Snap-in" dialog box select "Add..."
d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and click "Add"
e. In the "Select Group Policy Object" dialog box click the "Browse" button.
f. On the "Browse for a Group Policy Object" dialog box choose the "All" tab
g. For each source GPO identified in step 2, correct the specific User Rights or Restricted Groups that were flagged with a red X in step 2. These User Rights or Restricted Groups can be corrected by removing or correcting any references to the problem accounts that were identified in step 1.

Avatar of Richard2k4
Richard2k4
Flag of United States of America image

any chance you have a gpo to rename the guest or admin accounts?  if so and you manually did them before the gpo could, you will get scecli events.
Avatar of NewbieITGal

ASKER

Hi Richard d2k4:

No,  that's not the case here.
I got the problem solved.  
Avatar of JeremyThomas
JeremyThomas

I got the problem solved.  

What was your solution? I have the same issue with Cannot Find DefaultAppPool as well as  Cannot find Classic .NET AppPool
ASKER CERTIFIED SOLUTION
Avatar of NewbieITGal
NewbieITGal
Flag of Afghanistan image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Glen Knight
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.

In case anyone else has this problem again:

http://support.microsoft.com/kb/977695

(the above link applies to Win2K8R2, but this has been a problem for a while, and there are other KBs that apply to other versions of Windows)

You can either request and install the hotfix (which the MS website says requires a restart), or you can do it manually as per the info contained in the link. Doing it manually resolved my problems, no restart needed.