adprep /forestprep Fails with errors

G

Guest

We have successfully upgraded Exchange E2K to E2K3 on a DC running W2K SP4.
Now we are trying to upgrade DC to W2K3.
When we ran adprep /forestprep, it has lots of issues, checked the whole
internet, still having the same issues :)

The errors are
*******************************
7: CN=uid,CN=Schema,CN=Configuration,DC=enetfinity,DC=com
Entry DN: CN=uid,CN=Schema,CN=Configuration,DC=enetfinity,DC=com
Add error on line 62: Unwilling To Perform
The server side error is "Schema update failed: duplicate LDAP display name."
6 entries modified successfully.
An error has occurred in the program
*******************************


Somewhere on the MS website, told to run the script schchk.vbs.

After running this script, getting the following errors:

*******************************

================================================================================
schchk run at 12/21/2004 8:39:38 PM
schema file schemadump.ldf
schema addition file sch18.ldf
Reading schema: done (87.48438).
1951 attributes and 355classes.

Processing file to check:
Oid 1.2.840.113556.1.2.444 used in schema addition
cn=ms-exch-assistant-name,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=ms-exch-assistant-name,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 1.2.840.113556.1.2.593 used in schema addition
cn=ms-exch-labeleduri,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=ms-exch-labeleduri,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 0.9.2342.19200300.100.1.55 used in schema addition
cn=audio,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for cn=audio,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 0.9.2342.19200300.100.1.7 used in schema addition
cn=photo,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for cn=photo,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 0.9.2342.19200300.100.1.60 used in schema addition
cn=jpegphoto,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=jpegphoto,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 0.9.2342.19200300.100.1.21 used in schema addition
cn=secretary,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=secretary,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 2.16.840.1.113730.3.1.216 used in schema addition
cn=userpkcs12,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=userpkcs12,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 2.16.840.1.113730.3.1.1 used in schema addition
cn=carlicense,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=carlicense,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 1.3.6.1.4.1.250.1.57 used in schema addition
cn=labeleduri,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=labeleduri,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 0.9.2342.19200300.100.1.6 used in schema addition
cn=roomnumber,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=roomnumber,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 2.5.4.50 used in schema addition
cn=uniquemember,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=uniquemember,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 2.16.840.1.113730.3.1.2 used in schema addition
cn=departmentnumber,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=departmentnumber,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 1.2.840.113549.1.9.2 used in schema addition
cn=unstructuredname,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=unstructuredname,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 2.16.840.1.113730.3.1.39 used in schema addition
cn=preferredlanguage,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=preferredlanguage,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 2.5.4.45 used in schema addition
cn=x500uniqueidentifier,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=x500uniqueidentifier,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 1.2.840.113549.1.9.8 used in schema addition
cn=unstructuredaddress,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=unstructuredaddress,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.

Oid 2.5.4.58 used in schema addition
cn=attributecertificateattribute,cn=schema,cn=configuration,=configuration,dc=enetfinity,dc=com
already exists for
cn=attributecertificateattribute,cn=schema,cn=configuration,dc=enetfinity,dc=com
Adding this attribute would result in duplicate oids which is not allowed.
done (0.84375).

*******************************

I really appreciate, if any oen could help us out in this.

Regards
-Sudhakar
 
G

Guest

THe following is the error we are getting, when we run adprep, the KB note
has already been applied.

****************************************************
7: CN=uid,CN=Schema,CN=Configuration,DC=enetfinity,DC=com
Entry DN: CN=uid,CN=Schema,CN=Configuration,DC=enetfinity,DC=com
Add error on line 62: Unwilling To Perform
The server side error is "Schema update failed: duplicate LDAP display name."
6 entries modified successfully.
An error has occurred in the program

****************************************************

Thanks for any help on this.
Regards
-Sudhakar
 

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. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Upgrade Adprep error 1
want the Windows 2003 Server Join to an W2K domain be a DC 2
ADPREP for windows 2003 AD failed 5
ADPREP failure on Win2K server 8
remove sub-domain on root domain 2
Problem with the schema master server 1
adprep failure, adding 2003 R2 x64 server to 2000 domain 5
2k server to 2k3 AD upgrade 0

Top