Home
  •  

ConfigMgr 2007 Consolidated Status: CI Assignment Manager failed to process CI Assignment changes but will retry on next processing cycle

SMSv4_Consolidated_Status__CI_Assignment_Manager_failed_to_process_CI_Assignment_changes_but_will_retry_on_next_processing_cycle_1_Rule (Rule)

Knowledge Base article:

Summary

When the configuration item assignment Manager wakes up due to change notifications it reads the changed configuration item assignments from the Configuration Manager database. If it fails to read the changes for any reasons then it raises this status message. The configuration item assignment Manager reads the changes again on the next processing cycle timeout or when the next change notification is received, whichever comes first. Note that in this case any changed configuration item assignments processing would be delayed until it succeeds in reading the changes from Configuration Manager database.

Causes

Configuration item assignment Manager may fail to read the changes from Configuration Manager database due to SQL connectivity issues. If you observer multiple status messages then you may want to review any SQL connectivity issues related status messages and fix possible connectivity problems.

Element properties:

TargetMicrosoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Database_Servers_Installation
CategoryEventCollection
EnabledFalse
Alert GenerateFalse
RemotableTrue
CommentMom2005ID='{9B304641-0B41-43D7-B64E-33B4F99B5880}';MOM2005ComputerGroupID={15348338-2E39-4B34-9DFF-4719AE7F1CCE}

Member Modules:

ID Module Type TypeId RunAs 
_F320DA51_13BF_11D3_B2CD_00A0C92A28B4_ DataSource System.Mom.BackwardCompatibility.FilteredEvent.DataProvider Default
ConsolidatedEventWriteAction WriteAction System.Mom.BackwardCompatibility.ConsolidatedEventResponse Default

Source Code:

<Rule ID="SMSv4_Consolidated_Status__CI_Assignment_Manager_failed_to_process_CI_Assignment_changes_but_will_retry_on_next_processing_cycle_1_Rule" Target="Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Database_Servers_Installation" Enabled="false" ConfirmDelivery="false" Comment="Mom2005ID='{9B304641-0B41-43D7-B64E-33B4F99B5880}';MOM2005ComputerGroupID={15348338-2E39-4B34-9DFF-4719AE7F1CCE}">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="_F320DA51_13BF_11D3_B2CD_00A0C92A28B4_" Comment="{F320DA51-13BF-11D3-B2CD-00A0C92A28B4}" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.FilteredEvent.DataProvider">

      <Expression>

        <And>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="Integer">EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>5804</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="String">PublisherName</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>ConfigMgr 2007 Monitor SMS Status Messages</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="ConsolidatedEventWriteAction" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.ConsolidatedEventResponse">

      <ConsolidationProperties>

        <PropertyXPathQuery>EventDisplayNumber</PropertyXPathQuery>

        <PropertyXPathQuery>PublisherName</PropertyXPathQuery>

        <PropertyXPathQuery>EventDescription</PropertyXPathQuery>

      </ConsolidationProperties>

      <Interval>3600</Interval>

    </WriteAction>

  </WriteActions>

</Rule>