toolguy99
asked on
Error extending Schema from 2000 to 2008 due to exchange
I'm currently trying to upgrade our network from server 2000 to server 2008. I currently have one server that functions as the domain controller and also hosts exchange server 2000. when i try running forestprep I was greeted with the error "Adprep was unable to extend the schema.
[Status/Consequence]
There is a schema conflict with Exchange 2000. The schema is not upgraded.
[User Action]
The schema conflict must be resolved before running adprep. Resolve the schema c
onflict, allow the change to replicate between all replication partners, and the
n run Adprep. For information on resolving the conflict, see Microsoft Knowledge
Base article Q325379."
I followed the steps in the KB particularly scenario 2 , however while trying to run the inetorgpersonprevent.ldf file I get the following error
"Connecting to "servername".
Logging in as current user using SSPI
Importing directory from file "inetorgpersonprevent.ldf"
Error occured during initialization
File operation failure
0 entries modified successfully.
An error has occurred in the program"
Here's what i have in the inetorgpersonprevent.ldf file
dn: CN=ms-Exch-Assistant-Name, CN=Schema, CN=Configu ration,DC= X
changetype: Modify
replace:LDAPDisplayName
LDAPDisplayName: msExchAssistantName
-
dn: CN=ms-Exch-LabeledURI,CN=S chema,CN=C onfigurati on,DC=X
changetype: Modify
replace: LDAPDisplayName
LDAPDisplayName: msExchLabeledURI
-
dn: CN=ms-Exch-House-Identifie r,CN=Schem a,CN=Confi guration,D C=X
changetype: Modify
replace: LDAPDisplayName
LDAPDisplayName: msExchHouseIdentifier
-
dn:
changetype: Modify
add: schemaUpdateNow
schemaUpdateNow: 1
-
I've checked to make sure that there are no white spaces and there is an extra line after the last "-".
The file is saved as a Unicode File.
I have no errors when I run DCDiag.
No errors show in the Event Viewer
[Status/Consequence]
There is a schema conflict with Exchange 2000. The schema is not upgraded.
[User Action]
The schema conflict must be resolved before running adprep. Resolve the schema c
onflict, allow the change to replicate between all replication partners, and the
n run Adprep. For information on resolving the conflict, see Microsoft Knowledge
Base article Q325379."
I followed the steps in the KB particularly scenario 2 , however while trying to run the inetorgpersonprevent.ldf file I get the following error
"Connecting to "servername".
Logging in as current user using SSPI
Importing directory from file "inetorgpersonprevent.ldf"
Error occured during initialization
File operation failure
0 entries modified successfully.
An error has occurred in the program"
Here's what i have in the inetorgpersonprevent.ldf file
dn: CN=ms-Exch-Assistant-Name,
changetype: Modify
replace:LDAPDisplayName
LDAPDisplayName: msExchAssistantName
-
dn: CN=ms-Exch-LabeledURI,CN=S
changetype: Modify
replace: LDAPDisplayName
LDAPDisplayName: msExchLabeledURI
-
dn: CN=ms-Exch-House-Identifie
changetype: Modify
replace: LDAPDisplayName
LDAPDisplayName: msExchHouseIdentifier
-
dn:
changetype: Modify
add: schemaUpdateNow
schemaUpdateNow: 1
-
I've checked to make sure that there are no white spaces and there is an extra line after the last "-".
The file is saved as a Unicode File.
I have no errors when I run DCDiag.
No errors show in the Event Viewer
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Firstly you have to get your Exchange Upgraded then AD as backward compatibility does not works fine always ..... and many issues with Windows 2000 and Windows 2008 ..... when both are DC's as Windows 2008 has communication issues with Windows 2000 and also many GPP and other issues
Make sure you are in the My Documents directory when running the file. When in command prompt type dir and ensure that the file is listed.
ASKER
I had missed the part about logging into the schema master and was trying to perform this on the Exchange server, that is also a DC, but not the master. Also, I hadn't modified the registry to allow for updates on the master.