The following information should be available if you click the link at the
bottom of the message in the Event Viewer.
A rule firing object state was not found in the extended stored procedure
cache.
Explanation
The generator fires event and scheduled rules by preparing and then firing
the rules. The preparation steps include creating views over the event and
subscription tables and adding a rule firing object to an internal cache
called the extended stored procedure cache. The running of notification
rules can then use those views and call the Notify function associated with
the notification class for which the notifications are generated.
However, if a Notify function is run outside the context of the generator,
the preparation steps do not occur, no rule firing object is created, and
the extended stored procedure cache is left in an unexpected state.
User Action
Do not run the notification functions outside the context of the generator.
If you want to test rules, copy the complete rule to Query Analyzer, remove
the notification function, and make the necessary table name changes before
running the rule.
For example, suppose you have the following event rule in your application
definition file (ADF):
SELECT dbo.FlightNotificationsNotify(S.SubscriberId,
S.DeviceName, S.SubscriberLocale, E.Carrier,
E.LeavingFrom, E.GoingTo, E.Price, E.Conditions)
FROM FlightEvents E, FlightSubscriptions S
WHERE E.LeavingFrom = S.LeavingFrom
AND E.GoingTo = S.GoingTo
AND ( (E.Carrier = S.Carrier) OR (S.Carrier = '*') )
AND E.Price < S.Price
You would change it as follows to test the rule in Query Analyzer:
SELECT S.SubscriberId, S.DeviceName, S.SubscriberLocale,
E.Carrier, E.LeavingFrom, E.GoingTo, E.Price,
E.Conditions
FROM NSFlightEventsEvents E, NSFlightSubscriptionsSubscriptions S
WHERE E.LeavingFrom = S.LeavingFrom
AND E.GoingTo = S.GoingTo
AND ( (E.Carrier = S.Carrier) OR (S.Carrier = '*') )
AND E.Price < S.Price
Even though running the notification function outside the context of the
generator causes events to be written to the application log, you should not
need to take corrective action. The generator should continue firing rules
according to its schedule.
If the events persist or notifications are not being generated, stop and
restart the Notification Services instance that is hosting the generator,
and stop and restart the SQL Server that is hosting the Notification
Services databases.
--
This posting is provided "AS IS" with
no warranties, and confers no rights.
Use of included script samples are
subject to the terms specified at
<a style='text-decoration: underline;' href="http://www.microsoft.com/info/cpyright.htm." target="_blank">http://www.microsoft.com/info/cpyright.htm.</a>
"Dave" <anonymous.RemoveThis@discussions.microsoft.com> wrote in message
news:04DD107C-5E2B-4DAB-B0A7-187FED4EBF27@microsoft.com...
> Unfortunately, there is no alternative but to post to this newsgroup.
>
> Did anybody ever solve this error message? We are seeing the same
message.
>
> Insert lonely sound of whistling wind here...
>
> Dave<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Notification Services error 60018 
FAQ
Profile
Private Messages
Log in
