adprep /forestprep errors

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I ran adprep forest prep and SCh14.ldf thru sch30.ldf are still in
winnt\system32. How can I tell if it upgraded correctly?

The last part of the logs are as follows


Adprep was about to call the following LDAP API. ldap_modify_s(). The entry
to modify is CN=Ipsec-Policy,CN=Schema,CN=Configuration,DC=bnicoal0,DC=com.



LDAP API ldap_modify_s() finished, return code is 0x33



ADPREP was unable to modify the default security descriptor on object
CN=Ipsec-Policy,CN=Schema,CN=Configuration,DC=bnicoal0,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 system root System32\Debug\Adprep\Logs
directory for more information.

Adprep encountered an LDAP error.

Error code: 0x33. Server extended error code: 0x20d9, Server error message:
000020D9: SvcErr: DSID-030A05F8, problem 5001 (BUSY), data 33
..



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\20050915152908 directory for more
information.
 
To resolve this issue I would suggest you to run the script and the
registry changes mentioned in the KB Artilce: 329194

HTH
Srikanth N
 
I ran adprep forest prep and SCh14.ldf thru sch30.ldf are
still in
winntsystem32. How can I tell if it upgraded correctly?

The last part of the logs are as follows


Adprep was about to call the following LDAP API.
ldap_modify_s(). The entry
to modify is
CN=Ipsec-Policy,CN=Schema,CN=Configuration,DC=bnicoal0,DC=com.



LDAP API ldap_modify_s() finished, return code is 0x33



ADPREP was unable to modify the default security descriptor on
object
CN=Ipsec-Policy,CN=Schema,CN=Configuration,DC=bnicoal0,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 system root
System32DebugAdprepLogs
directory for more information.

Adprep encountered an LDAP error.

Error code: 0x33. Server extended error code: 0x20d9, Server
error message:
000020D9: SvcErr: DSID-030A05F8, problem 5001 (BUSY), data 33
..



Adprep set the value of registry key
SystemCurrentControlSetServicesNTDSParametersSchema
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:WINNTsystem32debugadpreplogs20050915152908 directory
for more
information
Click to expand...

See:
MS-KBQ314649_W2K3 ADPREP Command Causes Mangled Attributes in W2K
Forests That Contain E2K Servers
MS-KBQ325379_How to Upgrade Windows 2000 Domain Controllers to Windows
Server 2003
MS-KBQ555040_Common Mistakes When Upgrade Windows 2000 Domain To
Windows 2003
http://www.petri.co.il/windows_2003_adprep.htm


You can rerun ADPREP /FORESTPREP on the schema master if you meet all
prerequisites mentioned in the articles.

Afterwards run ADPREP /DOMAINPREP on the Infrastructure master
 
Back
Top