Wednesday, March 21, 2012

Error 14258: ... SQL ServerAgent is starting

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.
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"
<vsiat@.discussions.microsoft.com> wrote:

>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.
"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.
"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"
<vsiat@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>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:

No comments:

Post a Comment