none
notification subscriptions that use alert fields as criteria

    Question

  • seem to be having some problems getting notification subscriptions working when trying to use custom field 1 or alert description.  anyone else seeing this problem?

    here's an article i found.  i'm runing sp1 r2 so i'm not sure if it applies or not.  http://support.microsoft.com/kb/937470.
    seems to be the exact issue i'm experiencing.

    thanks!

    ::marcus
    Thursday, June 18, 2009 10:08 PM
    Moderator

Answers

  • I had the same problem. I opened a case at Micrsoft. After investigating they confirmed that is is a bug.

    The following procedure can be used as a workaround until a hotfix is available

    1, Export the ‘Notifications Internal Library’ Management Pack.

    2, Increase the <Version>. For example:

    <Version>6.1.7221.1</Version>

     

    3, Locate the mistakes for each custom Field, which will look like:

     <SimpleExpression xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

                    <ValueExpression>

                                    <Property>Custom8</Property>

                    </ValueExpression>

                    <Operator>Equal</Operator>

    <ValueExpression>

                                    <Value>RobsTest</Value>

                     </ValueExpression>

      </SimpleExpression>

     

    4, Update this by changing Custom8 to CustomField8. For example:

    <SimpleExpression xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

                    <ValueExpression>

                                    <Property>CustomField8</Property>

                    </ValueExpression>

                    <Operator>Equal</Operator>

    <ValueExpression>

                                    <Value>RobsTest</Value>

                     </ValueExpression>

      </SimpleExpression>

     

    5, Save the file & import back into OpsMgr.

    Friday, July 10, 2009 6:00 PM

All replies

  • Marcus,

    I will look into this.  Can you export your notifications MP and post just the section for the subscription you are having an issue with?

    Thanks
    Rob Kuehfus | System Center Operations Manager | Setup and Deployment Program Manager
    Friday, June 19, 2009 1:56 AM
    Moderator
  • hey rob!  thanks for the response.  is this what you're looking for?

    <Rule ID="Subscription41352810_bb11_4d86_adce_d36fd7c00543" Enabled="true" Target="Notification!Microsoft.SystemCenter.AlertNotificationSubscriptionServer" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">
            <Category>Notification</Category>
            <DataSources>
              <DataSource ID="DS1" RunAs="SystemCenter!Microsoft.SystemCenter.DatabaseWriteActionAccount" TypeID="SystemCenter!Microsoft.SystemCenter.SubscribedAlertProvider">
                <AlertChangedSubscription Property="Any">
                  <Criteria>
                    <Expression>
                      <And xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                        <Expression>
                          <SimpleExpression>
                            <ValueExpression>
                              <Property>RuleId</Property>
                            </ValueExpression>
                            <Operator>Equal</Operator>
                            <ValueExpression>
                              <Value>79762c98-ecb3-c400-48e1-fcfaa6b0ab38</Value>
                            </ValueExpression>
                          </SimpleExpression>
                        </Expression>
                        <Expression>
                          <SimpleExpression>
                            <ValueExpression>
                              <Property>Custom1</Property>
                            </ValueExpression>
                            <Operator>Like</Operator>
                            <ValueExpression>
                              <Value>MyGroup%</Value>
                            </ValueExpression>
                          </SimpleExpression>
                        </Expression>
                      </And>
                    </Expression>
                  </Criteria>
                  <ExpirationStartTime>06/18/2009 13:58:54</ExpirationStartTime>
                  <PollingIntervalMinutes>1</PollingIntervalMinutes>
                  <UserSid>S-1-5-21-1085031214-1078081533-725345543-210845</UserSid>
                  <LanguageCode>ENU</LanguageCode>
                  <ExcludeNonNullConnectorIds>false</ExcludeNonNullConnectorIds>
                  <RuleId>$MPElement$</RuleId>
                  <TargetBaseManagedEntityId>$Target/Id$</TargetBaseManagedEntityId>
                  <TimeZone>2C01000000000000C4FFFFFF00000B0000000100020000000000000000000300000002000200000000000000|Eastern Standard Time</TimeZone>
                </AlertChangedSubscription>
              </DataSource>
            </DataSources>
            <ConditionDetection ID="CD1" TypeID="Microsoft.SystemCenter.Notification.Recipients">
              <Recipients>
                <To>
                  <DirectoryReference>
                    <RecipientId>bee91da9-68f8-4c7a-a55d-8deff73f86d2</RecipientId>
                  </DirectoryReference>
                </To>
              </Recipients>
            </ConditionDetection>
            <WriteActions>
              <WriteAction ID="WA0" TypeID="SMTPAction_bf7ca42e_8065_48f1_a441_9a51c6e29ada" />
            </WriteActions>
          </Rule>

    ::marcus
    Friday, June 19, 2009 12:48 PM
    Moderator
  • rob - any progress?  i'm going to test this in my lab to see if the hotfix corrects this problem.
    ::marcus
    Monday, June 22, 2009 2:49 PM
    Moderator
  • Hi

    I think the problem might be here:
                            <ValueExpression>
                              <Property>Custom1</Property>
                            </ValueExpression>

    Take a look in the operationsmanager event log on the RMS for events 11402 .. I'm gettinng an error stating that the alert subscription data source module was unable to find alerts that match the subscription due to database errors ... Invalid propertyname custom1 ... notifications in general are working as it even emails me this error ;-)

    I haven't tried all the custom fields but filtering on custom field 3 has the same result.

    The database has the fields entitled "customfield1" etc ... is the query \ stored proc that is calling the notification querying a non-existant field??

    Cheers

    Graham 

    Tuesday, June 23, 2009 8:13 AM
    Moderator
  • hey graham -

    on the event rule, i'm pushing parameter 3 from the event into custom field 1.  on the notification sub, i'm using custom field 1 to do a wildcard match against the value.

    regarding the value "custom1" as opposed to "customfield1", i don't really know which is the correct one.  if customfield1 is the correct value, then there is a UI issue since the value for custom1 is being generated by the notification sub wizard.  :o

    found out exchange in the lab isn't working (surprise).  i can't test the email notifications at the moment to verify the hotfix noted earlier in this thread.

    ::marcus
    Tuesday, June 23, 2009 12:36 PM
    Moderator
  • Hi Marcus

    Just created a view based on a custom field and to be fair the xml uses <custom1> as well .... when you get your system back up and running take a look at the operations manager event log on the RMS when the notification should fire. I get  events 11402:

    "alert subscription data source module was unable to find alerts that match the subscription due to database errors ... Invalid propertyname custom1" (or custom3 if I try an alternative custom field).

    Might well be a bug.

    Cheers

    Graham
    Tuesday, June 23, 2009 2:07 PM
    Moderator
  • no 11402 on my end.  i'm going to use the command notification route and just code in smtp reactions to the custom1 value.  here we go...

    ::marcus
    Tuesday, June 23, 2009 2:47 PM
    Moderator
  • Hi Marcus

    As an update on this - I have had some feedback from MSFT support this morning and they can reproduce the problem. I'll try and keep the thread updated.

    Cheers

    Graham
    Friday, July 3, 2009 8:09 AM
    Moderator
  • good to know.  i ended up using the scripted approach for now: http://marcusoh.blogspot.com/2009/06/monitoring-group-changes-with-opsmgr.html.

    let me know how much traction you get with this.  still very interested.

    ::marcus
    Monday, July 6, 2009 1:34 PM
    Moderator
  • I had the same problem. I opened a case at Micrsoft. After investigating they confirmed that is is a bug.

    The following procedure can be used as a workaround until a hotfix is available

    1, Export the ‘Notifications Internal Library’ Management Pack.

    2, Increase the <Version>. For example:

    <Version>6.1.7221.1</Version>

     

    3, Locate the mistakes for each custom Field, which will look like:

     <SimpleExpression xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

                    <ValueExpression>

                                    <Property>Custom8</Property>

                    </ValueExpression>

                    <Operator>Equal</Operator>

    <ValueExpression>

                                    <Value>RobsTest</Value>

                     </ValueExpression>

      </SimpleExpression>

     

    4, Update this by changing Custom8 to CustomField8. For example:

    <SimpleExpression xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

                    <ValueExpression>

                                    <Property>CustomField8</Property>

                    </ValueExpression>

                    <Operator>Equal</Operator>

    <ValueExpression>

                                    <Value>RobsTest</Value>

                     </ValueExpression>

      </SimpleExpression>

     

    5, Save the file & import back into OpsMgr.

    Friday, July 10, 2009 6:00 PM