Article ID: 2294243 - Last Review: August 26, 2010 - Revision: 1.0

WinRM times out and you receive an error message when you try to add a Mailbox server to an existing DAG

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Expand all | Collapse all

SYMPTOMS

When you try to add a new Microsoft Exchange Server 2010 Mailbox server to an existing Database Availability Group (DAG), the operation times out when it tries to install the Failover Clustering component. Additionally, you receive the following status message:
The task is installing the Windows Failover Cluster component on the server <SERVERNAME>.
When the time-out occurs, you receive the following error message:
Processing data for a remote command failed with the following error message: The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about_Remote_Troubleshooting Help topic.

+ CategoryInfo : OperationStopped: (System.Manageme...pressionSyncJob:PSInvokeExpressionSyncJob) [], PSRemotingTransportException

+ FullyQualifiedErrorId : JobFailure
However, the installation of the Failover Clustering component continues and succeeds after several minutes. If you run the Add-DatabaseAvailabilityGroupServer task again, the task finishes successfully.
Back to the top

CAUSE

When the Add-DatabaseAvailabilityGroupServer task runs, Exchange checks whether the target server already has the Failover Clustering component installed. If the Failover Clustering component is not installed, Exchange starts the installation of this component. During this process, the Microsoft Failover Cluster Virtual Driver (netft.sys) is also installed.

If Symantec Endpoint Protection is running on this computer, a driver that is named Teefer2 Miniport (teefer2.sys) is also installed. The installation of this third-party driver causes the network connection to drop out for a few minutes. This outage causes the connection between PowerShell.exe and the PowerShell application pool in Internet Information Services to be dropped. When the PowerShell application pool completes the Failover Clustering installation, it cannot notify PowerShell.exe that the installation is successful. Eventually, PowerShell.exe reaches the WinRM time-out value and fails.
Back to the top

RESOLUTION

To resolve this problem, use of the following methods before you add the server to the DAG:
  • Install the Failover Clustering component manually.
  • Work with the third-party vendor for help to remove and reinstall Symantec Endpoint Protection.
For information about how to contact Symantec, visit the following Microsoft website:
http://support.microsoft.com/gp/vendors (http://support.microsoft.com/gp/vendors)
Back to the top
APPLIES TO
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
Back to the top
Keywords: 
kbsurveynew KB2294243
Back to the top