Re: ADPrep /domainprep error
- From: tarolvey <tarolvey@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 6 Oct 2006 13:24:02 -0700
Sorry Herb my mistake it was not the schema master that I moved over It was
the Infrastructure Master and yes I did run it on the Ifrastructure Master
and DCdiag comes up clean not a single error. could one of the hotfixes be
causing a problem? or a particular service.
--
To hell and back!
"Herb Martin" wrote:
.Adprep was unable to update domain-wide information.
[Status/Consequence]Adprep requires access to existing domain-wide
information from the infrastructure master in order to complete this
operation.[User Action] Check the log file, Adprep.log, in the
C:\WINNT\system32\debug\adprep\logs\20060906135606 directory for more
information.
I have tried moving schema master over to other DC and run it from
there,but the same error occurs,I have run dcdiag on both DC with no
errors
verified the sysvol entry is correct in the registry I am loged in with
the
appropriate permissions,the event logs are clean(no errors) but I can't
seem
to resolve the issue. If anyone has seen this error or might have a
solution
then I would be very grateful for any help you can provide.
Did you verify that your Infrastructure Master is healthy?
(DCDiag should have complained if it were not.)
Did you try running the prep on the Infrastructure Master
or on the 'other DC' instead of messing with the Schema
Master which is only for ForestPrep?
"tarolvey" <tarolvey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A958170F-CF9A-4C33-B5A9-8953352EE113@xxxxxxxxxxxxxxxx
I have two windows 2000 servers sp4 and I would like to add a windows 2003
R2
sever to the domain and have run adprep /forestprep on schema master
(which
holds all operations) with no errors, I then ran adprep /domainprep and
failed with the following message:
Adprep created the log file ADPrep.log under
C:\WINNT\system32\debug\adprep\logs\20060906135606 directory.
Adprep copied file L:\I386\schema.ini from installation point to local
machine under directory C:\WINNT.
Adprep successfully made the LDAP connection to the local domain
controller
NEGUS.
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 was about to call the following LDAP API. ldap_add_s(). The entry
to
add is cn=DomainUpdates,cn=System,DC=oz,DC=lds.
LDAP API ldap_add_s() finished, return code is 0x44
Adprep attempted to create the directory service object
cn=DomainUpdates,cn=System,DC=oz,DC=lds.[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=DomainUpdates,cn=System,DC=oz,DC=lds.
LDAP API ldap_add_s() finished, return code is 0x44
Adprep attempted to create the directory service object
cn=Operations,cn=DomainUpdates,cn=System,DC=oz,DC=lds.[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=ab402345-d3c3-455d-9ff7-40268a1099b6,cn=Operations,cn=DomainUpdates,cn=System,DC=oz,DC=lds.
LDAP API ldap_search_s() finished, return code is 0x20
Adprep verified the state of operation
cn=ab402345-d3c3-455d-9ff7-40268a1099b6,cn=Operations,cn=DomainUpdates,cn=System,DC=oz,DC=lds.
[Status/Consequence]The operation has not run or is not currently running.
It
will be run next.
Adprep was about to call the following LDAP API. ldap_add_s(). The entry
to
add is CN=WMIPolicy,CN=System,DC=oz,DC=lds.
LDAP API ldap_add_s() finished, return code is 0x13
Adprep was unable to create the object CN=WMIPolicy,CN=System,DC=oz,DC=lds
in Active Directory.[Status/Consequence]This Adprep operation failed.[User
Action] Check the log file adprep.log in the system root
System32\Debug\Adprep\Logs directory for more information. Restart Adprep.
Adprep encountered an LDAP error. Error code: 0x13. Server extended error
code: 0x51b, Server error message: 0000051B: AtrErr: DSID-031506FD, #1:
0: 0000051B: DSID-031506FD, problem 1005 (CONSTRAINT_ATT_TYPE), data 0,
Att
20119 (nTSecurityDescriptor)
Adprep was unable to update domain-wide information.
[Status/Consequence]Adprep requires access to existing domain-wide
information from the infrastructure master in order to complete this
operation.[User Action] Check the log file, Adprep.log, in the
C:\WINNT\system32\debug\adprep\logs\20060906135606 directory for more
information.
I have tried moving schema master over to other DC and run it from
there,but the same error occurs,I have run dcdiag on both DC with no
errors
verified the sysvol entry is correct in the registry I am loged in with
the
appropriate permissions,the event logs are clean(no errors) but I can't
seem
to resolve the issue. If anyone has seen this error or might have a
solution
then I would be very grateful for any help you can provide.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Thanks so much!
--
To hell and back!
- References:
- ADPrep /domainprep error
- From: tarolvey
- Re: ADPrep /domainprep error
- From: Herb Martin
- ADPrep /domainprep error
- Prev by Date: System State Restore - extra files
- Next by Date: Re: ADPrep /domainprep error
- Previous by thread: Re: ADPrep /domainprep error
- Next by thread: Re: ADPrep /domainprep error
- Index(es):
Relevant Pages
|
