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

x
?
Solved

Exchange 2010 Install problem

Posted on 2011-02-22
10
Medium Priority
?
2,668 Views
Last Modified: 2012-08-14
I am installing Exchange 2010 for the first time on a new domain (testing for a roll-out in 6 months).  I have run all of the prerequisite scripts, however am coming up with the following errors:
Summary: 4 item(s). 1 succeeded, 3 failed.
Elapsed time: 00:00:32


Languages Prerequisites
Completed

Elapsed Time: 00:00:12


Hub Transport Role Prerequisites
Failed

Error:
Setup encountered a problem while validating the state of Active Directory: Active Directory server DC-NAME.DOMAIN.TLDN is not available. Error message: A local error occurred.

Error:
Setup cannot continue because one or more SMTP/Send connectors have invalid settings: Active Directory server DC-NAME.DOMAIN.TLDN is not available. Error message: A local error occurred.

Elapsed Time: 00:00:07


Client Access Role Prerequisites
Failed

Error:
Setup encountered a problem while validating the state of Active Directory: Active Directory server DC-NAME.DOMAIN.TLDN is not available. Error message: A local error occurred.

Error:
The start mode for the Net.Tcp Port Sharing service must be set to Automatic before Setup can continue.

Elapsed Time: 00:00:06


Mailbox Role Prerequisites
Failed

Error:
Setup encountered a problem while validating the state of Active Directory: Active Directory server DC-NAME.DOMAIN.TLDN is not available. Error message: A local error occurred.

Elapsed Time: 00:00:06

I have double- and triple-checked all the steps in installing...  anyone run into this before?
0
Comment
Question by:brianpettyjohn
  • 6
  • 2
  • 2
10 Comments
 

Author Comment

by:brianpettyjohn
ID: 34957020
And I have checked to make sure the DC is running and reachable from the server to which I am attempting to install exchange.
0
 
LVL 3

Expert Comment

by:pitchford
ID: 34957218
Check your DNS settings. AD relies heavily on DNS. Make sure you can ping DOMAIN.TLDN as well as DC-NAME.DOMAIN.TLDN. Is your Exchange box also a domain controller?

I guess I should also step back and as, is the Exchange server a member of the domain? =) I'm going to assume it is.

If your DNS is good check this out:

It is caused by stored username/passwords (probably from browser sessions) that cause .NET's RPC interfaces to fail and has nothing to do with DNS.  Here is how to fix it without deleting admin profiles etc.

1. Click Start, click Run, type "control keymgr.dll" , and the click OK.
2. Delete any entry that matches the names of the Exchange servers or domain controllers in your organization.

If in doubt clear all entries present.


Best of luck!
0
 

Author Comment

by:brianpettyjohn
ID: 34957317
Yes, I can ping DOMAIN.TLDN as well as DC-NAME-DOMAIN.TLDN.  

I went through and checked cached credentials, still no-go.  Good tips, though.  Never thought of the keymgr
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
LVL 3

Expert Comment

by:pitchford
ID: 34957347
Check your FISMO roles. I'd have to assume that you have only 1 DC and it is the master for all 5.

Foregive me, I don't know your expertise with AD but if you need help: http://en.wikipedia.org/wiki/Active_Directory
0
 

Author Comment

by:brianpettyjohn
ID: 34957611
Checked all the roles.  Yes, I have only the 1 DC, it holds all the roles.  setup/ps completed successfully.  

One thing I am going to try is this:  These machines (VMs) were once a part of another domain (the template).  On the exchange server, I changed the machine from domain 1 to domain 2 (directly).  I am going to try and disjoin from domain 1, change to workgroup, then add to domain 2.  Will try in the morning.  Thank you for your help, I'll let you know the results.
0
 
LVL 31

Expert Comment

by:MegaNuk3
ID: 34958625
"The start mode for the Net.Tcp Port Sharing service must be set to Automatic" is it?
Reboot the server, after setting the above to automatic and try the install again.
0
 

Author Comment

by:brianpettyjohn
ID: 34960686
I saw the "The start mode for the Net.Tcp Port Sharing service must be set to Automatic"  message, changed the setting, rebooted, and it still failed (although that particular message didn't show up again).  Am beginning to work on this issue again this morning, by removing from the domain and re-adding.  Will post results shortly.
0
 

Accepted Solution

by:
brianpettyjohn earned 0 total points
ID: 34962073
Solved it.  I removed the new exchange server from the domain, and into a workgroup.  Rebooted.  Changed back to the new domain.  Rebooted.  Was then able to successfully install exchange from that point.

Thank you for all your help!
0
 
LVL 31

Expert Comment

by:MegaNuk3
ID: 34962721
Thanks for the solution
0
 

Author Closing Comment

by:brianpettyjohn
ID: 34995395
Began disecting the error messages.  Although the DC was reachable from the exchange computer, there seemed to be aproblem in AD reconciliation.  Therefore, i backed out of the domain and went back in.  SUCCESS!
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Question has a verified solution.

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

As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
Exchange administrators are always vigilant about Exchange crashes and disasters that are possible any time. It is quite essential to identify the symptoms of a possible Exchange issue and be prepared with a proper recovery plan. There are multiple…
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
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

834 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