locked
NetApp Clustered Data ONTAP MP: SCOM 2012 R2 MS Powershell script was dropped RRS feed

  • Question

  • Hello,

    I have added some NetApp Clusters to SCOM 2012 R2 and discovered them.
    Now I get this annoying warning for Monitoring.ps1 and Discovery.ps1:Powershell script was dropped every 15 minutes.

    I think this prevents the SCOM Agent from discovering Information about the Clusters.
    The error code is attached at the end of page.
    Can someone help me?

    regards,

    Matthias

    Error Discovery.ps1:

    The PowerShell script failed with below exception

    System.Management.Automation.MethodInvocationException: Exception
    calling "CreateDomain" with "3" argument(s): "The specified user does not have a
    valid profile. Unable to load
    'Microsoft.EnterpriseManagement.HealthService.Internal, Version=7.0.5000.0,
    Culture=neutral, PublicKeyToken=31bf3856ad364e35'."At line:40 char:12
    +
    return [AppDomain]::CreateDomain("OC.Cluster.OM.Powershell.NonDefaultAppDoma
    ...
    +
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    at
    System.Management.Automation.ExceptionHandlingOps.ConvertToMethodInvocationException(Exception
    exception, Type typeToThrow, String methodName, Int32 numArgs, MemberInfo
    memberInfo)
    at CallSite.Target(Closure , CallSite , RuntimeType , String ,
    Object , Object )
    at
    System.Dynamic.UpdateDelegates.UpdateAndExecute4[T0,T1,T2,T3,TRet](CallSite
    site, T0 arg0, T1 arg1, T2 arg2, T3 arg3)
    at
    System.Management.Automation.Interpreter.DynamicInstruction`5.Run(InterpretedFrame
    frame)
    at
    System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
    frame)

    Script Name: Discovery.ps1

    One or more
    workflows were affected by this.

    Workflow name:
    DataONTAP.Cluster.Discovery.Rule

    Instance name: Clustered Data ONTAP:
    Management Server Resource Pool

    Instance ID:
    {9B98C733-1520-62CD-662A-2B6B1C5DCB7F}

    XML Discovery.ps1:

    < DataItem
    type =" System.XmlData " time =" 2016-04-01T00:00:00.3070786+02:00 " sourceHealthServiceId =" 6FA0044D-D37C-9C58-D906-4E7C8BF54459 " >
    < EventData
    >
      < Data > XXXXXX </ Data >
      < Data > DataONTAP.Cluster.Discovery.Rule </ Data >
      < Data > Clustered Data
    ONTAP: Management Server Resource Pool
    </ Data >
      < Data > {9B98C733-1520-62CD-662A-2B6B1C5DCB7F} </ Data >
      < Data > Discovery.ps1 </ Data >
      < Data > 1800
    </ Data
    >
      < Data > System.Management.Automation.MethodInvocationException:
    Exception calling "CreateDomain" with "3" argument(s): "The specified user does
    not have a valid profile. Unable to load
    'Microsoft.EnterpriseManagement.HealthService.Internal, Version=7.0.5000.0,
    Culture=neutral, PublicKeyToken=31bf3856ad364e35'."At line:40 char:12 + return
    [AppDomain]::CreateDomain("OC.Cluster.OM.Powershell.NonDefaultAppDoma ... +
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ at
    System.Management.Automation.ExceptionHandlingOps.ConvertToMethodInvocationException(Exception
    exception, Type typeToThrow, String methodName, Int32 numArgs, MemberInfo
    memberInfo) at CallSite.Target(Closure , CallSite , RuntimeType , String ,
    Object , Object ) at
    System.Dynamic.UpdateDelegates.UpdateAndExecute4[T0,T1,T2,T3,TRet](CallSite
    site, T0 arg0, T1 arg1, T2 arg2, T3 arg3) at
    System.Management.Automation.Interpreter.DynamicInstruction`5.Run(InterpretedFrame
    frame) at
    System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
    frame)
    </ Data >
      < Data > System.Management.Automation.MethodInvocationException
    </ Data
    >
      </ EventData
    >
      </ DataItem
    >

    Error Monitoring.ps1:

    The PowerShell script failed with below exception

    System.Management.Automation.MethodInvocationException: Exception
    calling "CreateDomain" with "3" argument(s): "The specified user does not have a
    valid profile. Unable to load
    'Microsoft.EnterpriseManagement.HealthService.Internal, Version=7.0.5000.0,
    Culture=neutral, PublicKeyToken=31bf3856ad364e35'."At line:40 char:12
    +
    return [AppDomain]::CreateDomain("OC.Cluster.OM.Powershell.NonDefaultAppDoma
    ...
    +
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    at
    System.Management.Automation.ExceptionHandlingOps.ConvertToMethodInvocationException(Exception
    exception, Type typeToThrow, String methodName, Int32 numArgs, MemberInfo
    memberInfo)
    at CallSite.Target(Closure , CallSite , RuntimeType , String ,
    Object , Object )
    at
    System.Dynamic.UpdateDelegates.UpdateAndExecute4[T0,T1,T2,T3,TRet](CallSite
    site, T0 arg0, T1 arg1, T2 arg2, T3 arg3)
    at
    System.Management.Automation.Interpreter.DynamicInstruction`5.Run(InterpretedFrame
    frame)
    at
    System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
    frame)

    Script Name: Monitoring.ps1

    One or more
    workflows were affected by this.

    Workflow name:
    DataONTAP.Cluster.Monitoring.Vserver.Connection.Rule

    Instance name:
    a90aa9c0-9923-11e5-94cd-00a0986e78b3

    Instance ID:
    {4B3E134E-D96B-98E3-1CF2-82FFE1FCE1A9}

    XML Monitoring.ps1:

    < DataItem
    type =" System.XmlData " time =" 2016-04-01T00:01:00.4855272+02:00 " sourceHealthServiceId =" 6FA0044D-D37C-9C58-D906-4E7C8BF54459 " >
    < EventData
    >
      < Data > XXXXX </ Data >
      < Data > DataONTAP.Cluster.Monitoring.Vserver.Connection.Rule
    </ Data
    >
      < Data > a90aa9c0-9923-11e5-94cd-00a0986e78b3 </ Data >
      < Data > {4B3E134E-D96B-98E3-1CF2-82FFE1FCE1A9} </ Data >
      < Data > Monitoring.ps1 </ Data >
      < Data > 60 </ Data >
      < Data > System.Management.Automation.MethodInvocationException:
    Exception calling "CreateDomain" with "3" argument(s): "The specified user does
    not have a valid profile. Unable to load
    'Microsoft.EnterpriseManagement.HealthService.Internal, Version=7.0.5000.0,
    Culture=neutral, PublicKeyToken=31bf3856ad364e35'."At line:40 char:12 + return
    [AppDomain]::CreateDomain("OC.Cluster.OM.Powershell.NonDefaultAppDoma ... +
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ at
    System.Management.Automation.ExceptionHandlingOps.ConvertToMethodInvocationException(Exception
    exception, Type typeToThrow, String methodName, Int32 numArgs, MemberInfo
    memberInfo) at CallSite.Target(Closure , CallSite , RuntimeType , String ,
    Object , Object ) at
    System.Dynamic.UpdateDelegates.UpdateAndExecute4[T0,T1,T2,T3,TRet](CallSite
    site, T0 arg0, T1 arg1, T2 arg2, T3 arg3) at
    System.Management.Automation.Interpreter.DynamicInstruction`5.Run(InterpretedFrame
    frame) at
    System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
    frame)
    </ Data >
      < Data > System.Management.Automation.MethodInvocationException
    </ Data
    >
      </ EventData
    >
      </ DataItem
    >

    Tuesday, April 5, 2016 9:26 AM

All replies

  • Hello,

    Based on my research, the discovery and monitoring scripts used by OCPM are called using the Windows PowerShell and are run under the context of the default action account in SCOM. This account should have a Windows profile created to run the PowerShell script. If this account is not used to log in to the SCOM server before running the OCPM SCOM Management pack, the discovery and monitoring tasks will fail to run the PowerShell script.

    Can you Perform the following steps and retry the operation

    1. Log in to the SCOM server with the default action account.
    2. Restart the SCOM service.
    3. Run a manual discovery in SCOM.

    Also please refer to this KB article.

    https://kb.netapp.com/support/index?page=content&i​d=S%3A2020050&actp=LIST

    In addition, you may contact NetApp to help on this.

    Regards,

    Yan Li


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    • Edited by Yan Li_ Wednesday, April 6, 2016 6:32 AM
    • Marked as answer by Matthias Huetz Wednesday, April 6, 2016 9:38 AM
    • Unmarked as answer by Matthias Huetz Wednesday, April 6, 2016 12:32 PM
    • Proposed as answer by Yan Li_ Thursday, April 14, 2016 2:04 AM
    • Marked as answer by Yan Li_ Tuesday, April 26, 2016 4:38 AM
    • Unmarked as answer by Matthias Huetz Tuesday, October 25, 2016 6:58 AM
    Wednesday, April 6, 2016 6:31 AM
  • Hello,

    Thanks that solved the problem!

    regards,

    Matthias

    Wednesday, April 6, 2016 9:39 AM
  • Hello,

    all script error have come back after the discovery task.
    I did everything you suggested me to do:

    "Can you Perform the following steps and retry the operation

    1. Log in to the SCOM server with the default action account.
    2. Restart the SCOM service.
    3. Run a manual discovery in SCOM."

    Do you have any idea how I can solve this problem?

    regards,

    Matthias

    Wednesday, April 6, 2016 12:32 PM
  • Hello,

    Would you please check whether the default action account have a Windows profile in your SCOM server?

    In addition, for this problem, it is also suggested to contact NetApp to help on this.

    Regards,

    Yan Li


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, April 8, 2016 9:00 AM
  • Hi Yan Li,

    It's been a while since I last responded to this post, but it seems the Problem is still remaining.
    I checked the Default Action Account Setting as well as the Windows Profile on all Management Server.
    Everthing Looks fine, but I noticed that the OnCommand Plug-in is installed only on one out of two Management Server.

    Also i was able to set the limit of scripts, that can be executed at once, to 100 and time out to 60 minutes.
    Still no effect on the script drop warning!

    NetApp is also not replying to my post...

    Thank you in advance!

    Matt 

    Monday, October 24, 2016 3:03 PM