|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Error 14258: ... SQL ServerAgent is startingWhenever I attempt to edit/run/... a scheduled job, I get the error message:
"Error 14258: Cannot perform this operation while SQL ServerAgent is starting. Try again later." I also notice that all scheduled jobs have "Date/time not available" in "Next Run Date". Of course Agent is not starting now, it has already started (Alerts and Operators can be edited without a problem). The server is SQL2000, SP4. Check the status of the service from Administrative Tools -
is the service Running or Starting? Alerts and operators can be edited without Agent running. Also check your Agent.out file. -Sue On Thu, 16 Feb 2006 03:55:29 -0800, "vsiat" <vs***@discussions.microsoft.com> wrote: Show quoteHide quote >Whenever I attempt to edit/run/... a scheduled job, I get the error message: >"Error 14258: Cannot perform this operation while SQL ServerAgent is >starting. Try again later." >I also notice that all scheduled jobs have "Date/time not available" in >"Next Run Date". > >Of course Agent is not starting now, it has already started (Alerts and >Operators can be edited without a problem). The server is SQL2000, SP4. The service IS running. I restarted it to make sure though, as I also did
with the server and the machine; nothing worked. The service is reported to be running in both enterprise manager and windows services but no scheduled jobs can be edited/run/...etc. Also, when I stop the service I can edit jobs or create new ones, but there is no way to run them. There is no Agent.out file. Show quoteHide quote "Sue Hoegemeier" wrote: > Check the status of the service from Administrative Tools - > is the service Running or Starting? > Alerts and operators can be edited without Agent running. > Also check your Agent.out file. > > -Sue ok, I checked SQLAgent.out file. It has one entry:
"... ? [393] Waiting for SQL Server to recover databases..." but I don't understand which databases it is recovering as there is no such indication in SQL server logs or Current activity. Show quoteHide quote "Sue Hoegemeier" wrote: > Check the status of the service from Administrative Tools - > is the service Running or Starting? > Alerts and operators can be edited without Agent running. > Also check your Agent.out file. > > -Sue 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 On Fri, 17 Feb 2006 00:41:28 -0800, "vsiat" <vs***@discussions.microsoft.com> wrote: Show quoteHide quote >ok, I checked SQLAgent.out file. It has one entry: >"... ? [393] Waiting for SQL Server to recover databases..." > >but I don't understand which databases it is recovering as there is no such >indication in SQL server logs or Current activity. > > >"Sue Hoegemeier" wrote: > >> Check the status of the service from Administrative Tools - >> is the service Running or Starting? >> Alerts and operators can be edited without Agent running. >> Also check your Agent.out file. >> >> -Sue 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. Show quoteHide quote "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" <vs***@discussions.microsoft.com> wrote: Show quoteHide quote >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  
Other interesting topics
|
|||||||||||||||||||||||
