locked
Exchange 2007 SCC Cluster MP Error RRS feed

  • Question

  • I have import the Exchange 2007 MP and i'm getting some active warning alerts.

     

    The process started at 3:04:40 PM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 4294967295 Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "DiscoverCluster.js" 4 {59105181-CE39-3377-3D34-9312B2B06FBC} {6EB68F77-FA40-4C6D-BCBA-3FAB7B20EE5F} EXCHVS02.local.net 8.1.240.6 "Default-First-Site-Name" EXCHVS02 Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 29\14140\ One or more workflows were affected by this. Workflow name: Microsoft.Exchange2007.OmSp1.ServerRole.Mailbox.OnCluster.Discovery Instance name: Discovery Helper (EXCHVS02.local.net) Instance ID: {6EB68F77-FA40-4C6D-BCBA-3FAB7B20EE5F} Management group: NET

    Date and Time:

    8/22/2010 3:04:40 PM

    Log Name:

    Operations Manager

    Source:

    Health Service Modules

    Event Number:

    21405

    Level:

    2

    Logging Computer:

    EXM-02

    User:

    N/A

     

    need help to resolve this issue.


    Aucsna
    Tuesday, August 24, 2010 6:13 AM

Answers

  • It looks like your SCC cluster is not being discovered correctly. Please override the log level parameter for the discovery. That will generate more data into the event log of the Exchange node to determine why the discovery fails. Ensure that the cluster virtual node is correctly discovered and has the DNSName property populated (since that property is required for the Exchange discovery to work).
    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    • Marked as answer by Yog Li Wednesday, September 1, 2010 10:58 AM
    Thursday, August 26, 2010 4:16 PM
  • Hi, you should override the discovery rule,

    Exchange 2007 CCR Clustered Mailbox Server Role Discovery

     

    thanks


    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    • Marked as answer by Yog Li Wednesday, September 1, 2010 10:58 AM
    Friday, August 27, 2010 10:54 PM

All replies

  • It looks like your SCC cluster is not being discovered correctly. Please override the log level parameter for the discovery. That will generate more data into the event log of the Exchange node to determine why the discovery fails. Ensure that the cluster virtual node is correctly discovered and has the DNSName property populated (since that property is required for the Exchange discovery to work).
    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    • Marked as answer by Yog Li Wednesday, September 1, 2010 10:58 AM
    Thursday, August 26, 2010 4:16 PM
  • which rule should i overwrite? (Alert on Failed Batch Responses)?

     

     


    Aucsna
    Thursday, August 26, 2010 8:03 PM
  • Hi, you should override the discovery rule,

    Exchange 2007 CCR Clustered Mailbox Server Role Discovery

     

    thanks


    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    • Marked as answer by Yog Li Wednesday, September 1, 2010 10:58 AM
    Friday, August 27, 2010 10:54 PM
  • I have override the Exchange 2007 CCR Clustered Mailbox Server Role Discovery rule.

     

    value set to Logging Level = 4 / Frequency 600

     

    but i'm able to see any errors on the scom server. could please tell me which server event log should i check.



    Aucsna
    Wednesday, September 1, 2010 2:25 PM
  • These will be logged as information messages in the operations manager event log on the physical node(s) of the cluster. Override it for all nodes of the cluster.

    I suspect that the DNS name of the cluster is not discovered, which makes the discovery exit early. You could also check that directly, by looking at the properties of the virtual node in OM (I assume that the virtual node is discovered).

     


    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    Wednesday, September 1, 2010 10:36 PM
  • I have restarted the OPS MGR Service for Cluster mailbox server, after that i have seen below logs. event id 101 DiscoverCluster.js : Expected 8 arguments. But there were 7 arguments. Exiting script. =========================== event id 1210 New configuration became active. Management group "NET", configuration id:"72 71 CC 53 BF 7B 27 49 B7 4F 9E 7E F4 36 0D 16 F1 AD D4 21 ". =========================== event id 10720 The Backwards Compatibility mapper module was not able to start because discovery has not fully completed for this Health Service. This is a transient issue, the affected rule(s) will be unloaded and the Health Service will restart them when initialization is complete. One or more workflows were affected by this. Workflow name: System.Mom.BackwardCompatibility.ServiceStateMonitoring Instance name: EXCHC01.mal.local Instance ID: {4BE81326-E314-251A-A311-E31F26A972C6} Management group: NET =========================== event id 5500 Frequent state change requests caused the incoming state change request to be dropped due to it being older than currently recorder state change for this monitor. This could also be due to an invalid configuration for this monitor. Affected monitor ID: 949A0003-4589-EC81-F5D8-5A3C7A07551B Instance ID: 65E440AC-4856-3747-B222-9F646D4040AC Management Group ID: 2A5A46B1-76CF-CA00-A2F1-CEE75A1C57EA Request generated time: 2010-09-02T09:00:18.4775952+03:00 Requested state: Success Recorded time: 2010-09-02T09:00:18.4932199+03:00 Recorded state Success For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. =========================== event id 5500 Frequent state change requests caused the incoming state change request to be dropped due to it being older than currently recorder state change for this monitor. This could also be due to an invalid configuration for this monitor. Affected monitor ID: BDA7F935-9E69-26BA-AC50-263457384DC0 Instance ID: 19F05FCA-3139-297B-E53D-4E8F35B25175 Management Group ID: 2A5A46B1-76CF-CA00-A2F1-CEE75A1C57EA Request generated time: 2010-09-02T09:00:18.4307211+03:00 Requested state: Success Recorded time: 2010-09-02T09:00:18.4463458+03:00 Recorded state Success For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    • Edited by shadowsl Thursday, September 2, 2010 7:51 AM content update
    Thursday, September 2, 2010 6:32 AM
  • I am pretty certain this is because your cluster node does not have the DNS name discovered. This should be fixed by applying the latest cumulative update to your environment (actually this issue was fixed a while ago).

    The Exchange discovery won't work until the dns name property of the cluster is discovered.


    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    Friday, September 3, 2010 12:34 AM