Troubleshooting and Limitations – Microsoft Exchange Server by PowerShell Discovery

This section describes troubleshooting and limitations for Microsoft Exchange Server by PowerShell discovery.

• Problem: No results brought, cmdlet calls end with errors like:

  Active Directory error 0x80072020 occurred while searching for domain controllers in domain <Domain Name>: An operations error occurred.

  +CategoryInfo :

  +FullyQualifiedErrorId : 7D2B0C9D

  Reason: The "Delegation" is not configured properly.

  Solution: Configure Active Directory "Delegation" as described in How to Configure the Active Directory Side.

• Problem: No results brought, cmdlet calls end with errors like:

  Value cannot be null..

  Parameter name: parameters

  + CategoryInfo :

  + FullyQualifiedErrorId : System.ArgumentNullException,Microsoft.Exchange.Management.
  SystemConfigurationTasks.GetExchangeServer

  Reason: The "Delegation" is not configured properly or connection is performed from an untrusted domain or not all required patches are installed on the server (for more details, see the official Microsoft site).

  Solution: Configure Active Directory "Delegation" as described in How to Configure the Active Directory Side, and check the patch-level. For more information, check the official Microsoft site.

• Problem: Calls to the Exchange command-lets fail with timeouts and/or session gets broken.

  An application cannot impersonate a user and then run Windows PowerShell commands in an Exchange Server 2007 environment.

  Reason: This is a known Exchange 2007 bug.

  Solution: To fix this problem, run Microsoft Patch KB943937, which is a part of MS Exchange 2007 SP1. For more information, see the Microsoft Patch description (http://support.microsoft.com/kb/943937).