The Get-ClusteredMailboxServerStatus cmdlet does not run successfully, you receive an error message, and event ID 4999 is logged in Exchange Server 2007

On a computer that is running Microsoft Exchange Server 2007, you open Exchange Management Shell. Then, you try to obtain the cluster mailbox server status of a remote cluster continuous replication (CCR) cluster by running the following cmdlet:When you do this, the Get-ClusteredMailboxServerStatus cmdlet does not run successfully. Additionally, you receive the following error message:Additionally, the following event is logged in the Application log:

Event Type: Error
Event Source: MSExchange Common
Event Category: General
Event ID: 4999
Description:
Watson report about to be sent to dw20.exe for process id: process id, with parameters: E12, processor, version, powershell, M.E.C.Replay, M.E.C.R.NetworkNameMatcher.IsNetNameResourceReachable, System.NullReferenceException, 7616, version. ErrorReportingEnabled: False

This behavior occurs if the CCR replication was enabled by using a redundant network name.

Note Typically, to enable CCR replication, the following cmdlet is used:

Workaround 1 (preferred)

Run the Get-ClusteredMailboxServerStatus cmdlet locally on the cluster node that owns the clustered mailbox server whose status you want to view. You can also use the Remote Desktop client to connect to a node in the cluster and then run the Get-ClusteredMailboxServerStatus cmdlet locally in this manner.

Workaround 2

Disable the ContinuousReplicationHostName cmdlet. To do this, run the following cmdlet:

This behavior is by design.

For more information, visit the following Microsoft Web sites: