locked
SCOM Test-ReplicationHealth Runing localy / SCOM give an alert RRS feed

  • Question

  • Hi,
    I have a problem. I am geting in SCOM a lot of alerts with

    Mailbox Database Copies Failed - CADV0260 (Mailbox) - CDCCAD False Database copies failed on server
    Mailbox Database Copies Failed - CADV0261 (Mailbox) - CDCCAD False Database copies failed on server
    CADV0260.ad1.internal;CADV0260 (Mailbox) - CDCCAD Replay Service - CADV0260 (Mailbox) - CDCCAD False Error occurred while executing the Test-ReplicationHealth diagnostic cmdlet. 
    CADV0261.ad1.internal;CADV0261 (Mailbox) - CDCCAD Replay Service - CADV0261 (Mailbox) - CDCCAD False Error occurred while executing the Test-ReplicationHealth diagnostic cmdlet.

    The comand Test-Replication is working corectly on the server if you run it manualy.

    I have investigated and it appers that are related to the events:

    Log Name:      MSExchange Management
    Source:        MSExchange CmdletLogs
    Date:          14.2.2012 20:46:08
    Event ID:      6
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      CADV0261.domain.local
    Description:
    Cmdlet failed. Cmdlet Test-ReplicationHealth, parameters {MonitoringContext=True, TransientEventSuppressionWindow=3}.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange CmdletLogs" />
        <EventID Qualifiers="49152">6</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-02-14T18:46:08.000000000Z" />
        <EventRecordID>40570</EventRecordID>
        <Channel>MSExchange Management</Channel>
        <Computer>CADV0261.domain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Test-ReplicationHealth</Data>
        <Data>{MonitoringContext=True, TransientEventSuppressionWindow=3}</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>Exchange Management Console-Local</Data>
        <Data>876</Data>
        <Data>
        </Data>
        <Data>40</Data>
        <Data>00:00:00.5616036</Data>
        <Data>View Entire Forest: 'False', Default Scope: 'domain.local', Configuration Domain Controller: 'CADAD1DC02.domain.local', Preferred Global Catalog: 'CADad1dc01.domain.local', Preferred Domain Controllers: '{ CADad1dc01.domain.local }'</Data>
        <Data>System.Management.Automation.PSInvalidOperationException: The WriteObject and WriteError methods cannot be called from outside the overrides of the BeginProcessing, ProcessRecord, and EndProcessing methods, and only from that same thread. Validate that the cmdlet makes these calls correctly, or please contact Microsoft Support Services.
       at System.Management.Automation.MshCommandRuntime.ThrowIfWriteNotPermitted(Boolean needsToWriteToPipeline)
       at System.Management.Automation.MshCommandRuntime.WriteHelper_ShouldWrite(ActionPreference preference, ContinueStatus lastContinueStatus)
       at System.Management.Automation.MshCommandRuntime.WriteVerbose(VerboseRecord record)
       at System.Management.Automation.Cmdlet.WriteVerbose(String text)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteVerbose(LocalizedString text)
       at Microsoft.Exchange.Monitoring.ActiveManagerCheck.InternalRun()
       at Microsoft.Exchange.Monitoring.ReplicationCheck.Run()
       at Microsoft.Exchange.Monitoring.MultiReplicationCheck.Run()
       at Microsoft.Exchange.Monitoring.TestReplicationHealth.RunChecks()
       at Microsoft.Exchange.Monitoring.TestReplicationHealth.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()</Data>
        <Data>0</Data>
        <Data>
        </Data>
      </EventData>
    </Event>

     

    Log Name:      MSExchange Management
    Source:        MSExchange CmdletLogs
    Date:          14.2.2012 20:46:08
    Event ID:      6
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      CADV0261.domain.local
    Description:
    Cmdlet failed. Cmdlet Test-ReplicationHealth, parameters {MonitoringContext=True}.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange CmdletLogs" />
        <EventID Qualifiers="49152">6</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-02-14T18:46:08.000000000Z" />
        <EventRecordID>40571</EventRecordID>
        <Channel>MSExchange Management</Channel>
        <Computer>CADV0261.domain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Test-ReplicationHealth</Data>
        <Data>{MonitoringContext=True}</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>Exchange Management Console-Local</Data>
        <Data>876</Data>
        <Data>
        </Data>
        <Data>18</Data>
        <Data>00:00:00.5772037</Data>
        <Data>View Entire Forest: 'False', Default Scope: 'domain.local', Configuration Domain Controller: 'CADAD1DC02.domain.local', Preferred Global Catalog: 'CADad1dc01.domain.local', Preferred Domain Controllers: '{ CADad1dc01.domain.local }'</Data>
        <Data>System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.Exchange.Monitoring.ActiveManagerCheck.InternalRun()
       at Microsoft.Exchange.Monitoring.ReplicationCheck.Run()
       at Microsoft.Exchange.Monitoring.MultiReplicationCheck.Run()
       at Microsoft.Exchange.Monitoring.TestReplicationHealth.RunChecks()
       at Microsoft.Exchange.Monitoring.TestReplicationHealth.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()</Data>
        <Data>0</Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Hope that you can help,
    Thank you

    Tuesday, February 14, 2012 7:16 PM

Answers

  • Hi,

    If the result is success when you run test-replicatiionhealth, then I think you can ignore the alert.

    Also you can run ExBPA to double check the health of the organization.


    Xiu Zhang

    TechNet Community Support

    • Marked as answer by Xiu Zhang Monday, February 27, 2012 6:15 AM
    Thursday, February 16, 2012 7:19 AM

All replies

  • Hi,

    If the result is success when you run test-replicatiionhealth, then I think you can ignore the alert.

    Also you can run ExBPA to double check the health of the organization.


    Xiu Zhang

    TechNet Community Support

    • Marked as answer by Xiu Zhang Monday, February 27, 2012 6:15 AM
    Thursday, February 16, 2012 7:19 AM
  • Hi!

    We have the same problem. Just upgraded the mgmt pack for exchange 2010 from 14.0.650.8 to 14.2.71.0 on one of our environments (test). The agents on all machines reports to two different SCOM enviroments (test and production). As soon we updates the test SCOM environment we're getting these errors all the time. I can runt the cmdlets manually without any errors and i don't think the solution is not to ignore the alerts.

    /JonasR

    Tuesday, March 27, 2012 1:10 PM
  • Hi,

    We are also experiencing the same problem  We are constantly receiving this alert after upgrading to Exchange 2010 mp 14.2.71.0.  I agree with the above that we should just ignore the alert.  I also don't want to run the cmdlets manually all the time.  The alert should be fixed.  Thanks, Joanne Kamo

    Thursday, July 12, 2012 2:30 PM
  • Test-ReplicationHealth cmd-let from Exchange Management Tools is not thread safe. So, the only one instance of this command could be executed in every time moment. You could easily reproduce this problem, you should just open two PowerShell command line session, print this command in both and try to execute them simultaneously (press Enter in both PowerShell windows as quick as possible). You will see the same error. Probably sometimes SCOM runs several instances of this command very closely in time and you get this error.
    Friday, September 7, 2012 3:05 PM