Re: Directory Service logged NTDS replication (1083 and 1955) events

Hi
Have a look if helps:
http://www.jsifaq.com/SF/Tips/Tip.aspx?id=7926


--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"lzd212" <u34991@uwe> wrote in message news:7394b45d30e0f@xxxxxx
Hi, we've 2 DCs (Windows 2003 Standard R2 SP2) in our domain. PDC is Primary
DNS
Server, ADC is Secondary DNS Server (both:AD
Integrated - replicated to all DNS Server in the AD domain). PDC pointed to
it self for Primary DNS and ADC as Secondary DNS and ADC pointed to itself as

Primary DNS and PDC as Secondary DNS.
Domain and Forest function level is Windows 2003, both DCs are Global Catalog
Server and no child domain/other domain in the forest.

I'm continuously get these error (1083 followed by 1955):

Event Type: Warning
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1083
Date: 6/12/2007
Time: 4:04:48 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: GMSI-DC01
Description:
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=Administrator,CN=Users,DC=globalmediasvc,DC=fam
Network address:
f3f9cdd5-fe1b-4c10-ba8e-eee29ee73489._msdcs.globalmediasvc.fam

This operation will be tried again later.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Information
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1955
Date: 6/12/2007
Time: 4:04:48 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: GMSI-DC01
Description:
Active Directory encountered a write conflict when applying replicated
changes to the following object.

Object:
CN=Administrator,CN=Users,DC=globalmediasvc,DC=fam
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
http://go.microsoft.com/fwlink/events.asp.

Already check it in eventid.net but did not know how to resolved it, please
advice.

Regards,

Acung


.

Relevant Pages

  • NTDS Replication error
    ... Server, Additional DC (hereafter ADC) is Secondary DNS Server (both:AD ... it could be because replication of these changes is occurring. ...
    (microsoft.public.windows.server.active_directory)
  • Re: ADC Connection Agreement replication time
    ... ADC replicated the accounts and that is why you are getting the warnings. ... completed replication by now, and the verify is finding several mailboxes ... install Exchange 2003 on. ... You can run the ADC service on any Windows 2000 or 2003 server, ...
    (microsoft.public.exchange.setup)
  • Re: Taking too long for Connection Agreement to replicate
    ... ADC replicated the accounts and that is why you are getting the warnings. ... completed replication by now, and the verify is finding several mailboxes ... install Exchange 2003 on. ... You can run the ADC service on any Windows 2000 or 2003 server, ...
    (microsoft.public.exchange.setup)
  • Re: ADC 8026 Errors following an Exchange 5.5 to Exchange 2003 migrati
    ... ADC Replication Is Not Successful and an Event 8026 Message Is ... to do with public folder replication of hierarchy or content. ... Successfully moved the mailboxes from the old server to the NEWSERVER ...
    (microsoft.public.exchange2000.setup.installation)
  • Directory Service logged NTDS replication (1083 and 1955) events
    ... Server, ADC is Secondary DNS Server (both:AD ... it could be because replication of these changes is occurring. ...
    (microsoft.public.windows.server.active_directory)