This error message is logged when the Run() method does not return within
five minutes.
IEventProvider.Run() is not called within a thread by NS. As such, the Run()
method usually needs to start up its own thread, or fire up some CLR event
handlers.
-Colin
--
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
http://www.microsoft.com/info/cpyright.htm. Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
----------------------------------------------------------------------------
----------------------------------------------------
[quoted text, click to view] "Mark Weiss" <anonymous@discussions.microsoft.com> wrote in message
news:29ca801c465ce$e3e21750$a501280a@phx.gbl...
> What can cause this error to occur: "The application did
> not return in a timely manner from the Run method." The
> terribly unfortunate behavior in these circumstances is
> that NS shuts down the custom Event Provider that timed
> out. Even more unfortunate is that the process continues
> to run, but of course it doesn't do anything because the
> Event Provider is not running. What possible alternatives
> are there to handle this situation more robustly? I have
> all of the code in my Run method in a try/catch block, and
> I return true from the catch block. In this case I logged
> no exception -- the only error was the Notification
> Services-generated error about not returning in a timely
> manner. Can a simple database timeout cause this? Or can
> it only be caused by returing false from Run?