[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

MSExchangeDSAccess errors preventing installation of Exchange 2k3

Posted on 2006-04-26
10
Medium Priority
?
1,014 Views
Last Modified: 2008-03-06
We have a Win2k domain with 2 win2k DCs, both of which are GCs.  We have another server running win2k and exchange 2k enterprise edition.  I am trying to install a fourth machine with Win2k3 and Exchange 2k3 to migrate from the third machine, but MSExchangeDSAccess errors are preventing the new Exchange services from running.

I have verified the following:
Both Exchange machines point to DNS servers for DNS.  Both DNS servers point to themselves for DNS.
Both Exchange machines complete DCDIAG and NETDIAG successfully.
PolicyTest.exe verifies that Exchange Enterprise Servers have the correct permissions in the Default Domain Controllers Policy.
ForestPrep and DomainPrep completed successfully.

Here is what is weird:
The old Win2k exchange server works, but the following errors are regularly logged in the Application log:


Event Type:      Information      
Event Source:      MSExchangeDSAccess      
Event Category:      Topology       
Event ID:      2069      
Date:            4/26/2006
Time:            9:55:14 AM
User:            N/A
Computer:      MTMAIL      
Description:            
Process EMSMTA.EXE (PID=3644).  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.             



Event Type:      Information      
Event Source:      MSExchangeDSAccess      
Event Category:      Topology       
Event ID:      2077      
Date:            4/26/2006
Time:            9:55:14 AM
User:            N/A
Computer:      MTMAIL      
Description:            
Process EMSMTA.EXE (PID=3644).  DSAccess could not find any Domain Controller servers in neither the local site 'Default-First-Site-Name' nor the following sites:              
             

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


Both of these errors repeat for the STORE.EXE, EMSMTA.EXE and WINMGT.EXE executables.  Note that the list of sites is actually blank (we only have one site).  In the Exchange System Manager on this machine on the Directory Access Tab:
Domain Controllers populate from auto discovery, but I CANNOT select DCs, GCs, or Config DC, uncheck Auto Discovery, and manually add.  Always fails with: The server mtmain.moys.local does not exist or is not appropriately configured.  
Do you want this server removed from this list?

On the NEW Exchange box, In the Exchange System Manager on this machine on the Directory Access Tab:
Domain Controllers DO NOT populate from auto discovery, and I CANNOT select DCs, GCs, or Config DC, uncheck Auto Discovery, and manually add.  Always fails with: The server mtmain.moys.local does not exist or is not appropriately configured.  Do you want this server removed from this list?

And the app log shows:

Event Type:      Error      
Event Source:      MSExchangeDSAccess      
Event Category:      Topology       
Event ID:      2114      
Date:            4/26/2006
Time:            9:56:12 AM
User:            N/A
Computer:      MTMAILB      
Description:            
Process EXMGMT.EXE (PID=320). Topology Discovery failed, error 0x80040a02.             

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



Event Type:      Information      
Event Source:      MSExchangeDSAccess      
Event Category:      Topology       
Event ID:      2069      
Date:            4/26/2006
Time:            9:56:12 AM
User:            N/A
Computer:      MTMAILB      
Description:            
Process EXMGMT.EXE (PID=320).  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.            



Event Type:      Information      
Event Source:      MSExchangeDSAccess      
Event Category:      Topology       
Event ID:      2077      
Date:            4/26/2006
Time:            9:56:12 AM
User:            N/A
Computer:      MTMAILB      
Description:            
Process EXMGMT.EXE (PID=320).  DSAccess could not find any Domain Controller servers in neither the local site 'Default-First-Site-Name' nor the following sites:              
             

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

So, all problems seem to point to DNS/DC/GC problems, but they actually check out OK and the old one works.  Any ideas?
0
Comment
Question by:theblackrich
  • 5
  • 3
8 Comments
 
LVL 24

Expert Comment

by:flyguybob
ID: 16547763
Check your domain controller's settings in Active Directory Sites and Services and see if any of them are Global Catalogs (NTDS settings).  Also make sure that you have configured a subnet and assigned it to a site.
0
 
LVL 24

Expert Comment

by:flyguybob
ID: 16547778
This is for Windows 2000 Active Directory, but applies to Windows 2003.
http://support.microsoft.com/?kbid=269098
0
 

Author Comment

by:theblackrich
ID: 16548373
Both DCs are Global Catalog servers, and both of our subnets are included in the Defaul-First-Site-Name site.
0
Industry Leaders: 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!

 
LVL 24

Expert Comment

by:flyguybob
ID: 16548512
What was the role of MTMain?  If it was an Exchange server or an old domain controller, it may need cleaned out of Active directory (NTDSUtil and ADSIEdit).

Thanks,

Bob
0
 
LVL 24

Expert Comment

by:flyguybob
ID: 16548548
One thing I would recommend is to uncheck the GC role from one of the DCs, click Apply, OK, and then reboot.  Once it is back up, make it a GC.  Look in the Active Directory event logs for the GC announcement (1129 or 1149 if memory serves me correctly).

Regarding cleaning out a DC:
http://support.microsoft.com/kb/216498

Removing an Exchange server with ADSIEdit (very brief overview)
http://www.msexchange.org/tutorials/Remove-Exchange-server-entire-Exchange-organization.html


0
 

Author Comment

by:theblackrich
ID: 16554078
MTMAIN is a DC on the same subnet as both Exchange boxes.

I unchecked the GC role from the other DC and rebooted, and then re-applied the role and a short while later the informational 1119 message ws logged in the Directory Service log.

Event Type:      Information
Event Source:      NTDS General
Event Category:      Replication
Event ID:      1119
Date:            4/26/2006
Time:            7:20:41 PM
User:            Everyone
Computer:      MTOHIO
Description:
This Windows Domain Controller is now a Global Catalog server.
0
 
LVL 24

Accepted Solution

by:
flyguybob earned 2000 total points
ID: 16554729
After the 1119 (thanks for the note), reboot the Global Catalog server.

After re-reading the article I think you may have a DNS Island issue if MTMain is pointing to itself for primary DNS name resolution.
Please see the two KB articles below.
http://support.microsoft.com/kb/275278/en-us
http://support.microsoft.com/kb/291382

In Windows 2000, I point a DC to a partner DC first and then to itself second in the DNS server search order.  If there are more than 2 DCs in a site, then I point to it last in the Server Search order.

Bob
0
 

Author Comment

by:theblackrich
ID: 16737363
dsacls "cn=sites, cn=configuration,DC=mydomain,DC=local" /S /T
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
In this post, I will showcase the steps for how to create groups in Office 365. Office 365 groups allow for ease of flexibility and collaboration between staff members.
This video discusses moving either the default database or any database to a new volume.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Suggested Courses

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question