| Event Id | 60018 |
| Source | NotificationServices |
| Description | A rule firing object state was not found in the extended stored procedure cache |
| Event Information | "According to Microsoft: Cause: 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. 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." |
| Reference Links | A rule firing object state was not found in the extended stored procedure cache |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.