Consider the following scenario:
You use Microsoft Exchange Troubleshooting Assistant (Extra.exe) to troubleshoot a Microsoft Exchange Server 2010 server.
You use Exchange Troubleshooting Assistant to request traces and to collect diagnostic information.
The ADProvider trace component and the ClientThrottlingState trace tag are selected in the tracing.
You run a command in Exchange Management Shell (EMS), or you perform an operation in Exchange Management Console (EMC). For example, you run the Get-Mailbox command.
In this scenario, you receive the following error message in EMS or in a pop-up window from EMC:
Processing data from remote server failed with the following error message: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OperationStopped: (System.Manageme...pressionSyncJob:PSInvokeExpressionSyncJob) , PSRemotingTransportException
+ FullyQualifiedErrorId : JobFailure
This problem occurs because the ClientThrottlingState trace tag is enabled. When this trace tag is enabled and when a command is run, the PowerShell application pool crashes and then restarts.
To resolve this problem, install the update rollup that is described in the following Microsoft Knowledge Base article:
982639 Description of Update Rollup 4 for Exchange Server 2010
To work around this problem, disable the ADProvider tag and the ClientThrottlingState tag. Or, leave the tags enabled and then clear the Debug trace type. To do this, follow these steps:
Click Start, and then click Run.
Type C:\Program Files\Microsoft\Exchange Server\V14\Bin\extra.exe in the Open field, and then click OK.
Click Go to the Welcome screen, and then click Select a Task.
Click Trace Control, and then click OK.
Click Set manual trace tags.
On the next page, click ADProvider under the Components to Trace tab, and then clear the ClientThrottlingState check box under the Trace Tags tab. Or, clear the Debug check box.
Click Start Tracing, and then click Stop tracing now.
Even after you stop tracing and disable the tag, this problem may persist for a time. This problem persists if the Debug TraceLevel property is contained in the ADProvider:ClientThrottlingState tag in the EnabledTraces.Config file. If you continue to experience this problem, rename or delete the EnabledTraces.Config file on the System drive (drive C).
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.