Error 14258: ... FIXED !

I changed 'lightweight pooling' to 0, as you suggested, and after restarting
the server (just to make sure...) everything was back to normal !
Thank you very much for your time and invaluable help.
PS: by checking ERRORLOG I found out that the server did some database
recovering after the restart which immediately finished successfully, in
contrast to previous times when I was continously getting the error "[393]
Waiting for SQL Server to recover databases...". I don't know if that has to
do with the 'lightweight pooling' option change.
"Sue Hoegemeier" wrote:

> If you tried stopping and then restarting just the Agent
> service and it won't start, reporting the same error then my
> guess would be that you are running SQL Server in
> lightweight pooling mode. Set it back to the default of
> thread mode.
> sp_configure 'allow updates', 1
> go
> reconfigure with override
> go
> sp_configure 'lightweight pooling', 0
> go
> reconfigure with override
> go
> -Sue
Yes it was from the lightweight pooling change. You rarely
would change that setting - and as you saw changing default
settings can sometimes have adverse affects. The issues you
saw were all symptoms of problems from having lightweight
pooling on.
-Sue
On Tue, 21 Feb 2006 01:12:28 -0800, "vsiat"
<vsiat@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I changed 'lightweight pooling' to 0, as you suggested, and after restarting
>the server (just to make sure...) everything was back to normal !
>Thank you very much for your time and invaluable help.
>PS: by checking ERRORLOG I found out that the server did some database
>recovering after the restart which immediately finished successfully, in
>contrast to previous times when I was continously getting the error "[393]
>Waiting for SQL Server to recover databases...". I don't know if that has to
>do with the 'lightweight pooling' option change.
>
>"Sue Hoegemeier" wrote: