Exchange 2007 - PrepareSchema Failing

This may have been asked elsewhere, but I can't find any solutions to where someone was running only one domain controller.  I was doing my prep work getting prepared to install Exchange 2007 (transition from Exchange 2003).  I have already ran the command sucessfully.  When I run the, I receive the following error message:

Extending Active Directory schema.......................FAILED
An error occurred when executing 'ldifde.exe' to import schema file 'E:\Setup\ServerRoles\Common\Setup\Data\PostExchange2003_schema0.ldf'.  Error code: 8206.  More details can be found in the rror file 'C:\Documents and Settings\Administrator.DOMAIN\Local Settings\Temp\2\ldif.err.

When looking at the error file in the Temp directory, I get the following:

Connecting to ""
Logging in as current user using SSPI
Importing directory from file "E:\Setup\ServerRoles\Common\Setup\Data\PostExchange2003_schema0.ldf"
Loading entries
1: CN=ms-Exch-ELC-Expiry-Action,CN=Schema,CN=Configuration,DC=cayefurniture,DC=com
Entry DN: CN=ms-Exch-ELC-Expiry-Action,CN=Schema,CN=Configuration,DC=cayefurniture,DC=com
Add error on line 1: Busy
The server side error is "The FSMO role ownership could not be verified because its directory partition has not replicated successfully with atleast one replication partner."
0 entries modified successfully.
An error has occurred in the program

I have been reading about this being a replication problem, however, we only have one domain controller.  

Also to note, I have already installed the following on the x64 Exchange server:
.NET Framework 2.0; .NET Framework 2.0 SP1; Powershell

Also, I have done the following:
Exchange 2003 organization is Native Mode
Exchange 2003 Server running SP2
Active Directory functional level has been raised to Windows 2000 native

Any ideas of what I should do?  Surely there wouldn't be any problem in installing Exchange 2007 when you are only running 1 domain controller would there?
If I need to provide any further information, please let me know.  Thanks.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sounds like you once had another DC in there somewhere and it was not gracefully removed. Would this be the case?

Exchange 2007 can definitely be installed when there's only a single domain controller.  I am guessing your problem is due to some old entries in AD for domain controllers.  i.e.  Exchange thinks there are multiple domain controllers.

Have you run replmon on the domain controller?  What about dcdiag?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
To check this go to AD Sites and Services, expand sites, then expand servers and see what listed there.

As a side note, you should really think of putting in a second DC. The domain will go down if that one crashes.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

david_greerAuthor Commented:
Ok.  I went to AD Sites and Services, and we actually have 2 servers listed.  
I also ran DCDiag on the domain controller.............I have attached the results of that scan to this message.

Also to note, I ran replmon, and am getting the following messages:

>>Direct Replication Partner Data<<
Server is current through Property Update USN: 118847
Replication Failure: Changes have not been successfully replicated from BACKUP for 10929 attempts
Replication Failure: The reason is: There are no more endpoints available from the endpoint mapper
Replication Failure: The last replication attempt was: 3/27/2009 3:54:13 PM (local)

I'm not sure what is happening.  Since I've been with the company, I have only been aware of one domain might be possible that the guy before me had done something with the BACKUP server.
run the following command on your domain controller to see what roles it is running.

netdom query fsmo

It shouldn't list any roles as being on the server called "BACKUP", or else you'd be having lots of other issues in Active Directory.  But I'd check just in case.

Here is an article from MS that explains how to transfer any roles to the correct domain controller:

Once all roles are transferred, you can just select the server "BACKUP" as it shows up in AD sites and services and delete it.
david_greerAuthor Commented:
Ok, after running the netdom query fsmo command, I received the following:
Schema Owner......nadc
Domain Role Owner......nadc
PDC Role..........nadc
Rid Pool Manager..........nadc
Infrastructure Owner.......nadc

So it looks like all roles are currently on the nadc server.  I'm not sure exactly why the Backup server is showing up in Sites and Services.

So, now I would be okay to delete the BACKUP server from Sites and Services, and that would auto correct my replication problem?
yes, that should work.

If it still gives you errors, you may need to go into adsiedit.  But I think that'll work.
david_greerAuthor Commented:
Ok, when I went into AD Sites and Services and tried to delete the BACKUP Server, I received the following error message:

Do not delete the BACKUP container object.  BACKUP contains objects representing domain controller BACKUP and possibly other domain controllers.  To delete these objects, demote the domain controllers using the Active Directory Installation Wizard (DCPROMO).  If the domain controllers represented by these objects are permanently offline and can no longer be demoted using the Active Directory Installation Wizard (DCPROMO), you must delete them one at a time.
I'm affraid your going to need to ru through this - it's not at difficult as it looks.

Basically is loading ADSIEDIT and cleaning out that domain controller from your AD metadata manually. Once that is done you'll have no more issues.
david_greerAuthor Commented:
Ok, I have read through this Microsoft article, but have concern regarding one of the steps.  On step 18, it is instructing to delete the A record (BACKUP) from DNS.  However, I do not need to delete this A record, as we will still have our BACKUP server online for backup functions.

Also, I'm vary wary of that beginning WARNING message at the top of the article, as we only have that one domain controller.  Is this anything to be very concerned about?

Any insight is greatly appreciated.
You may want to consider logging onto the server called "backup" to see if it thinks it is still a domain controller (just go to control panel->system->computer name and see if the whole window is grayed out.  If so, that means BACKUP still thinks it's a domain controller, and you'd probably be better off trying to get replication working again before doing anything with Exchange.

If it DOESN'T gray out that computer name window, then most likely you're already running a single domain controller setup and you should proceed with the MS instruction to remove references to BACKUP.  You don't need to have it remove the A record though.
david_greerAuthor Commented:
This worked beautifully guys.  As soon as ntdsutil ran and cleaned up all of the scattered pieces, prepareschema (as well as all of the other switches) completed 100%.  

One more question before I close this that I have done all of the prep work, I am now ready for the actual install of Exchange 2007.  Since we have another Exchange server (03) currently running on the network, if I continue with this install, is there anything at all that could interrupt service to our email?  I wanted to go ahead with the install, but wasn't sure if I needed to wait until the weekend when there were no users here to actually install 07.  Will there be any kind of services or email routing problems at all if I went ahead with the install?
You shouldn't have any problems.  Just make sure you create a send connector on the Exchange 2007 server, specify an address space of *.  That will allow it to send outgoing emails to the internet.  Otherwise once the 2003 server goes away, outgoing email will stop.
Sorry, just to clarify my previous post.  This would be done under organization configuration->Hub Transport->Send Connectors.
david_greerAuthor Commented:
Thanks for the reply esmith.  But as long as I keep the Exchange 2003 server up and running in our infrastructure, we should be okay to go ahead and install 07, correct?  Would I need to create this send connector on 07 as soon as I installed?

Sorry to sound so paranoid on this, but email is a very critical aspect of our operations, and I wanted to make absolutely 100% sure that if I went ahead and installed 07, that that wouldn't affect our email flow internally and externally at all.  I did notice that during the prep switches, it created a routing connector on our Exchange 2003 server.

Sorry for the delay - been away a while. Glad you got your AD sorted, that article is a bit scary but it's microsoft covering their rears.
As for exchange - it will be fine. Your 2003 install should not be affected at all. The Exchange 2007 installers are very intelligent and will recognise the 2003 intall and create all relevant connectors etc. The worst that may happen is that the exchange 2007 server won't be able to send/recieve mail but that's what test accounts are for.
Of course there's still no excuse not to take a full backup of your AD and Exchange server before you start work! ;)
Also, i would usually do this kind of work out of hours just in case.
Also, i still stand by my earlier point - build another DC ASAP.
Don't know if you've ever had to restore AD but believe me, if you were concerned about that article, have a read through the AD restore articles.
Correct.  The send connector gets created on the Exchange 2007 server after the Exchange setup program completes.

You may want to check out this MS article that describes how to remove a 2003 Exchange server from an Exchange 2007 environment.  It details several key steps to take before taking the 2003 server offline (such as creating a new public folder hierarchy, and moving all public folder replicas):

david_greerAuthor Commented:
Thanks so much again to you both.  You both have been a tremendous help to me in solving this issue of prepping for Exchange 2007.  You both were so helpful, I had to split the esmith69 for pointing me to replmon and dcdiag to realize that I was having unsucessful replication to a (dead) DC, and to Share-IT for pointing me to that great MS KB article for cleaning up the metadata.  Also, thanks to you both for the great advice regarding having Exchange 2007 in a coexistence state with 03.
Thanks again.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.