On a recent upgrade from Exchange 2000, which has been operating smoothly, I am getting the following errors:From Management Console: get-ExchangeServer Error: Active Directory server <FQDN> is not available. Error message: A local error occurred get-UMServer Error: Active Directory server <FQDN> is not available. Error message: A local error occurredFrom Management Shell: "Exception setting 'ViewEntireForest': 'Active Directory server <FQDN> is not available. Error message: A local error occurred.' It then lists the program file path and "ViewEntireForest = $False"The System log shows no errors. The Application log has two warning errors, events 2161 and 2159, each indicating that a read from AD failed. I can click OK to move past the error in the Management Console. Using the Performance Trouibleshooter for connection testing succeeds and shows no problems.This is a simple install on a single domain. It was an upgrade from Exchange 2000 to 2007 on a different server. There were no significant problems with the install other than public folders not being transferred. I was going into the shell to resolve this issue but couldn't issue the commands because of this condition. Any help is appreciated.Thanks.Edit: The AD log shows no errors and I have tried restarting the Exchange services.

Hi,Please first post the two event logs on the forum in order to do a better troubleshooting.ThanksAllen

Thanks for your reply. After your reply I set the logging level for ADAccess\General, ADAccess\Configuration, and ADAccess\Topology to "high" (duh), but the two log entries below continue to be the only indications of a problem. If there are others that should be increased for testing let me know. Thanks.Event Type: WarningEvent Source: MSExchange ADAccessEvent Category: Validation Event ID: 2161Date: 1/15/2010Time: 7:26:28 AMUser: N/AComputer: ACTSDescription:Process edgetransport.exe (Transport) (PID=2264). Object CN=ACTS-GENESIS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Moravian,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=moravian,DC=local read from acts.moravian.local failed validation. Attribute: TargetTransportServerVsis. Error message: TargetTransportServerVsis is mandatory.. Invalid data: . Event Type: WarningEvent Source: MSExchange ADAccessEvent Category: Validation Event ID: 2159Date: 1/15/2010Time: 7:26:28 AMUser: N/AComputer: ACTSDescription:Process edgetransport.exe (Transport) (PID=2264). Configuration object CN=ACTS-GENESIS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Moravian,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=moravian,DC=local read from acts.moravian.local failed validation and will be excluded from the result set. Set event logging level for Validation category to Maximum to get additional events about each failure.

Event Type: WarningEvent Source: MSExchange ADAccessEvent Category: Validation Event ID: 2161Date: 1/15/2010Time: 7:26:28 AMUser: N/AComputer: ACTSDescription:Process edgetransport.exe (Transport) (PID=2264). Object CN=ACTS-GENESIS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Moravian,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=moravian,DC=local read from acts.moravian.local failed validation. Attribute: TargetTransportServerVsis. Error message: TargetTransportServerVsis is mandatory.. Invalid data: . Event Type: WarningEvent Source: MSExchange ADAccessEvent Category: Validation Event ID: 2159Date: 1/15/2010Time: 7:26:28 AMUser: N/AComputer: ACTSDescription:Process edgetransport.exe (Transport) (PID=2264). Configuration object CN=ACTS-GENESIS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Moravian,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=moravian,DC=local read from acts.moravian.local failed validation and will be excluded from the result set. Set event logging level for Validation category to Maximum to get additional events about each failure. I have highlighted the process which gives the error. So, this means that the edge transport (CAS) is the one being the one responsible for this.The issue seems to be with the routing group connector.Navigate to: CN=1, CN=SMTP, CN=PROTOCOLS, CN=Exchange server, CN=Servers, CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Moravian,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=moravian,DC=local.Copy the distinguished name (DN) of that attribute.Now go to:CN=ACTS-GENESIS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Moravian,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=moravian,DC=local | Using ADSIEDIT. Look for the attribute msExchTargetBridgeHeadServerDN value from the properties.Paste the DN that we copied already and restart the Microsoft Exchange Transport service.All the best :)- Nagesh

Event Type: WarningEvent Source: MSExchange ADAccessEvent Category: Validation Event ID: 2161Date: 1/15/2010Time: 7:26:28 AMUser: N/AComputer: ACTSDescription:Process edgetransport.exe (Transport) (PID=2264). Object CN=ACTS-GENESIS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Moravian,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=moravian,DC=local read from acts.moravian.local failed validation. Attribute: TargetTransportServerVsis. Error message: TargetTransportServerVsis is mandatory.. Invalid data: . Event Type: WarningEvent Source: MSExchange ADAccessEvent Category: Validation Event ID: 2159Date: 1/15/2010Time: 7:26:28 AMUser: N/AComputer: ACTSDescription:Process edgetransport.exe (Transport) (PID=2264). Configuration object CN=ACTS-GENESIS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Moravian,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=moravian,DC=local read from acts.moravian.local failed validation and will be excluded from the result set. Set event logging level for Validation category to Maximum to get additional events about each failure. I have highlighted the process which gives the error. So, this means that the edge transport (CAS) is the one being the one responsible for this.The issue seems to be with the routing group connector.Navigate to: CN=1, CN=SMTP, CN=PROTOCOLS, CN=Exchange server, CN=Servers, CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Moravian,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=moravian,DC=local.Copy the distinguished name (DN) of that attribute.Now go to:CN=ACTS-GENESIS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Moravian,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=moravian,DC=local | Using ADSIEDIT. Look for the attribute msExchTargetBridgeHeadServerDN value from the properties.Paste the DN that we copied already and restart the Microsoft Exchange Transport service.All the best :) - Nagesh Thank you for your reply. Sorry, I've been out sick for a week and just yesterday tried your solution. It made to difference. A couple of other items for you consideration... As I said in my original message, this is a simple install on a single server in a single domain. There is no Edge Transport. I used the "transition" process per the relevant KB articles for moving from Exchange 2000 to Exchange 2007 on a different server. These errors did not occur until the old server was removed from the domain. The current server name is "Acts." The previous server was "Genesis". I'm not sure why there is a CN=ACTS-GENESIS.Thanks in advance to anyone who has other ideas.

I also upgraded from Exchagne 2000 to 2007 and I had or at least have the same problem and I think I managed to resolve it.The clue is in both events, which you have to read back wards and apply it to ADSIEDIT from a domain controller, which in your case is acts.moravian.local.CN=ACTS-GENESIS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Moravian,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=moravian,DC=local Which translates in ADSIEDIT to:Configuration (moravian.local)CN=ServicesCN=Microsoft ExchangeCN=MoravianCN=Administrative GroupsCN=Exchange Administrative Group (FYDIBOHF23SPDLT)CN=Routing GroupsCN=Exchange Routing Group (DWBGZMFD01QNBJR)CN=ConnectionsCN=ACTS-GENESISAs CN=ACTS-GENESIS refers to your old Exchange 2000 server, I guessed that it should be deleted.I'm going to monitor the event log tomorrow to see if I've managed to solve it.