Event ID 22406 on first SCOM 2016 Management Server

Forum: Operations Manager4
Viewing 3 posts - 1 through 3 (of 3 total)
  • #230218
    Profile photo of Birdal
    Birdal
    Participant

    Hi,

    I installed the first Management Server based on SCOM 2016. The Operations Database is installed on another compuer, also Data Warehouse Databse  on the other Computer. The first Manaegemnt Server installation run without any problem.

    As I analyzed always EventView logs I found repeated Event ID 22406 with error  “Operations Manager The PowerShell script failed with below exception”.

    This error is generated alway for two scripts:

    Script Name: GetMGAlertsCount.ps1 and Script Name: AgentStateRollup.ps1

    (see attachment)

    What is the resaon of these logs on a completely new installed Management Server?

    Best Regards

    Birdal

    Attachments:
    You must be logged in to view attached files.
    #230789

    Hi,

    I’m also facing similar issue, following event is logged frequently on the management server but is it not newly set up server.

    I understood that these alerts are from our Customized TFS management pack but not sure how to fix it. This is also impacting the discovery of TFS team projects.

    Event Id 22406, Health Service Modules

    The PowerShell script failed with below exception

    System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter ‘TeamProjectUrl’ because it is an empty string.
    at System.Management.Automation.ParameterBinderBase.ValidateNullOrEmptyArgument(CommandParameterInternal parameter, CompiledCommandParameter parameterMetadata, Type
    argumentType, Object parameterValue, Boolean recurseIntoCollections)
    at System.Management.Automation.ParameterBinderBase.BindParameter(CommandParameterInternal parameter, CompiledCommandParameter parameterMetadata,
    ParameterBindingFlags flags)
    at System.Management.Automation.CmdletParameterBinderController.BindParameter(CommandParameterInternal argument, MergedCompiledCommandParameter parameter,
    ParameterBindingFlags flags)
    at System.Management.Automation.CmdletParameterBinderController.BindParameter(UInt32 parameterSets, CommandParameterInternal argument,
    MergedCompiledCommandParameter parameter, ParameterBindingFlags flags)
    at System.Management.Automation.CmdletParameterBinderController.BindParameters(UInt32 parameterSets, Collection1 arguments)
    at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParametersNoValidation(Collection
    1 arguments)
    at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParameters(Collection`1 arguments)
    at System.Management.Automation.CommandProcessor.BindCommandLineParameters()
    at System.Management.Automation.CommandProcessorBase.DoPrepare(IDictionary psDefaultParameterValues)
    at System.Management.Automation.Internal.PipelineProcessor.Start(Boolean incomingStream)
    at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)

    Script Name: TfsTeamProject.HttpAvailability.ps1

    One or more workflows were affected by this.

    Workflow name: XXXXXXXX.TfsTeamProject.HttpAvailability
    Instance name:
    Instance ID: {84A6BB6F-4D7B-986E-3935-325A68C267D5}
    Management group: XXXXXX

    #231015
    Profile photo of Shahid
    Shahid
    Participant

    I a m also having many PowerShell failure warning with Event ID 22406. I am using SCOM 2012 R2. Please suggest the solution

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.