Re: NTDS Replication Event ID 1083/1955 and account lockouts
- From: Vic <Vic@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 13 May 2009 17:52:02 -0700
Here's a copy of the events
Event 1083
Active Directory could not update the following object with changes received
from the domain controller at the following network address because Active
Directory was busy processing information.
Object:
CN=Victor Gabriel - Adm,OU=Op Accts,OU=Admins,OU=Sydney,DC=avant,DC=local
Network address:
82713579-4787-439a-9a8f-185fd1e97325._msdcs.avant.local
This operation will be tried again later.
Event 1955
Active Directory encountered a write conflict when applying replicated
changes to the following object.
Object:
CN=Victor Gabriel - Adm,OU=Op Accts,OU=Admins,OU=Sydney,DC=avant,DC=local
Time in seconds:
0
Event log entries preceding this entry will indicate whether or not the
update was accepted.
A write conflict can be caused by simultaneous changes to the same object or
simultaneous changes to other objects that have attributes referencing this
object. This commonly occurs when the object represents a large group with
many members, and the functional level of the forest is set to Windows 2000.
This conflict triggered additional retries of the update. If the system
appears slow, it could be because replication of these changes is occurring.
User Action
Use smaller groups for this operation or raise the functional level to
Windows Server 2003.
For more information, see Help and Support Center at
"Marcin" wrote:
Vic,.
have you tried any of the tools/methods described in the
http://technet.microsoft.com/en-us/library/cc738772.aspx and
http://technet.microsoft.com/en-us/library/cc776964.aspx?
hth
Marcin
"Vic" <Vic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8CBC9020-5341-4862-B76A-6A305B763741@xxxxxxxxxxxxxxxx
Hi,
We have had problems for some time with user accounts being locked for
reasons other than users typing in their passwords incorrectly. The issue
does not descriminate and happens at random to all users reagrdless of
privilidges and roles, even when the user is logged in and working away.
The event log of our PDC does show Event 1083 and 1955 for a a user
account
that is locked.
Not sure if the event is ocurring after the account has been locked or the
event occurs and then the account is locked.
Is this event generated because the account is locked ?
We run a 2003 Environment, where the PDC was upgraded from a Win2000 box.
We
also run Citirx for all users apps.
We have a single domain, which was created by the merging of two older
domains.
The PDC server also tuns DHCP.
Checks I have performed already include :
- the are no duplicate objects
- The domain functional level is Win 2003
- repadmin shows success
- dcdiag passes all tests
We have several doamin controllers in other locations serviced by WAN
Links
serviced by 2-4 Mbps links.
Any help appreciated. Thanks
- References:
- Prev by Date: Re: NTDS Replication Event ID 1083/1955 and account lockouts
- Next by Date: Re: NTDS Replication Event ID 1083/1955 and account lockouts
- Previous by thread: Re: NTDS Replication Event ID 1083/1955 and account lockouts
- Next by thread: Re: NTDS Replication Event ID 1083/1955 and account lockouts
- Index(es):
Relevant Pages
|
