Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 788
  • Last Modified:

Upgraded Domain Controller from 2000 to 2003 and now Exchange 2003 won't start

After upgrading my Domain Controller from Windows 2000 Small Business Server to 2003.  Before doing so I made my Exchange Server a domain controller to ensure Active Directory was saved since you cannot upgrade SBS to 2003 Enterprise.  I had to do a fresh install.

Now System Attendant won't start on the Exchange Server.  Here's what errors I'm getting.

Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      General
Event ID:      1005
Date:            5/5/2006
Time:            9:08:07 PM
User:            N/A
Computer:      EQUALITYSRV
Description:
Unexpected error The specified domain either does not exist or could not be contacted. Facility: Win32 ID no: c007054b Microsoft Exchange System Attendant  occurred.

For more information, click http://www.microsoft.com/contentredirect.asp.

And


Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      Monitoring
Event ID:      9098
Date:            5/5/2006
Time:            9:08:13 PM
User:            N/A
Computer:      EQUALITYSRV
Description:
The MAD Monitoring thread was unable to read its configuration from the DS, error '0x80010002'.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2114
Date:            5/5/2006
Time:            9:43:17 PM
User:            N/A
Computer:      EQUALITYSRV
Description:
Process INETINFO.EXE (PID=296). Topology Discovery failed, error 0x80040a02.

For more information, click http://www.microsoft.com/contentredirect.asp.

Also, I'm getting Information errors every 5 or so minutes

Event Type:      Information
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2069
Date:            5/5/2006
Time:            9:48:48 PM
User:            N/A
Computer:      EQUALITYSRV
Description:
Process INETINFO.EXE (PID=296).  DSAccess could not find any Global Catalog servers in neither the local site 'Default-First-Site-Name' nor the following sites:  
 

For more information, click http://www.microsoft.com/contentredirect.asp.


I tried removing the old server name from the Domain list and then readding it but that didn't help.

0
looknow12
Asked:
looknow12
  • 3
  • 3
1 Solution
 
Rant32Commented:
<< I made my Exchange Server a domain controller >>

This also requires the domain controller to be a global catalog server.

Please check in the AD Sites & Services snap in, open the Properties of "NTDS Settings" underneath the Exchange server computer object, and make sure that the Global Catalog checkbox is enabled.

https://www.microsoft.com/technet/prodtechnol/exchange/Analyzer/7423376e-686b-4cda-b90f-cf5cff4f8981.mspx?mfr=true
"If Exchange Server is running on a domain controller, you must also make that domain controller a global catalog server."
0
 
looknow12Author Commented:
Yes, but since I removed the exchange server as a domain controller.  I wish to add certificate services and have RPC over HTTP so according to MS, the Exchange Server cannot be a domain controller.  I ran DCPROMO and removed it as a Domain and did not check this is the last server in the Domain.
0
 
looknow12Author Commented:
I did however find the newly upgraded Domain Server and went to NTDS Settings and noticed it was not checked as a Global Catalog.  Should it be?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Rant32Commented:
You *must not* change the role of the server after installing Exchange server on it. Don't run DCPROMO on the Exchange server to change the domain controller role (either way).

<< newly upgraded Domain Server and went to NTDS Settings and noticed it was not checked as a Global Catalog.  Should it be? >>
A Global Catalog is essential to user authentication and Exchange operation so you always need to have at least one GC and preferably two available in the domain. That's not possible with SBS but it is with other versions of Windows.

If Exchange Server is installed on a Domain Controller, then it *will always use itself as a DC/GC*. Exchange server will NOT locate and use other domain controllers if installed on a DC. That's why Exchange breaks if you remove the DC role from an Exchange server.

For references to all of these, read http://www.xosoft.com/products/Why_not_to_run_Exchange_Server_2003_on_Domain_Controller.doc (Word document)

I don't know if re-promoting the Exchange box will solve your problems. I think you need to re-install Exchange Server. Then I must recommend you do some homework regarding installation and migration of Windows and Exchange because this is not the way to do it.
0
 
looknow12Author Commented:
RANT32 got me looking in the right area.  The Exchange Server is not to be a Domain Controller, however I noticed there were no domain servers that were checked as Global Catalogs.  How that happened I'm not sure.  After doing that and restarting the Exchange Server the Exchange Services became operational.
0
 
Rant32Commented:
Thanks for the feedback and the reward.
0

Featured Post

Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now