locked
"HP StoreVirtual SNMP Trap Catcher Rule" error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've installed the "HP Storage Management Pack for System Center" version 3.0.1.0 on Scom 2012 SP1. On every physical and virtual machine I receive lots of related errors like the one below. checked and double checked the SNMP configurations. Checked for the mentioned "HPEnterpriseStorageLeftHandMP" rule but I can't find this one in SCOM. What can be the problem.

    Thanks for your reply.

    Module was unable to execute the notification query.

    Error: 0x80041010

    Details: Invalid class

    One or more workflows were affected by this. 

    Workflow name: HPEnterpriseStorageLeftHandMP.BootTrap.Catcher.Rule

    Instance name: HP StoreVirtual SNMP Trap Catcher Rule

    Instance ID: {FD94C6F8-1E4A-0C5E-D1EC-C328EBC8C6BD}

    Management group: My Group

    Wednesday, October 2, 2013 8:42 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    We can use the powershell comlet to get scom rule or disable scom rule:

    Get-SCOMRule

    http://technet.microsoft.com/en-us/library/hh918556(v=sc.10).aspx

    Disable-SCOMRule

    http://technet.microsoft.com/en-us/library/hh920256(v=sc.10).aspx

    Alex Zhao
    TechNet Community Support

    • Marked as answer by Cloud_TS Monday, October 21, 2013 9:40 AM
    Friday, October 4, 2013 9:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Don't know how the answer is related to my problem. But I noticed something else.

    Even on my monitored XP machines I read the same kind of error but it gave me some extra information. It's in dutch, but it says its missing a powershell script. Even the directory its in, is missing. Come to believe it's from an older version that was left behind in the HP Storage Management Pack.

    Could it simply be some script on the Scom server that needs to be tweaked?

    Type gebeurtenis:    Fout

    Bron van gebeurtenis:    Health Service Modules

    Categorie van gebeurtenis:    Geen

    Gebeurtenis-ID:    21400

    Datum:        5-10-2013

    Tijd:        17:10:46

    Gebruiker:        n.v.t.

    Computer:    Mycomputer

    Beschrijving:

    Kan geen proces genereren als gevolg van fout 0x80070003 : Het systeem kan het opgegeven pad niet vinden.

    ; deze werkstroom wordt verwijderd.



    Opdracht die is uitgevoerd:  
     "C:\WINDOWS\System32\WindowsPowerShell\v1.0\PowerShell.exe" "&
    '"C:\Program Files\System Center Operations Manager\Agent\Health Service
    State\Monitoring Host Temporary Files
    2\815\HPEnterpriseStorageLeftHandMPDiscovery.ps1"'
    '{08817C3D-C739-55BA-6F65-3D9DB2DE27D6}'
    '{EB100167-5D6B-4027-AD5C-E00C75F15C16}' 'HP StoreVirtual Storage'
    ICT-CONTROLE"

    Werkmap:    C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 2\815\



    Dit is van invloed op een of meer werkstromen.  



    Werkstroomnaam: HPEnterpriseStorageLeftHandMP.DiscoverRule

    Exemplaarnaam: MyComputer

    Exemplaar-id: {EB100167-5D6B-4027-AD5C-E00C75F15C16}

    Beheergroep: My Group



    Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie.

    Saturday, October 5, 2013 3:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    2 Years later..but did you ever find a solution? We use version 4.2 of that management pack and suffer the same issue. I believe it is related to the discovery job. At first we had an override to enable the job on the windows class and all systems that had agents at that time suffer this alert. After that i override the discovery to run only on the objects of the collectionservers. Now servers that got an agent after i changed the override don't show the alert...i only don't know how to get rid of the alerts of the earlier agents..cleaning the health service state folder don't seem to work.

    Gr,

    Ronald

    Thursday, July 23, 2015 11:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    unfortunately not. After all updates the messages are still there. learned to ignore them.
    Thursday, July 23, 2015 11:43 AM