RE: NTDS Replication error

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Sorry for not replying for ages. I´ve not heard anything about what the new
service pack brings, in fact I´ve only installed in one computer, an ISA
server.

Do you have a solution to your problem yet?

"Acung" wrote:

I add my users manually because we start with 20 users only at that time.
Did you heard anything about this error in the new service pack?

Cheers,

Acung

"johnny_mango" wrote:

Hi,

I still have the same problem. At the moment I am off-site, and wouldn´t
expect to be back there for the next 3 or 4 weeks, during that time our
client´s staff will be migrating machines, activating more user accounts, so
I would expect to learn a bit more at that time.

I am suprised there haven´t been any replies from any of the AD experts,
considering there are now a few of us experiencing this problem. Perhaps it
is just an "expected" error message and can be ignored, as per netid.net.
However, I had never seen it before in any other deployment.

How did you add your user accounts to AD? Was it also scripted?

"Acung" wrote:

Hi, the problem still exist and I'm ignoring it because didn't know what to
do to resolve the problem and no feed back from the newsgroup during the
times.
Do you have any progress with it?

Regards,

Acung

"Acung" wrote:

Hi, we've 2 DCs (Windows 2003 Standard R2) in our domain. PDC is Primary DNS
Server, Additional DC (hereafter 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&Forest function level is Windows
2003, transitive trust has eshtablished with our parent company.

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

Event Type: Warning
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1083
Date: 1/31/2007
Time: 2:11:50 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=domain,DC=fam
Network address:
f3f9cdd5-fe1b-4c10-ba8e-eee29ee73489._msdcs.domain.fam

This operation will be tried again later.

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

and

Event Type: Information
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1955
Date: 1/31/2007
Time: 2:17:46 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=domain,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.

AD seems working well, no other issue in the server and client's side.
Please advice,

Regards,

Acung

.



Relevant Pages

  • RE: NTDS Replication error
    ... Will update you if have any progress on it. ... Did you heard anything about this error in the new service pack? ... Server, Additional DC is Secondary DNS Server (both:AD ...
    (microsoft.public.windows.server.active_directory)
  • RE: NTDS Replication error
    ... Server, Additional DC is Secondary DNS Server (both:AD ... Active Directory could not update the following object with changes received ... Active Directory encountered a write conflict when applying replicated ...
    (microsoft.public.windows.server.active_directory)
  • RE: NTDS Replication error
    ... Server, Additional DC is Secondary DNS Server (both:AD ... Active Directory could not update the following object with changes received ... Active Directory encountered a write conflict when applying replicated ...
    (microsoft.public.windows.server.active_directory)
  • RE: NTDS Replication error
    ... Server, Additional DC is Secondary DNS Server (both:AD ... Active Directory could not update the following object with changes received ... Active Directory encountered a write conflict when applying replicated ...
    (microsoft.public.windows.server.active_directory)
  • Change Server IP address, implications?
    ... I currently have a Windows 2000 Server running as the PDC providing mainly ... File/Print Services within a relatively simple enviornment. ... Service Pack 2. ... Active Directory is also running which replicates with a another 2000 backup ...
    (microsoft.public.win2000.general)