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

This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
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:
Get-ClusteredMailboxServerStatus -Identity cluster mailbox server name
When you do this, the Get-ClusteredMailboxServerStatus cmdlet does not run successfully. Additionally, you receive the following error message:
WARNING: An unexpected error has occurred and debug information is being generated: Object reference not set to an instance of an object.
Get-ClusteredMailboxServerStatus : Object reference not set to an instance of an object.
At line:1 char:33
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

CAUSE
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:
Enable-ContinuousReplicationHostName -Identity cluster mailbox server name -TargetMachine node name -IPv4Address ip address -HostName ContinuousReplicationHostName
WORKAROUND

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:
Disable-ContinuousReplicationHostName -Identity cluster mailbox server name -TargetMachine node name -IPv4Address ip address -HostName ContinuousReplicationHostName
STATUS
This behavior is by design.
Properties

Article ID: 952119 - Last Review: 01/16/2015 02:28:53 - Revision: 2.0

  • Microsoft Exchange Server 2007 Standard Edition
  • Microsoft Exchange Server 2007 Enterprise Edition
  • kbnosurvey kbarchive kbprb kbtshoot kbexpertiseinter KB952119
Feedback