AD 2000 to 2003 R2

Discussion in 'Server Migration' started by ben51, Apr 9, 2009.

  1. ben51

    ben51 Guest

    Hello,

    I have some problem with the adprep /forestprep command on a Windows 2000
    SP4. When I run the command I see the message below. What could I do?

    =============================================================================
    "attributeId" attribute value for objects defined in Windows 2000 schema and
    ext
    ended schema do not match.


    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1
    ..4.7000.187.102" for object
    "CN=uid,CN=Schema,CN=Configuration,DC=ilmh,DC=be" di
    fferently than the schema extension needed for Windows 2003 server .
    [Status/Consequence]
    Adprep cannot extend your existing schema
    [User Action]
    Contact the vendor of the application that previously extended the schema to
    res
    olve the inconsistency. Then run adprep again.




    =============================================================================
    "isSingleValued" attribute value for objects defined in Windows 2000 schema
    and
    extended schema do not match.


    A previous schema extension has defined the attribute value as "TRUE" for
    object
    "CN=uid,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema e
    xtension needed for Windows 2003 server .
    [Status/Consequence]
    Adprep cannot extend your existing schema
    [User Action]
    Contact the vendor of the application that previously extended the schema to
    res
    olve the inconsistency. Then run adprep again.




    =============================================================================
    "attributeSyntax" attribute value for objects defined in Windows 2000 schema
    and
    extended schema do not match.


    A previous schema extension has defined the attribute value as "2.5.5.5" for
    obj
    ect "CN=uid,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schem
    a extension needed for Windows 2003 server .
    [Status/Consequence]
    Adprep cannot extend your existing schema
    [User Action]
    Contact the vendor of the application that previously extended the schema to
    res
    olve the inconsistency. Then run adprep again.
     
    ben51, Apr 9, 2009
    #1
    1. Advertisements

  2. Hello ben51,

    Did you previously try to extend the schema for an application?
     
    Isaac Oben [MCITP,MCSE], Apr 10, 2009
    #2
    1. Advertisements

  3. ben51

    kj [SBS MVP] Guest

    Looks similar to the Services For Unix (SFU) issue.

    http://support.microsoft.com/kb/919938

    Did anyone ever install a version of Services For Unix in your forest?


     
    kj [SBS MVP], Apr 10, 2009
    #3
  4. ben51

    ben51 Guest

    Hello,

    Yes I think that SFU was installed on this DC, but I already have applied
    the change from the KB 919938 and after that it makes the errors you already
    seen. Before I applied the schéma changes, it was this:

    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.102" for object
    "CN=uid,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the schema
    extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "isSingleValued" attribute value for objects defined in Windows 2000 schema
    and extended schema do not match.



    A previous schema extension has defined the attribute value as "TRUE" for
    object "CN=uid,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeSyntax" attribute value for objects defined in Windows 2000 schema
    and extended schema do not match.



    A previous schema extension has defined the attribute value as "2.5.5.5" for
    object "CN=uid,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.70" for object
    "CN=uidNumber,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.71" for object
    "CN=gidNumber,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.97" for object
    "CN=gecos,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.72" for object
    "CN=loginShell,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.92" for object
    "CN=shadowLastChange,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently
    than the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.93" for object
    "CN=shadowMin,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeSyntax" attribute value for objects defined in Windows 2000 schema
    and extended schema do not match.



    A previous schema extension has defined the attribute value as "2.5.5.5" for
    object "CN=shadowMin,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently
    than the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.90" for object
    "CN=shadowMax,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.91" for object
    "CN=shadowWarning,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than
    the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeSyntax" attribute value for objects defined in Windows 2000 schema
    and extended schema do not match.



    A previous schema extension has defined the attribute value as "2.5.5.5" for
    object "CN=shadowWarning,CN=Schema,CN=Configuration,DC=ilmh,DC=be"
    differently than the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.89" for object
    "CN=shadowInactive,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than
    the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.88" for object
    "CN=shadowExpire,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than
    the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.87" for object
    "CN=shadowFlag,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.86" for object
    "CN=memberUid,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.79" for object
    "CN=memberNisNetgroup,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently
    than the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeSyntax" attribute value for objects defined in Windows 2000 schema
    and extended schema do not match.



    A previous schema extension has defined the attribute value as "2.5.5.1" for
    object "CN=memberNisNetgroup,CN=Schema,CN=Configuration,DC=ilmh,DC=be"
    differently than the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.74" for object
    "CN=ipServicePort,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than
    the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.75" for object
    "CN=ipServiceProtocol,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently
    than the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.76" for object
    "CN=ipProtocolNumber,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently
    than the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.81" for object
    "CN=oncRpcNumber,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than
    the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.82" for object
    "CN=ipHostNumber,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than
    the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.77" for object
    "CN=ipNetworkNumber,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently
    than the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.78" for object
    "CN=ipNetmaskNumber,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently
    than the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.85" for object
    "CN=macAddress,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.96" for object
    "CN=bootParameter,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than
    the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.98" for object
    "CN=bootFile,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.94" for object
    "CN=nisMapName,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "isSingleValued" attribute value for objects defined in Windows 2000 schema
    and extended schema do not match.



    A previous schema extension has defined the attribute value as "FALSE" for
    object "CN=nisMapName,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently
    than the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "attributeId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.4.7000.187.95" for object
    "CN=nisMapEntry,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than
    the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "isSingleValued" attribute value for objects defined in Windows 2000 schema
    and extended schema do not match.



    A previous schema extension has defined the attribute value as "FALSE" for
    object "CN=nisMapEntry,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently
    than the schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.







    =============================================================================

    "governsId" attribute value for objects defined in Windows 2000 schema and
    extended schema do not match.



    A previous schema extension has defined the attribute value as
    "1.2.840.113556.1.5.7000.106.58" for object
    "CN=nisMap,CN=Schema,CN=Configuration,DC=ilmh,DC=be" differently than the
    schema extension needed for Windows 2003 server .

    [Status/Consequence]

    Adprep cannot extend your existing schema

    [User Action]

    Contact the vendor of the application that previously extended the schema to
    resolve the inconsistency. Then run adprep again.
     
    ben51, Apr 10, 2009
    #4
  5. ben51

    kj [SBS MVP] Guest

    Are you attempting a schema upgrade directly to V31 (R2)?

    Have you tried to first upgrade to V30 (2003 rtm)?

    Are you aware of any other schema exending installations that may have been
    applied?
     
    kj [SBS MVP], Apr 10, 2009
    #5
  6. ben51

    ben51 Guest

    Yes I try with windows 2003 cd but it makes another error :

    Adprep a détecté que les Services Microsoft Windows pour UNIX (SFU) sont
    install
    és dans cette forêt. Avant de continuer à utiliser adprep /forestprep, vous
    deve
    z appliquer le correctif logiciel Microsoft Q293783 pour SFU. Veuillez
    contacter
    les services de support technique Microsoft afin d'obtenir ce correctif.
    (Ce co
    rrectif logiciel n'est pas disponible sur le site Web Microsoft.)

    Sorry it is in french, but when I applied the patch it says that SFU isn't
    installed.

     
    ben51, Apr 10, 2009
    #6
  7. ben51

    kj [SBS MVP] Guest

    Unfortunately my French isn't very good, but what it should be saying is to
    the effect.of;

    Adprep successfully determined whether Microsoft Windows Services for UNIX
    (SFU) is installed or not. If adprep detected SFU, adprep also verified that
    Microsoft hotfix Q293783 for SFU has been applied.

    Can you translate that it is telling your that it did "successfully"
    determine or "unsuccessfully"?

    I think this is the first cause and you'll need to get this to complete
    before going to R2 (v31).

    First make sure that all your DC's are 2000 SP4 and above. Perhaps even
    re-applying SP4 again.

    Then repeat.

    If it still fails,

    Check the Ldif.err log file in the C:\WINNT\debug\adprep\logs\<date>
    directory for detailed information.


     
    kj [SBS MVP], Apr 10, 2009
    #7
  8. ben51

    ben51 Guest

    Ok the forestprep is running but it doesn't finished his job. It sounds like
    it fails to move the LDIFF.err log file. Here is the output log from adprep:

    Adprep verified the state of operation
    cn=4444c516-f43a-4c12-9c4b-b5c064941d61,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=ilmh,DC=be.

    [Status/Consequence]

    The operation has not run or is not currently running. It will be run next.



    Adprep was unable to complete because the call back function (null) failed.

    [Status/Consequence]

    Error message: Error(110) while running ""C:\WINNT\system32\LDIFde.exe" -o
    ObjectGuid -d
    "CN=user-Display,CN=405,CN=DisplaySpecifiers,CN=Configuration,DC=ilmh,DC=be"
    -u -f "C:\DOCUME~1\Admin\LOCALS~1\Temp\8\TMP60.tmp" -j
    "C:\WINNT\system32\debug\adprep\logs\20090410114224" -s melchior.ilmh.be".
    Could not move file
    C:\WINNT\system32\debug\adprep\logs\20090410114224\LDIF.err to
    C:\WINNT\system32\debug\adprep\logs\20090410114224\DisplaySpecifierUpgradeLdifError.001.txt. Le fichier sp‚cifi‚ est introuvable.

    (0x80070002).

    [User Action]

    Check the log file Adprep.log, in the
    C:\WINNT\system32\debug\adprep\logs\20090410114224 directory for more
    information.



    Adprep set the value of registry key
    System\CurrentControlSet\Services\NTDS\Parameters\Schema Update Allowed to 1



    Adprep was unable to update forest-wide information.

    [Status/Consequence]

    Adprep requires access to existing forest-wide information from the schema
    master in order to complete this operation.

    [User Action]

    Check the log file, Adprep.log, in the
    C:\WINNT\system32\debug\adprep\logs\20090410114224 directory for more
    information.
     
    ben51, Apr 10, 2009
    #8
  9. Hello ben51,

    Did you run the command on the schema master with an account that is member
    of the schema admin groups?

    Check with "netdom query fsmo" in a command prompt which machine the schema
    master is. Maybe you have to install the support/tools/suptools.msi from
    the 2000 installation disk.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Apr 10, 2009
    #9
  10. ben51

    ben51 Guest

    Yes for sure. I had already make this test. I also check up if my admin login
    has the Manage auditing and security log rights.
     
    ben51, Apr 10, 2009
    #10
  11. Hello ben51,

    Check out this article:
    http://support.microsoft.com/kb/324392

    Did you use the installation media for updating or copied the adprep folder
    from the disk to server? If last option is used, take the installation disk
    and run it from there.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Apr 10, 2009
    #11
  12. ben51

    ben51 Guest

    First thanks for your help. I run it from the installation media.
     
    ben51, Apr 10, 2009
    #12
  13. ben51

    kj [SBS MVP] Guest

    Might also want to do some basic forest/domain health checks with dcdiag /c
    /v /e, netdiag, and nltest as well.
     
    kj [SBS MVP], Apr 10, 2009
    #13
  14. ben51

    ben51 Guest

    When I run dcdiag /v I 've got some errors from the test in systemlog:

    Starting test: systemlog
    * The System Event log test
    An Error Event occured. EventID: 0x00000457
    Time Generated: 04/21/2009 13:01:30
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000452
    Time Generated: 04/21/2009 13:01:30
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000457
    Time Generated: 04/21/2009 13:01:30
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000452
    Time Generated: 04/21/2009 13:01:31
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000457
    Time Generated: 04/21/2009 13:01:31
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000452
    Time Generated: 04/21/2009 13:01:31
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000457
    Time Generated: 04/21/2009 13:01:32
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000452
    Time Generated: 04/21/2009 13:01:32
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000457
    Time Generated: 04/21/2009 13:01:33
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000452
    Time Generated: 04/21/2009 13:01:33
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000457
    Time Generated: 04/21/2009 13:01:33
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000452
    Time Generated: 04/21/2009 13:01:33
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000457
    Time Generated: 04/21/2009 13:01:34
    (Event String could not be retrieved)
    An Error Event occured. EventID: 0x00000452
    Time Generated: 04/21/2009 13:01:34
    (Event String could not be retrieved)
    ......................... SERVERNAME failed test systemlog
     
    ben51, Apr 21, 2009
    #14
  15. Hello ben51,

    For that you have to check the event viewer for errors. These are just the
    list that there are existing errors, maybe not relevant but check them and
    post here the complete error.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Apr 21, 2009
    #15
  16. ben51

    ben51 Guest

    It 's just some printers that he could not connect and all the other tests
    are passed.
     
    ben51, Apr 21, 2009
    #16
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.