Exchange 2003 Install cannot find schema master

Have 3 servers running windows 2003. The server i"m installing exchange on has passed the dcdiag test and the netdiag test. I've checked the RID, PID and infrastructure tabs to make sure it was on there and the check box for global catalog is checked so this server should be okay, but trying to run forestprep in exchange install says it can not talk to the schema master. What else should I check for?
sraleyAsked:
Who is Participating?
 
stronglineConnect With a Mentor Commented:
we seize role only when nobody claims to be the owner, or the original owner malfunction somehow and won't come back online for good.

I don't know what's prevent you from answering other questions

Are you the schema admin?
Did you set your schema master to accept updates?
http://support.microsoft.com/kb/285172
0
 
rakeshmiglaniCommented:
the server holding the  schema master role is up?
http://support.microsoft.com/kb/234790
0
 
stronglineCommented:
what exactly the error message is?

Are you the schema admin?
Did you set your schema master to accept updates?
Did you try to run forestprep from a different DC?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
sraleyAuthor Commented:
The server that is listed in the PID, RID and infrastructure tab is the one I'm putting exchange on, so yes its running.
0
 
sraleyAuthor Commented:
The error is that that exchange can not contact the schema master
0
 
sraleyAuthor Commented:
The exact message is: "failed to contact the schema master server for this active directory forest"
0
 
rakeshmiglaniCommented:
are all the FSMO roles held by the same server?
have you checked the server holding the schema master role?
0
 
sraleyAuthor Commented:
I've loaded the active directory schema and verified that server01 which is the one I'm putting exchange on is the schema master, I then went to server03 and ran it and it shows that server01 is the schema master. both are replicating ad and dns
0
 
sraleyAuthor Commented:
I reran dcdiag and just saw the test for KnowsOfRoleHolders says that it fails the test because server01 is the Rid Owner, but is deleted.  

I'm not sure aht that means since I'm running dcdiag on server01 and it is shown in AD as the RID, PID and Infrastructure operations master.
0
 
stronglineCommented:
we don't care who is RID, PID and Infrastructure (well we do but not for forestprep), we just need to know who is the schema master. And my 3 questions again:

Are you the schema admin?
Did you set your schema master to accept updates?
Did you try to run forestprep from a different DC?

run "netdom query fsmo" to find out.

If your dcdiag failed on KnowsOfRoleHolders, you have to solve it first, probably by seizing the role that nobody claims.
0
 
sraleyAuthor Commented:
how do I seize the role?
0
 
sraleyAuthor Commented:
netdom query says my machine is the schema owner and I got RID to change so my server is the owner of everything in the query results.
0
 
SembeeConnect With a Mentor Commented:
If you run netdom query fsmo and it shows any servers that are no longer alive, then you need to seize the roles.

http://support.microsoft.com/default.aspx?kbid=255504

Any other changes will be pointless if the roles are not held by active servers.

Simon.
0
 
sraleyAuthor Commented:
Finally did the seize the role and have exchange installed. I've renamed the mdbdata to mdbdata_orig and restored the mdbdata folder. Trying to do eseutil /p <path including priv1.edb>
eseutil /d <path including priv1.edb> on the files and get an error on priv1 stating:
operation terminated with error -1603 (jet_errnocurrentrecord, currency not on a record) after 6.62 seconds)

any ideas? I can't find this jet error on Microsoft.
0
 
stronglineCommented:
ok so you are trying to recover from something. Really better let us know from begining.
Did you install your exchange with same org/AG name and same location for MDBdata? With all above setting identical as your previous exchange, there is chance to bring the database back to consistant.
Did you make an extra copy before /p? If you don't, then really running /p again is your only option. /P is destructive and should be used as last resort.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.