adding 2003 to 2000 domain , ERROR: Failed to transfer the schema FSMO role: 52

[MasterCheef]

I have a small windows 2000 AD network, 1 DC configured as
DNS as well.
Now I am trying to add a windows 2003 server to the domain.
I have done all the prereqs, but when I run
adprep/forestprep on the DC windows 2000 sever to update
the schema. It stops and gives me the following error.

------Error starts here -----------------------------------
Opened Connection to NTSERVER
SSPI Bind succeeded
Current Schema Version is 13
Upgrading schema to version 30
ERROR: Failed to transfer the schema FSMO role: 52
(Unavailable).

If the error code is "Insufficient Rights", make sure you
are logged in as a mem
ber of the schema admin group.
Adprep was unable to upgrade the schema on the schema
master.
[Status/Consequence]
The schema will not be restored to its original state.
[User Action]
Check the Ldif.err log file in the C:\WINNT\system32
\debug\adprep\logs\200407191
04355 directory for detailed information.



Adprep was unable to update forest-wide information.
[Status/Consequence]
Adprep requires access to existing forest-wide information
from the schema maste
r in order to complete this operation.
[User Action]
Check the log file, Adprep.log, in the C:\WINNT\system32
\debug\adprep\logs\20040
719104355 directory for more information.
-----------Error End here ---------------------------------

I would appreciate all the help.

Thank you

Mastercheef

 

[Cary Shultz [A.D. MVP]]

Are you running the adprep switches while using an account that is a member
of the Schema Admins? By default, the Administrator account is a member of
the Administrators built-in, Domain Admins, Enterprise Admins and Schema
Admins.

I might also check to see if the FSMO roles are available. You can install
the Support Tools and use netdom to see. You would simply enter - at a
command prompt - netdom query fsmo. You could also use replmon.

HTH,

Cary

 

[MasterCheef]

Cary,
Thanks for your response.
I have been searching the net for this issue, I found one
of the suggested solution that having an orphaned DC can
cause this issue.
http://www.winnetmag.com/forums/rd.cfm?cid=54&tid=59969
and I do have a orpaned DC that needs to be deleted from
active directory, everyone suggests using ASDI edit tool.
I have ADSI edit tool installed but I am not exactly sure
what entires to delete for the old DC.
As I have never used this tool before.
If you have a good idea could you inform me on what exact
entries to delete for the old DC.
In this article they mention some entries but there are
way more entries for the old DC.

I would appreciate, if you can give an idea on what exact
entries to delete.
I am trying one thing at a time to eliminate the problem.

thanks
Mastercheef

-----Original Message-----
Are you running the adprep switches while using an account that is a member
of the Schema Admins? By default, the Administrator account is a member of
the Administrators built-in, Domain Admins, Enterprise Admins and Schema
Admins.

I might also check to see if the FSMO roles are available. You can install
the Support Tools and use netdom to see. You would simply enter - at a
command prompt - netdom query fsmo. You could also use replmon.

HTH,

Cary

I have a small windows 2000 AD network, 1 DC configured as
DNS as well.
Now I am trying to add a windows 2003 server to the domain.
I have done all the prereqs, but when I run
adprep/forestprep on the DC windows 2000 sever to update
the schema. It stops and gives me the following error.

------Error starts here -------------------------------- ---
Opened Connection to NTSERVER
SSPI Bind succeeded
Current Schema Version is 13
Upgrading schema to version 30
ERROR: Failed to transfer the schema FSMO role: 52
(Unavailable).

If the error code is "Insufficient Rights", make sure you
are logged in as a mem
ber of the schema admin group.
Adprep was unable to upgrade the schema on the schema
master.
[Status/Consequence]
The schema will not be restored to its original state.
[User Action]
Check the Ldif.err log file in the C:\WINNT\system32
\debug\adprep\logs\200407191
04355 directory for detailed information.



Adprep was unable to update forest-wide information.
[Status/Consequence]
Adprep requires access to existing forest-wide information
from the schema maste
r in order to complete this operation.
[User Action]
Check the log file, Adprep.log, in the C:\WINNT\system32
\debug\adprep\logs\20040
719104355 directory for more information.
-----------Error End here ------------------------------ ---

I would appreciate all the help.

Thank you

Mastercheef

.

 

[Cary Shultz [A.D. MVP]]

MasterCheef,

I would suggest that you install the Support Tools onto all of your existing
WIN2000 Servers. For resolving this issue I might start out by simply
installing it on all of your WIN2000 Domain Controllers. BTW - how many
Domain Controllers do you have?

I would also run dcdaig /c /v and netdiag /v on all of your WIN2000 Domain
Controllers. Let's see what is going on there. I would also take a look at
repadmin /showconn and repadmin /showreps. We need to find out what Domain
Controller is still there - but really isn't. These tools - all available
after you install the Support Tools - will help. The Support Tools are
located on the WIN2000 Server CD or the WIN2000 Service Pack CD in the
Support | Tools folder. You can also download it from the MS web site. I
would opt for either the download or the Service Pack CD....

I would also take a look at ntdsutil. This is actually the tool that you
would use first to remove an orphaned Domain Controller. Then, after you
have done that, you would go into DNS and make sure that this has been
cleaned up and then go into Active Directory Sites and Services MMC ( you
could also go in there right in the beginning to see if the orphaned DC
still shows up in there ) to make sure that it is gone from there and then
you could use ADSIEdit....

Here is a link on how to use ntdsutil ( available out of the box with
WIN2000 Server ):

http://support.microsoft.com/?id=216498

This should make things very clear for you....

A tip: when you connect to a Domain Controller you need to connect to an
existing Domain Controller, not to the one that you are trying to remove.
This is a common mistake that a lot of people make. You will get an error
message if you do connect to the one that you are trying to remove.

HTH,

Cary

Cary,
Thanks for your response.
I have been searching the net for this issue, I found one
of the suggested solution that having an orphaned DC can
cause this issue.
http://www.winnetmag.com/forums/rd.cfm?cid=54&tid=59969
and I do have a orpaned DC that needs to be deleted from
active directory, everyone suggests using ASDI edit tool.
I have ADSI edit tool installed but I am not exactly sure
what entires to delete for the old DC.
As I have never used this tool before.
If you have a good idea could you inform me on what exact
entries to delete for the old DC.
In this article they mention some entries but there are
way more entries for the old DC.

I would appreciate, if you can give an idea on what exact
entries to delete.
I am trying one thing at a time to eliminate the problem.

thanks
Mastercheef

-----Original Message-----
Are you running the adprep switches while using an account that is a member
of the Schema Admins? By default, the Administrator account is a member of
the Administrators built-in, Domain Admins, Enterprise Admins and Schema
Admins.

I might also check to see if the FSMO roles are available. You can install
the Support Tools and use netdom to see. You would simply enter - at a
command prompt - netdom query fsmo. You could also use replmon.

HTH,

Cary

I have a small windows 2000 AD network, 1 DC configured as
DNS as well.
Now I am trying to add a windows 2003 server to the domain.
I have done all the prereqs, but when I run
adprep/forestprep on the DC windows 2000 sever to update
the schema. It stops and gives me the following error.

------Error starts here -------------------------------- ---
Opened Connection to NTSERVER
SSPI Bind succeeded
Current Schema Version is 13
Upgrading schema to version 30
ERROR: Failed to transfer the schema FSMO role: 52
(Unavailable).

If the error code is "Insufficient Rights", make sure you
are logged in as a mem
ber of the schema admin group.
Adprep was unable to upgrade the schema on the schema
master.
[Status/Consequence]
The schema will not be restored to its original state.
[User Action]
Check the Ldif.err log file in the C:\WINNT\system32
\debug\adprep\logs\200407191
04355 directory for detailed information.



Adprep was unable to update forest-wide information.
[Status/Consequence]
Adprep requires access to existing forest-wide information
from the schema maste
r in order to complete this operation.
[User Action]
Check the log file, Adprep.log, in the C:\WINNT\system32
\debug\adprep\logs\20040
719104355 directory for more information.
-----------Error End here ------------------------------ ---

I would appreciate all the help.

Thank you

Mastercheef

.