Re: adprep failure, adding 2003 R2 x64 server to 2000 domain Optio

You get the code for your 32bit o/s, give it a whirl.

You are logged on as the schema admin when you go to extend this, correct?

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Doug B" <DougB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:67AECD4D-D14C-4D24-94F3-BC49B03853A1@xxxxxxxxxxxxxxxx
Paul,

From this blog entry I went with option #2, which from my reading is a
better option to try. It comes from the MS KB919151.

Is there something better about the trial version that you know of?

DB

"Paul Bergson [MVP-DS]" wrote:

Try downloading a trial version of Windows 2003 R2 and extending.
http://technet.microsoft.com/en-us/windowsserver/bb430833.aspx


(From
http://blogs.dirteam.com/blogs/jorge/archive/2007/01/05/How-to-deploy-64-bit-R2-DCs-in-a-32-bit-W2K3-AD-environment.aspx)



--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.

"Doug B" <DougB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CB93ED81-1830-41FE-B81E-7A3E6E9B4394@xxxxxxxxxxxxxxxx
I have only 1 DC in my 2000 domain, it is SP4 and up to date (patch
wise). The 2003 R2 server is x64, so I got the hotfix KB919151 from
microsoft. While running the adprep /forestprep (on the current dc
server as administrator) it errors out.

basically it is erroring out on two points.


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


Error message: Unable to connect to the domain controller
"xxxxxxx.com". "


And


"Adprep was unable to update forest-wide information.


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


I have run dcdiag /c /v and it only reports failure on SMTP service
not running and errors with kccevent. Both of which should have no
impact.


I also ran netdiag /v, no problems.


ran repadmin /showconn, it does show the one and only server


ran repadmin /showreps, again point to the dc server.


FSMO, all roles point to the current dc server.


Log follows: (this is the second attempt at running adprep, the first
shows
that it has upgraded the schema version to 31.)
=====================================================
Adprep created the log file ADPrep.log under C:\WINNT\system32\debug
\adprep\logs\20070707151104 directory.


Adprep copied file D:\adprep\schema.ini from installation point to
local machine under directory C:\WINNT.


Adprep copied file D:\adprep\dcpromo.csv from installation point to
local machine under directory C:\WINNT\system32\debug\adprep\data.


Adprep copied file D:\adprep\409.csv from installation point to local
machine under directory C:\WINNT\system32\debug\adprep\data.


Adprep successfully made the LDAP connection to the local domain
controller XXXXXX.


Adprep was about to call the following LDAP API. ldap_search_s(). The
base entry to start the search is (null).


LDAP API ldap_search_s() finished, return code is 0x0


Adprep successfully retrieved information from the local directory
service.


Adprep successfully initialized global variables.


[Status/Consequence]


Adprep is continuing.


ADPREP WARNING:


Before running adprep, all Windows 2000 domain controllers in the
forest should be upgraded to Windows 2000 Service Pack 1 (SP1) with
QFE 265089, or to Windows 2000 SP2 (or later).


QFE 265089 (included in Windows 2000 SP2 and later) is required to
prevent potential domain controller corruption.


For more information about preparing your forest and domain see KB
article Q331161 at http://support.microsoft.com.


[User Action]


If ALL your existing Windows 2000 domain controllers meet this
requirement, type C and then press ENTER to continue. Otherwise, type
any other key and press ENTER to quit.


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


Adprep was about to call the following LDAP API. ldap_add_s(). The
entry to add is cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=com.


LDAP API ldap_add_s() finished, return code is 0x44


Adprep attempted to create the directory service object
cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=com.


[Status/Consequence]


The object exists so Adprep did not attempt to rerun this operation
but is continuing.


Adprep was about to call the following LDAP API. ldap_add_s(). The
entry to add is
cn=Operations,cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=com.


LDAP API ldap_add_s() finished, return code is 0x44


Adprep attempted to create the directory service object
cn=Operations,cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=com.


[Status/Consequence]


The object exists so Adprep did not attempt to rerun this operation
but is continuing.


Adprep was about to call the following LDAP API. ldap_search_s(). The
base entry to start the search is cn=3467dae5-dedd-4648-9066-
f48ac186b20a,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=co­m.


LDAP API ldap_search_s() finished, return code is 0x0


Adprep checked to verify whether operation cn=3467dae5-dedd-4648-9066-
f48ac186b20a,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=co­m
has completed.


[Status/Consequence]


The operation GUID already exists so Adprep did not attempt to rerun
this operation but is continuing.


Adprep was about to call the following LDAP API. ldap_search_s(). The
base entry to start the search is cn=33b7ee33-1386-47cf-baa1-
b03e06473253,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=co­m.


LDAP API ldap_search_s() finished, return code is 0x0


Adprep checked to verify whether operation cn=33b7ee33-1386-47cf-baa1-
b03e06473253,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=co­m
has completed.


[Status/Consequence]


The operation GUID already exists so Adprep did not attempt to rerun
this operation but is continuing.


Adprep was about to call the following LDAP API. ldap_search_s(). The
base entry to start the search is cn=e9ee8d55-c2fb-4723-a333-
c80ff4dfbf45,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=co­m.


LDAP API ldap_search_s() finished, return code is 0x0


Adprep checked to verify whether operation cn=e9ee8d55-c2fb-4723-a333-
c80ff4dfbf45,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=co­m
has completed.


[Status/Consequence]


The operation GUID already exists so Adprep did not attempt to rerun
this operation but is continuing.


Adprep was about to call the following LDAP API. ldap_search_s(). The
base entry to start the search is
cn=ccfae63a-7fb5-454c-83ab-0e8e1214974e,cn=Operations,cn=ForestUpdates,CN=C­onfiguration,DC=XXXXX,DC=com.


LDAP API ldap_search_s() finished, return code is 0x0


Adprep checked to verify whether operation
cn=ccfae63a-7fb5-454c-83ab-0e8e1214974e,cn=Operations,cn=ForestUpdates,CN=C­onfiguration,DC=XXXXX,DC=com
has completed.


[Status/Consequence]


The operation GUID already exists so Adprep did not attempt to rerun
this operation but is continuing.


Adprep was about to call the following LDAP API. ldap_search_s(). The
base entry to start the search is cn=ad3c7909-
b154-4c16-8bf7-2c3a7870bb3d,cn=Operations,cn=ForestUpdates,CN=Configuration­,DC=XXXXX,DC=com.


LDAP API ldap_search_s() finished, return code is 0x0


Adprep checked to verify whether operation cn=ad3c7909-
b154-4c16-8bf7-2c3a7870bb3d,cn=Operations,cn=ForestUpdates,CN=Configuration­,DC=XXXXX,DC=com
has completed.


[Status/Consequence]


The operation GUID already exists so Adprep did not attempt to rerun
this operation but is continuing.


Adprep was about to call the following LDAP API. ldap_search_s(). The
base entry to start the search is cn=26ad2ebf-f8f5-44a4-b97c-
a616c8b9d09a,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=co­m.


LDAP API ldap_search_s() finished, return code is 0x0


Adprep checked to verify whether operation cn=26ad2ebf-f8f5-44a4-b97c-
a616c8b9d09a,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=co­m
has completed.


[Status/Consequence]


The operation GUID already exists so Adprep did not attempt to rerun
this operation but is continuing.


Adprep was about to call the following LDAP API. ldap_search_s(). The
base entry to start the search is cn=4444c516-f43a-4c12-9c4b-
b5c064941d61,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=XXXXX,DC=co­m.


LDAP API ldap_search_s() finished, return code is 0x20


.

Relevant Pages

  • Re: Adrprep /domainprep fails
    ... [Status/Consequence] ... Adprep is continuing. ... The object exists so Adprep did not attempt to rerun this operation but is continuing. ... The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing. ...
    (microsoft.public.win2000.active_directory)
  • ADPREP /DOMAINPREP /GPPREP
    ... Adprep created the log file ADPrep.log under ... Adprep was about to call the following LDAP API. ... entry to start the search is. ... [Status/Consequence] ...
    (microsoft.public.windows.server.active_directory)
  • Re: ADPREP /DOMAINPREP /GPPREP
    ... Adprep created the log file ADPrep.log under ... Adprep was about to call the following LDAP API. ... entry to start the search is. ... [Status/Consequence] ...
    (microsoft.public.windows.server.active_directory)
  • Re: Adprep for Windows 2008
    ... [Status/Consequence] ... The operation GUID already exists so Adprep did not attempt to rerun this ... Adprep was about to call the following LDAP API. ... entry to start the search is ...
    (microsoft.public.windows.server.active_directory)
  • Re: Adprep for Windows 2008
    ... [Status/Consequence] ... Adprep merged the existing security descriptor with the new access control ... entry. ... Adprep was about to call the following LDAP API. ...
    (microsoft.public.windows.server.active_directory)