locked
Errors On Blackberry Enterprise Server - 9100 and 10407 RRS feed

  • Question

  • My Blacberry Enterprise Server is not being properly monitored out of System Center Essentials.  In the Computers view, it shows as a type unkown.  It is the only server that in our environment that is experiencing these errors.  It started out as events 9100 and 10407; finding no resolution, but having had it work in the past, I tried removing SCE from the server, and removing the server from SCE, adding it the following day.  Now I get event 9100, with a different line refence as the fialing point in the script.

     

    The SCE Management Packs were updated to the August, 2007 management pack files.  I went ahead and downloaded the msi, expanded it, and re-imported the management packs, which SCE told me that it did not do since they were the same versions as what I was trying to install.

     

    Original 9100 Error:

     

    Event Type: Error
    Event Source: Health Service Modules
    Event Category: None
    Event ID: 9100
    Date:  1/24/2008
    Time:  6:01:19 AM
    User:  N/A
    Computer: MNOPBES
    Description:
    An error occurred on line 101 while executing script 'MOM Backward Compatibility Service State Monitoring Script'
    Source: SWbemServicesEx
    Description: Quota violation 

    One or more workflows were affected by this. 

    Workflow name: System.Mom.BackwardCompatibility.ServiceStateMonitoring
    Instance name: mnopbes.mpls1.org
    Instance ID: {119188A4-3256-6DF4-BD20-3F42EA01D023}
    Management group: LSS002_MG

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: Health Service Modules
    Event Category: None
    Event ID: 10407
    Date:  1/24/2008
    Time:  6:01:23 AM
    User:  N/A
    Computer: MNOPBES
    Description:
    ExecQuery failed

     Query: 'SELECT NumberOfProcessors FROM Win32_ComputerSystem WHERE DomainRole >3'
     
    Error: 0x8004106c
    Details: 

    One or more workflows were affected by this. 

    Workflow name: System.Mom.BackwardCompatibility.Computer.DC.DiscoveryRule
    Instance name: mnopbes.mpls1.org
    Instance ID: {119188A4-3256-6DF4-BD20-3F42EA01D023}
    Management group: LSS002_MG

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: Health Service Modules
    Event Category: None
    Event ID: 10407
    Date:  1/24/2008
    Time:  6:01:40 AM
    User:  N/A
    Computer: MNOPBES
    Description:
    ExecQuery failed

     Query: 'SELECT * FROM Win32_Service WHERE Name="ClusSvc" and State="Running"'
     
    Error: 0x8004106c
    Details: 

    One or more workflows were affected by this. 

    Workflow name: Microsoft.Windows.Cluster.Service.Discovery
    Instance name: mnopbes.mpls1.org
    Instance ID: {20A0C84F-522F-A5D8-7A79-E7E671F934AF}
    Management group: LSS002_MG

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: Health Service Modules
    Event Category: None
    Event ID: 10407
    Date:  1/24/2008
    Time:  6:01:51 AM
    User:  N/A
    Computer: MNOPBES
    Description:
    ExecQuery failed

     Query: 'SELECT NumberOfProcessors FROM Win32_ComputerSystem WHERE DomainRole >3'
     
    Error: 0x8004106c
    Details: 

    One or more workflows were affected by this. 

    Workflow name: Microsoft.SystemCenter.DiscoverWindowsServerDCComputer
    Instance name: mnopbes.mpls1.org
    Instance ID: {119188A4-3256-6DF4-BD20-3F42EA01D023}
    Management group: LSS002_MG

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Now I just get the following 9100 error, which references a different line in the script:

     

    Event Type: Error
    Event Source: Health Service Modules
    Event Category: None
    Event ID: 9100
    Date:  1/31/2008
    Time:  2:15:47 PM
    User:  N/A
    Computer: MNOPBES
    Description:
    An error occurred on line 71 while executing script 'MOM Backward Compatibility Service State Monitoring Script'
    Source: Microsoft VBScript runtime error
    Description: Type mismatch: 'SetEventParameter'

    One or more workflows were affected by this. 

    Workflow name: System.Mom.BackwardCompatibility.ServiceStateMonitoring
    Instance name: mnopbes.mpls1.org
    Instance ID: {119188A4-3256-6DF4-BD20-3F42EA01D023}
    Management group: LSS002_MG

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    On the bright side, no 10407 warnings are taking place.  Apparently, I am not the only person who has a combinatiion of SCE2007, and servers running Windows 2003 SP2 with BlackBerry Enterprise Server version 4.x producing an error concerning hte MOM 2005 Backwards Compatability Script.

     

    I did try editing the script, removing the offending blank line.  SCE dutifully noted that the script was not a match wo what it expected, replaced it on the next cycle, and started producing 9100 errors again.  It's a good news/bad news scenario...

     

    The other role that this server supports is for MessagOne EMS, which does mailbox re-imports after email server outages.  That software primarilly does information gathering and monitoring of our Exchagne servers and polls some informtion off of the GC's.  However, the 9100 errors regardless of the state of MessageOne (whcih is idle except for its once a day routines of gathering informaiton).

     

    Thanks for looking at this.  Hopefully, someone else has run into this and has a fix.

     

    Jim@Work

    Thursday, January 31, 2008 8:36 PM

Answers

  • Hi,

     

    This is the bug for SCOM 2007, customer encounter this problem with SCOM can be fixed by deploying Service Pack1 for SCOM 2007.

     

    For SCE has the same monitoring component as SCOM 2007,so issue outline here, we suggest downloading and applying the "OpsMgr 2007 MOM 2005 Backward Compatibility MP Update" as a work-around.Also this problem has been reported,we will reply here if any update from product team.

     

    Updates includes the following additional functionality:

     

    1. Update to allow script generated performance data from converted MPs to be written to the data warehouse
    2. Update to allow script generated events from converted MPs to be written to the data warehouse
    3. Update to allow service state events to be written to the data warehouse


    Details please see the below web pages:

     

    OpsMgr 2007 MOM 2005 Backward Compatibility MP Update

    http://www.microsoft.com/downloads/details.aspx?FamilyID=655cdd06-861e-4342-99b2-8a81e09f6546&DisplayLang=en

     

    Please let us know the result.

     

    2.    Error 10407

     

    The error code 0x8004106c = WBEM_E_QUOTA_VIOLATION. Indicated that WMI is taking up too much memory. This can be caused by low memory availability or excessive memory consumption by WMI.

    828653 Large WMI notification query may cause a quota violation
    http://support.microsoft.com/?id=828653

     

     

    BTW,"System Center Operations Manager 2007 Update" includes the below list files but not 'MOM Backward Compatibility MP"

     

    • Microsoft.SystemCenter.2007.mp (6.0.5000.28)
    • Microsoft.SystemCenter.Internal.mp (6.0.5000.28)
    • Microsoft.SystemCenter.Library.mp (6.0.5000.28)
    • Microsoft.SystemCenter.OperationsManager.200.mp (6.0.5000.28)
    • Microsoft.SystemCenter.ServiceDesigner.Library.mp (6.0.5000.28)
    • Microsoft.SystemCenter.WebApplication.Library.mp (6.0.5000.28)
    • System.Health.Library.mp (6.0.5000.28)

     

     

    Please let us know the result.

    Thanks.

     

     

    Best regards,

    Xiu Zhang - MSFT

    Microsoft Online Community Support

    Monday, February 4, 2008 6:31 AM

All replies

  • Hi,

     

    This is the bug for SCOM 2007, customer encounter this problem with SCOM can be fixed by deploying Service Pack1 for SCOM 2007.

     

    For SCE has the same monitoring component as SCOM 2007,so issue outline here, we suggest downloading and applying the "OpsMgr 2007 MOM 2005 Backward Compatibility MP Update" as a work-around.Also this problem has been reported,we will reply here if any update from product team.

     

    Updates includes the following additional functionality:

     

    1. Update to allow script generated performance data from converted MPs to be written to the data warehouse
    2. Update to allow script generated events from converted MPs to be written to the data warehouse
    3. Update to allow service state events to be written to the data warehouse


    Details please see the below web pages:

     

    OpsMgr 2007 MOM 2005 Backward Compatibility MP Update

    http://www.microsoft.com/downloads/details.aspx?FamilyID=655cdd06-861e-4342-99b2-8a81e09f6546&DisplayLang=en

     

    Please let us know the result.

     

    2.    Error 10407

     

    The error code 0x8004106c = WBEM_E_QUOTA_VIOLATION. Indicated that WMI is taking up too much memory. This can be caused by low memory availability or excessive memory consumption by WMI.

    828653 Large WMI notification query may cause a quota violation
    http://support.microsoft.com/?id=828653

     

     

    BTW,"System Center Operations Manager 2007 Update" includes the below list files but not 'MOM Backward Compatibility MP"

     

    • Microsoft.SystemCenter.2007.mp (6.0.5000.28)
    • Microsoft.SystemCenter.Internal.mp (6.0.5000.28)
    • Microsoft.SystemCenter.Library.mp (6.0.5000.28)
    • Microsoft.SystemCenter.OperationsManager.200.mp (6.0.5000.28)
    • Microsoft.SystemCenter.ServiceDesigner.Library.mp (6.0.5000.28)
    • Microsoft.SystemCenter.WebApplication.Library.mp (6.0.5000.28)
    • System.Health.Library.mp (6.0.5000.28)

     

     

    Please let us know the result.

    Thanks.

     

     

    Best regards,

    Xiu Zhang - MSFT

    Microsoft Online Community Support

    Monday, February 4, 2008 6:31 AM
  • Hi Xiu Zhang -

     

    Thanks for the clarification.  Running the OpsMgr 2007 MOM 2005 Backward Compatibility MP Update has left the condition of the monitored server failing on line 101 instead of 71.  Since the hotfix is not fully tested at this time, and the overall impact on my server is minimal, I will hold off on the fix described in http://support.microsoft.com/?id=828653.  We are seeing a number of workstations with the same basic backward compatability script error, although I haven't put the time into investigating further to see if there is a pattern to which workstations are affected.  Knowing that the solution is being addressed and will be part of a rollup or released fix is enough for now.

     

    Thanks for your timely response.

     

    Jim@Work

    Monday, February 4, 2008 10:16 PM