Event ID 1202 - Error code 0x6fc

[doug.masters@gmail.com]

Getting this error about every 12 hours, only on one DC. I have
followed the directions in KB324383 and found the two accounts that it
is unhappy about. Yesterday I found that one of the accounts was in
the Login Locally section of the Default Domain Controller Policy and
removed it. I didn't find the other one anywhere.

This morning I still get the error and issuing the FIND command on the
winlogon.log reports the same two accounts as yesterday, however when
I run the FIND on the GPT*.* files , those two users names are NOT
found in either policy.

 

[Robert L [MVP - Networking]]

Have you tried this one:
Troubleshooting SceCli Event ID 1202
The presence of SceCli event ID 1202 in the application event log indicates that there might be problems with Active Directory replication, especially if the error text for this message contains a Win32 error code of either Error 1332 (0x534) or Error 1332 (0x6fc). The procedure for troubleshooting this event with either hexadecimal code is the same.

Active Directory Operations Overview: Troubleshooting Active ...SceCli event ID 1202. A user account in one or more Group Policy objects (GPOs) ...... The presence of SceCli event ID 1202 in the application event log ....
www.microsoft.com/.../windows2000se...irectory/maintain/opsguide/part1/adogd12.mspx



Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<doug.masters@gmail.com> wrote in message news:1185891023.540690.21170@w3g2000hsg.googlegroups.com...
Getting this error about every 12 hours, only on one DC. I have
followed the directions in KB324383 and found the two accounts that it
is unhappy about. Yesterday I found that one of the accounts was in
the Login Locally section of the Default Domain Controller Policy and
removed it. I didn't find the other one anywhere.

This morning I still get the error and issuing the FIND command on the
winlogon.log reports the same two accounts as yesterday, however when
I run the FIND on the GPT*.* files , those two users names are NOT
found in either policy.

 

[doug.masters@gmail.com]

Yes, Robert, that's the KB article I referenced in my original email.

Step Three offers the two accounts it cannot find. However, neither
of those accounts return any results in Step Four.


On Jul 31, 9:46 am, "Robert L [MVP - Networking]"
<nore...@hotmail.com> wrote:
> Have you tried this one:
> Troubleshooting SceCli Event ID 1202
> The presence of SceCli event ID 1202 in the application event log indicates that there might be problems with Active Directory replication, especially if the error text for this message contains a Win32 error code of either Error 1332 (0x534) or Error 1332 (0x6fc). The procedure for troubleshooting this event with either hexadecimal code is the same.
>
> Active Directory Operations Overview: Troubleshooting Active ...SceCli event ID 1202. A user account in one or more Group Policy objects (GPOs) ..... The presence of SceCli event ID 1202 in the application event log ...
> www.microsoft.com/.../windows2000serv/technologies/activedirectory/ma...
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting onhttp://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access onhttp://www.HowToNetworking.com <doug.mast...@gmail.com> wrote in messagenews:1185891023.540690.21170@w3g2000hsg.googlegroups.com...
>
> Getting this error about every 12 hours, only on one DC. I have
> followed the directions in KB324383 and found the two accounts that it
> is unhappy about. Yesterday I found that one of the accounts was in
> the Login Locally section of the Default Domain Controller Policy and
> removed it. I didn't find the other one anywhere.
>
> This morning I still get the error and issuing the FIND command on the
> winlogon.log reports the same two accounts as yesterday, however when
> I run the FIND on the GPT*.* files , those two users names are NOT
> found in either policy.