Home
  •  

HIP - Host requests rejected

HIP___Host_requests_rejected_12_Rule.AdvancedAlertCriteriaMonitor (UnitMonitor)

Knowledge Base article:

Management Pack
Summary

A large number of incoming requests from a host system are being rejected by the HIP Application.

 
Causes
  • The requests are from an unrecognized host system
  • The maximum number of queued requests for the HIP Application has been reached
  • The requests have invalid resolution data
 
Resolutions
  • Requests from an unrecognized host system or malformed requests could indicate a possible security attack being attempted on the HIP Service. The client system issuing the requests should be investigated.
  • If requests are being rejected because the maximum number of queued requests has been reached, consider increasing the number of worker threads on the HIP Application or increasing the maximum number of queued requests.
  • If requests are being rejected due to invalid resolution data, compare the request and what is expected in the HIP application view. As necessary, adjust the view and/or the host system making the request.
  • If this condition is encountered on a regular basis, consider adding an additional server(s) running the HIP Application to support the application load.
 
© 1995-2001 Microsoft Corporation, all rights reserved.

Element properties:

TargetMicrosoft.HostIntegrationServer.2006.HIS_HIP_Class
Parent MonitorApp
CategoryStateCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeSystem.Mom.BackwardCompatibility.PerformanceThreshold.TwoStateMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
HIP - Host requests rejected
{1}
RunAsDefault
CommentMom2005ID='{6421E5D3-1E3D-41F3-89B7-EDD7589721D2}'

Source Code:

<UnitMonitor ID="HIP___Host_requests_rejected_12_Rule.AdvancedAlertCriteriaMonitor" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.PerformanceThreshold.TwoStateMonitorType" Accessibility="Internal" Target="Microsoft.HostIntegrationServer.2006.HIS_HIP_Class" Enabled="true" ParentMonitorID="App" Comment="Mom2005ID='{6421E5D3-1E3D-41F3-89B7-EDD7589721D2}'">

  <Category>StateCollection</Category>

  <AlertSettings AlertMessage="HIP___Host_requests_rejected_12_Rule.AdvancedAlertCriteriaMonitor.StringResource">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/Name$</AlertParameter1>

      <AlertParameter2>$Data/Context/Description$</AlertParameter2>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState HealthState="Error" MonitorTypeStateID="ConditionTrue" ID="AlertConditionTrue"/>

    <OperationalState HealthState="Success" MonitorTypeStateID="ConditionFalse" ID="AlertConditionFalse"/>

  </OperationalStates>

  <Configuration>

    <ServerRole>HIS HIP</ServerRole>

    <Component>App</Component>

    <ServerRoleInstance>$Target/Property[Type="Microsoft.HostIntegrationServer.2006.HIS_HIP_Class"]/Application_Name$</ServerRoleInstance>

    <RuleId>$MPElement[Name="HIP___Host_requests_rejected_12_Rule"]$</RuleId>

    <Threshold>180</Threshold>

    <Operator>Greater</Operator>

  </Configuration>

</UnitMonitor>