Schema errors when trying to update for 2003 R2
- From: "Jim Williams" <williams_email@xxxxxxxxxxxxxx>
- Date: 25 Jul 2006 05:19:46 -0700
I'm getting some errors when I run adprep /forestprep from CD 2 of 2003
R2.
At the moment we have 5 domain controllers, four are running Windows
2000 and one is running Windows 2003. I upgraded our schema last year
so that we could add a 2003 domain controller and everying went fine
(alghough I did have to run a hotfix from MS because we previously had
Services for Unix installed - I think that's our problem!).
I setup a VMWARE machine with 2003 server SP1 installed and added it to
our domain. I then installed AD on it and transferred the Schema Master
role to it. I then stopped outbound replication, took a snapshot (just
in case) and tried to run adprep /forestprep, but I get the following
errors:
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.79" for object
"CN=memberNisNetgroup,CN=Schema,CN=Configuration,DC=q
ueenelizabeth,DC=cumbria,DC=sch,DC=uk" differently than the schema
extension nee
ded for Windows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeSyntax" attribute value for objects defined in Windows 2000
schema and
extended schema do not match.
A previous schema extension has defined the attribute value as
"2.5.5.1" for obj
ect
"CN=memberNisNetgroup,CN=Schema,CN=Configuration,DC=queenelizabeth,DC=cumbri
a,DC=sch,DC=uk" differently than the schema extension needed for
Windows 2003 se
rver .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeId" attribute value for objects defined in Windows 2000
schema and ext
ended schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.74" for object
"CN=ipServicePort,CN=Schema,CN=Configuration,DC=queen
elizabeth,DC=cumbria,DC=sch,DC=uk" differently than the schema
extension needed
for Windows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeId" attribute value for objects defined in Windows 2000
schema and ext
ended schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.75" for object
"CN=ipServiceProtocol,CN=Schema,CN=Configuration,DC=q
ueenelizabeth,DC=cumbria,DC=sch,DC=uk" differently than the schema
extension nee
ded for Windows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeId" attribute value for objects defined in Windows 2000
schema and ext
ended schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.76" for object
"CN=ipProtocolNumber,CN=Schema,CN=Configuration,DC=qu
eenelizabeth,DC=cumbria,DC=sch,DC=uk" differently than the schema
extension need
ed for Windows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeId" attribute value for objects defined in Windows 2000
schema and ext
ended schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.81" for object
"CN=oncRpcNumber,CN=Schema,CN=Configuration,DC=queene
lizabeth,DC=cumbria,DC=sch,DC=uk" differently than the schema extension
needed f
or Windows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeId" attribute value for objects defined in Windows 2000
schema and ext
ended schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.82" for object
"CN=ipHostNumber,CN=Schema,CN=Configuration,DC=queene
lizabeth,DC=cumbria,DC=sch,DC=uk" differently than the schema extension
needed f
or Windows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeId" attribute value for objects defined in Windows 2000
schema and ext
ended schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.77" for object
"CN=ipNetworkNumber,CN=Schema,CN=Configuration,DC=que
enelizabeth,DC=cumbria,DC=sch,DC=uk" differently than the schema
extension neede
d for Windows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeId" attribute value for objects defined in Windows 2000
schema and ext
ended schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.78" for object
"CN=ipNetmaskNumber,CN=Schema,CN=Configuration,DC=que
enelizabeth,DC=cumbria,DC=sch,DC=uk" differently than the schema
extension neede
d for Windows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeId" attribute value for objects defined in Windows 2000
schema and ext
ended schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.85" for object
"CN=macAddress,CN=Schema,CN=Configuration,DC=queeneli
zabeth,DC=cumbria,DC=sch,DC=uk" differently than the schema extension
needed for
Windows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeId" attribute value for objects defined in Windows 2000
schema and ext
ended schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.96" for object
"CN=bootParameter,CN=Schema,CN=Configuration,DC=queen
elizabeth,DC=cumbria,DC=sch,DC=uk" differently than the schema
extension needed
for Windows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeId" attribute value for objects defined in Windows 2000
schema and ext
ended schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.98" for object
"CN=bootFile,CN=Schema,CN=Configuration,DC=queeneliza
beth,DC=cumbria,DC=sch,DC=uk" differently than the schema extension
needed for W
indows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeId" attribute value for objects defined in Windows 2000
schema and ext
ended schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.94" for object
"CN=nisMapName,CN=Schema,CN=Configuration,DC=queeneli
zabeth,DC=cumbria,DC=sch,DC=uk" differently than the schema extension
needed for
Windows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"isSingleValued" attribute value for objects defined in Windows 2000
schema and
extended schema do not match.
A previous schema extension has defined the attribute value as "FALSE"
for objec
t
"CN=nisMapName,CN=Schema,CN=Configuration,DC=queenelizabeth,DC=cumbria,DC=sch,
DC=uk" differently than the schema extension needed for Windows 2003
server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"attributeId" attribute value for objects defined in Windows 2000
schema and ext
ended schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..4.7000.187.95" for object
"CN=nisMapEntry,CN=Schema,CN=Configuration,DC=queenel
izabeth,DC=cumbria,DC=sch,DC=uk" differently than the schema extension
needed fo
r Windows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"isSingleValued" attribute value for objects defined in Windows 2000
schema and
extended schema do not match.
A previous schema extension has defined the attribute value as "FALSE"
for objec
t
"CN=nisMapEntry,CN=Schema,CN=Configuration,DC=queenelizabeth,DC=cumbria,DC=sch
,DC=uk" differently than the schema extension needed for Windows 2003
server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
=============================================================================
"governsId" attribute value for objects defined in Windows 2000 schema
and exten
ded schema do not match.
A previous schema extension has defined the attribute value as
"1.2.840.113556.1
..5.7000.106.58" for object
"CN=nisMap,CN=Schema,CN=Configuration,DC=queenelizabe
th,DC=cumbria,DC=sch,DC=uk" differently than the schema extension
needed for Win
dows 2003 server .
[Status/Consequence]
Adprep cannot extend your existing schema
[User Action]
Contact the vendor of the application that previously extended the
schema to res
olve the inconsistency. Then run adprep again.
I've checked the parameters on the Microsoft website at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adschema/adschema/active_directory_schema.asp
and they are not correct. However, I can't modify the entries using
ADSIEDIT as I get an error message about the 'attribute being owned by
the system'.
Can anybody offer any advice on the best way forward? Thanks for taking
the time to read this post.
Jim
.
- Follow-Ups:
- Re: Schema errors when trying to update for 2003 R2
- From: Generic42
- Re: Schema errors when trying to update for 2003 R2
- Prev by Date: Re: ADAM custom password policy
- Next by Date: Re: Backing up GP's and DFS shares?
- Previous by thread: Re: Resubnetting without loosing reservations
- Next by thread: Re: Schema errors when trying to update for 2003 R2
- Index(es):
Relevant Pages
|
Loading