Mirgating from 2003 to 2008

Discussion in 'Server Setup' started by ccheever, Oct 2, 2013.

  1. ccheever

    ccheever

    Joined:
    Oct 2, 2013
    Messages:
    1
    Likes Received:
    0
    Im migrating from a 2003 DC to a 2008 DC and im getting an error, I attached the log.

    The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing.
    [2013/10/02:11:39:00.814]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=dca8f425-baae-47cd-b424-e3f6c76ed08b,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=corningdata,DC=com.
    [2013/10/02:11:39:00.814]
    LDAP API ldap_search_s() finished, return code is 0x0
    [2013/10/02:11:39:00.814]
    Adprep checked to verify whether operation cn=dca8f425-baae-47cd-b424-e3f6c76ed08b,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=corningdata,DC=com has completed.

    [Status/Consequence]

    The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing.
    [2013/10/02:11:39:00.814]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=a662b036-dbbe-4166-b4ba-21abea17f9cc,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=corningdata,DC=com.
    [2013/10/02:11:39:00.814]
    LDAP API ldap_search_s() finished, return code is 0x0
    [2013/10/02:11:39:00.814]
    Adprep checked to verify whether operation cn=a662b036-dbbe-4166-b4ba-21abea17f9cc,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=corningdata,DC=com has completed.

    [Status/Consequence]

    The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing.
    [2013/10/02:11:39:00.814]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=9d17b863-18c3-497d-9bde-45ddb95fcb65,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=corningdata,DC=com.
    [2013/10/02:11:39:00.814]
    LDAP API ldap_search_s() finished, return code is 0x0
    [2013/10/02:11:39:00.814]
    Adprep checked to verify whether operation cn=9d17b863-18c3-497d-9bde-45ddb95fcb65,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=corningdata,DC=com has completed.

    [Status/Consequence]

    The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing.
    [2013/10/02:11:39:00.814]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=11c39bed-4bee-45f5-b195-8da0e05b573a,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=corningdata,DC=com.
    [2013/10/02:11:39:00.814]
    LDAP API ldap_search_s() finished, return code is 0x20
    [2013/10/02:11:39:00.814]
    Adprep verified the state of operation cn=11c39bed-4bee-45f5-b195-8da0e05b573a,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=corningdata,DC=com.

    [Status/Consequence]

    The operation has not run or is not currently running. It will be run next.
    [2013/10/02:11:39:00.830]
    ADPREP was unable to modify the default security descriptor on object CN=ms-DS-Managed-Service-Account,CN=Schema,CN=Configuration,DC=corningdata,DC=com.

    [Status/Consequence]

    Adprep attempts to merge the existing default security descriptors with the new access control entry (ACE).

    [User Action]

    Check the log file ADPrep.log in the C:\WINDOWS\debug\adprep\logs\20131002113859 directory for more information.
    [2013/10/02:11:39:00.845]
    Adprep encountered an LDAP error.

    Error code: 0x20. Server extended error code: 0x208d, Server error message: 0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
    'CN=Schema,CN=Configuration,DC=corningdata,DC=com'
    .
    [2013/10/02:11:39:00.845]
    Adprep set the value of registry key System\CurrentControlSet\Services\NTDS\Parameters\Schema Update Allowed to 1
    [2013/10/02:11:39:00.861]
    Adprep was unable to update forest 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:\WINDOWS\debug\adprep\logs\20131002113859 directory for more information.
     
    Last edited: Oct 2, 2013
    ccheever, Oct 2, 2013
    #1
    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.