Question

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Anyone have any info on this error.

Event Type: Warning
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1083
Date: 12/8/2004
Time: 11:01:41 PM
User: Everyone
Computer: EXCHANGE2
Description:
Replication warning: The directory is busy. It couldn't update object
CN=Tony Schlak,CN=Users,DC=optics,DC=arizona,DC=edu with changes made by
directory d502f905-094f-4bd4-afc7-4e6ef27a4027._msdcs.optics.arizona.edu.
Will try again later.


Thanks,
Tony

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Chances are it is a face value message-the directory was too busy to
immediately update that object.

If you see this often with a particular domain controller, it would be good
to begin some performance testing on it.

If it happens with particular objects, or always from as it accepts changes
from a particular domain controller replica partner, you would want to take
a close look at the object(s) and that domain controller.

The originating DC can be identified by checking DNS for what resolves to
the alias of d502f905-094f-4bd4-afc7-4e6ef27a4027._msdcs.optics.arizona.edu.

--

Tim Springston
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
"Tony Schlak" <tony@optics.arizona.edu> wrote in message
news:OVVVDCh3EHA.2312@TK2MSFTNGP15.phx.gbl...
> Anyone have any info on this error.
>
> Event Type: Warning
> Event Source: NTDS Replication
> Event Category: Replication
> Event ID: 1083
> Date: 12/8/2004
> Time: 11:01:41 PM
> User: Everyone
> Computer: EXCHANGE2
> Description:
> Replication warning: The directory is busy. It couldn't update object
> CN=Tony Schlak,CN=Users,DC=optics,DC=arizona,DC=edu with changes made by
> directory d502f905-094f-4bd4-afc7-4e6ef27a4027._msdcs.optics.arizona.edu.
> Will try again later.
>
>
> Thanks,
> Tony
>

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

It resolves back to itself.


"Tim Springston [MSFT]" <tspring@online.microsoft.com> wrote in message
news:eBuyK%23i3EHA.1404@TK2MSFTNGP11.phx.gbl...
> Chances are it is a face value message-the directory was too busy to
> immediately update that object.
>
> If you see this often with a particular domain controller, it would be
> good to begin some performance testing on it.
>
> If it happens with particular objects, or always from as it accepts
> changes from a particular domain controller replica partner, you would
> want to take a close look at the object(s) and that domain controller.
>
> The originating DC can be identified by checking DNS for what resolves to
> the alias of
> d502f905-094f-4bd4-afc7-4e6ef27a4027._msdcs.optics.arizona.edu.
>
> --
>
> Tim Springston
> Microsoft Corporation
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Tony Schlak" <tony@optics.arizona.edu> wrote in message
> news:OVVVDCh3EHA.2312@TK2MSFTNGP15.phx.gbl...
>> Anyone have any info on this error.
>>
>> Event Type: Warning
>> Event Source: NTDS Replication
>> Event Category: Replication
>> Event ID: 1083
>> Date: 12/8/2004
>> Time: 11:01:41 PM
>> User: Everyone
>> Computer: EXCHANGE2
>> Description:
>> Replication warning: The directory is busy. It couldn't update object
>> CN=Tony Schlak,CN=Users,DC=optics,DC=arizona,DC=edu with changes made by
>> directory d502f905-094f-4bd4-afc7-4e6ef27a4027._msdcs.optics.arizona.edu.
>> Will try again later.
>>
>>
>> Thanks,
>> Tony
>>
>
>