Error 1083 in event viewer : need advice

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Romain Pelissier (romain_26_at_hotmail.com)
Date: 05/26/04

  • Next message: Yor Suiris: "Re: Fed up with this problem"
    Date: Wed, 26 May 2004 16:51:46 -0400
    
    

    Hi,
    I hope someone can help with this and I am pretty sure that this kind of
    error happen to someone else.
    Here is the story :
    I have 4 servers : let call them srv1,srv2,srv3,srv4.
    srv1 is the master, the domain controller and the master of my windows 2000
    universe, it also has sms 2003 SP1 beta (need the beta because I need to
    have the default web site other than on port 80 because of epolicy
    orchestrator), and epolicy orchestrator
    srv2 is our mail server with exchange 2003 and groupshield 5.5, domain
    member
    srv3 is a file server, domain member
    srv4 is a remote server in another office, domain member.

    I have the 1083 error in the event viewer, meaning that an item could not be
    updated from a replication partner (between srv1 and srv2). Strange thing is
    that the item is the administrator account :
    Replication warning: The directory is busy. It couldn't update object
    CN=Administrator,CN=Users,DC=sqliaison,DC=com with changes made by directory
    bbd69e83-8165-4d47-b18e-8b5609c584af._msdcs.sqliaison.com. Will try again
    later.

    I have check several troubleshooting ways like :
    > place the account in another OU
    > verifying using LDP if there is no duplicate objects

    But nothing is relevant here, meaning that there is no replication errors
    when trying to use the active directory replication monitor and the kcc
    check is ok too.
    So I try to find why and use the command line utility :
    repadmin /showmeta "cn=administrator,cn=users,dc=mydomain,dc=com' srv1
    and try it also on :
    repadmin /showmeta "cn=administrator,cn=users,dc=mydomain,dc=com' srv2

    I find one difference :
    All versions are the same for the object, exept :
    for srv1 :
    Loc.USN Originating DSA Org.USN
    Org.Time/Date Ver Attribute
    1279952 Default-First-Site-Name\srv1 1279952
    2004-05-19 18:11.55 5 cn
    for srv2
    Loc.USN Originating DSA Org.USN
    Org.Time/Date Ver Attribute
    8822 Default-First-Site-Name\srv2 8822
    2004-02-02 18:16.57 1 cn

    So, the version is not the same for the 2 servers... Another strange thing
    is that if I make a change using AD users and computers to the administrator
    account (like the tel number) the srv1 has the change too !

    If anyone can tell me how I can resolve that ...
    I don't know if I have to modify manually the version number or what I need
    to check to know why or what make the difference of the version between the
    two servers...

    Any help will be VERY appreciated !
    please send a reply no romainp_nospam@sqliaison.com (remove _nospam)


  • Next message: Yor Suiris: "Re: Fed up with this problem"

    Relevant Pages

    • Re: Upgrading 32-bit AD to 64-bit - FSMO problem
      ... Ethernet adapter PUBLIC: ... regarding EX-DC3 replication look interesting...anyway, ... Performing downstream analysis. ... These servers can't get changes from home server EX-DC1: ...
      (microsoft.public.windows.server.active_directory)
    • Re: Upgrading 32-bit AD to 64-bit - FSMO problem
      ... regarding EX-DC3 replication look interesting...anyway, ... Performing downstream analysis. ... These servers can't get changes from home server EX-DC1: ...
      (microsoft.public.windows.server.active_directory)
    • Re: Upgrading 32-bit AD to 64-bit - FSMO problem
      ... DC's should NOT be multihomed, this creates lot's of problems, especially with replication. ... Performing downstream analysis. ... These servers can't get changes from home server EX-DC1: ...
      (microsoft.public.windows.server.active_directory)
    • RE: Global Katalog defekt
      ... also im Active Directory ist der Haken bei GC gesetzt. ... Identifying all servers. ... Active Directory LDAP Services Check ... The replication generated an error: ...
      (microsoft.public.de.german.win2000.active_directory)
    • Re: How to stop two servers in different sites trying to replicate with each other
      ... communicate directly with Site C and vice versa. ... ADSS the DC in Site B keeps setting up one of its replication partners to ... ISTG for intersites connections using BH) ... the ISTG won't use the BH servers between Site C and SiteB to ...
      (microsoft.public.win2000.active_directory)