Error 14258: Cannot perform this operation while SQLServerAgent is starting. Try again later.

I'm getting the following error on two of my SQL Servers -

Error 14258: Cannot perform this operation while SQLServerAgent is starting. Try again later.

The only solution that I have seen is the same solution that Microsoft has published in the following article - KB303287 [http://support.microsoft.com/?scid=http%3a%2f%2fwww.support.microsoft.com%2fkb%2f303287%2fen-us%2f]

The solution is to unflag the use of NT Fibers. However, our software application provider is advising us against doing this. Is there another fix anywhere that I could get my hands on - another solution?

Thanks in advance.

SQLAgent jobs fails because of the reason that it waits for event to signal recovery is complete.

Currently the only solution is to switch to thread mode.

http://msdn.microsoft.com/sql/default.aspx?pull=/library/en-us/dnsqldev/html/sqldev_02152005.asp

Above article recommends that you stay away from fiber mode and focus your tuning efforts on other things. If you run into a situation where you feel strongly you need fiber mode, it's probably worth a call into Microsoft Product Support Services to confirm your diagnosis.

Thanks,

Gops Dwarak

|||

Thanks very much for the reply and for the extra information as well. My situation actually started when we attempted to create and use a local machine account to run the SQLSERVERAGENT service. I'm not sure if this brings more into play or not. I took the service back to using a different priviledged domain account to run the service and I'm not getting the errors currently.

I would, however, much rather run this service as a local user for security reasons. I have not yet taken a fresh look at Microsoft's best practices on this issue [the service account], but I will be taking a look at that as well.

thanks again.

|||

We are having the same problem with our SQL Server Agent as well, and our started when we switched from the system account to a user account that was setup specifically for SQL.

Our server has 4 processors so I think that is why the server was originally flagged to run in fiber mode, however, I think we are going to have to switch back to thread mode because there are so many processes that this is killing by staying in fiber mode.

Anyway, if you have found out any further information on this subject I would greatly appreciate any advice you might have.

Thanks,

Lee

|||

We are having the same problem with our SQL Server Agent as well,

The server is NOT flagged to run in fiber mode

Do you know how to fix it?

Thanks,

Oleg

|||

As mentioned above in the posts, change the log on account from local system account to a specified account, even if its the same account that you are signed on to the server. Worked like a charm for me..

thanks guys...

|||

Oleg

Have you referred to the article above and steps defined.

Also if you are using distributed transactions its might worth to enable the mSDTC to auto start.

|||

Right on! How Fibre Mode got switched on will be vexing me now. At least server agent is running and I can see what is going on. When server agent hangs with a 14258, it seems to be running in enterprise manager but none of my jobs show a history from the point of failure.

I may have popped on the checkbox when i was looking at sql server properties. When the server was bounced last week to finish a patch the agent did not come back when Fibre Mode was enabled and hung all my agent jobs. That's the best I can do. Careful when you browse a production machine... I have DTS packages running on shedule so this turned out to be a big deal.

I will see tomorrow if everything runs ok. At least the error is clear when I try to edit the jobs. I would think a melitious attack to have caused real damage so I blame myself. Nothing in the security logs tells me any different. Thanks.

Error 14258: Cannot perform this operation while SQLServerAgent is starting. Try again later.

I'm getting the following error on two of my SQL Servers -

Error 14258: Cannot perform this operation while SQLServerAgent is starting. Try again later.

The only solution that I have seen is the same solution that Microsoft has published in the following article - KB303287 [http://support.microsoft.com/?scid=http%3a%2f%2fwww.support.microsoft.com%2fkb%2f303287%2fen-us%2f]

The solution is to unflag the use of NT Fibers. However, our software application provider is advising us against doing this. Is there another fix anywhere that I could get my hands on - another solution?

Thanks in advance.

SQLAgent jobs fails because of the reason that it waits for event to signal recovery is complete.

Currently the only solution is to switch to thread mode.

http://msdn.microsoft.com/sql/default.aspx?pull=/library/en-us/dnsqldev/html/sqldev_02152005.asp

Above article recommends that you stay away from fiber mode and focus your tuning efforts on other things. If you run into a situation where you feel strongly you need fiber mode, it's probably worth a call into Microsoft Product Support Services to confirm your diagnosis.

Thanks,

Gops Dwarak

|||

Thanks very much for the reply and for the extra information as well. My situation actually started when we attempted to create and use a local machine account to run the SQLSERVERAGENT service. I'm not sure if this brings more into play or not. I took the service back to using a different priviledged domain account to run the service and I'm not getting the errors currently.

I would, however, much rather run this service as a local user for security reasons. I have not yet taken a fresh look at Microsoft's best practices on this issue [the service account], but I will be taking a look at that as well.

thanks again.

|||

We are having the same problem with our SQL Server Agent as well, and our started when we switched from the system account to a user account that was setup specifically for SQL.

Our server has 4 processors so I think that is why the server was originally flagged to run in fiber mode, however, I think we are going to have to switch back to thread mode because there are so many processes that this is killing by staying in fiber mode.

Anyway, if you have found out any further information on this subject I would greatly appreciate any advice you might have.

Thanks,

Lee

|||

We are having the same problem with our SQL Server Agent as well,

The server is NOT flagged to run in fiber mode

Do you know how to fix it?

Thanks,

Oleg

|||

As mentioned above in the posts, change the log on account from local system account to a specified account, even if its the same account that you are signed on to the server. Worked like a charm for me..

thanks guys...

|||

Oleg

Have you referred to the article above and steps defined.

Also if you are using distributed transactions its might worth to enable the mSDTC to auto start.

Error 14258: Cannot perform this operation while SQLServerAgent is starting. Try again later.

I'm getting the following error on two of my SQL Servers -

Error 14258: Cannot perform this operation while SQLServerAgent is starting. Try again later.

The only solution that I have seen is the same solution that Microsoft has published in the following article - KB303287 [http://support.microsoft.com/?scid=http%3a%2f%2fwww.support.microsoft.com%2fkb%2f303287%2fen-us%2f]

The solution is to unflag the use of NT Fibers. However, our software application provider is advising us against doing this. Is there another fix anywhere that I could get my hands on - another solution?

Thanks in advance.

SQLAgent jobs fails because of the reason that it waits for event to signal recovery is complete.

Currently the only solution is to switch to thread mode.

http://msdn.microsoft.com/sql/default.aspx?pull=/library/en-us/dnsqldev/html/sqldev_02152005.asp

Above article recommends that you stay away from fiber mode and focus your tuning efforts on other things. If you run into a situation where you feel strongly you need fiber mode, it's probably worth a call into Microsoft Product Support Services to confirm your diagnosis.

Thanks,

Gops Dwarak

|||

Thanks very much for the reply and for the extra information as well. My situation actually started when we attempted to create and use a local machine account to run the SQLSERVERAGENT service. I'm not sure if this brings more into play or not. I took the service back to using a different priviledged domain account to run the service and I'm not getting the errors currently.

I would, however, much rather run this service as a local user for security reasons. I have not yet taken a fresh look at Microsoft's best practices on this issue [the service account], but I will be taking a look at that as well.

thanks again.

|||

We are having the same problem with our SQL Server Agent as well, and our started when we switched from the system account to a user account that was setup specifically for SQL.

Our server has 4 processors so I think that is why the server was originally flagged to run in fiber mode, however, I think we are going to have to switch back to thread mode because there are so many processes that this is killing by staying in fiber mode.

Anyway, if you have found out any further information on this subject I would greatly appreciate any advice you might have.

Thanks,

Lee

|||

We are having the same problem with our SQL Server Agent as well,

The server is NOT flagged to run in fiber mode

Do you know how to fix it?

Thanks,

Oleg

|||

As mentioned above in the posts, change the log on account from local system account to a specified account, even if its the same account that you are signed on to the server. Worked like a charm for me..

thanks guys...

|||

Oleg

Have you referred to the article above and steps defined.

Also if you are using distributed transactions its might worth to enable the mSDTC to auto start.

sql

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:

Error 14258

For the last two days I've been getting this error whenever I click on a Job
in Enterprise Manager:
Error 14258: Cannot perform this operation while SQLServerAgent is starting.
Try again later.
Any idea what is causing this? Agent appears to be running - it is
performing the assigned tasks on schedule.
I am also have a ongoing issue with this problem. Where you able to find
the root cause of this issue? Please let me know, as we are in bad need
of a solution to this problem.
Reply to thovorka@.quickutz.com
Thanks,
Todd
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Error 14258

For the last two days I've been getting this error whenever I click on a Job
in Enterprise Manager:
Error 14258: Cannot perform this operation while SQLServerAgent is starting.
Try again later.
Any idea what is causing this? Agent appears to be running - it is
performing the assigned tasks on schedule.I am also have a ongoing issue with this problem. Where you able to find
the root cause of this issue? Please let me know, as we are in bad need
of a solution to this problem.
Reply to thovorka@.quickutz.com
Thanks,
Todd
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Error 14258

For the last two days I've been getting this error whenever I click on a Job
in Enterprise Manager:
Error 14258: Cannot perform this operation while SQLServerAgent is starting.
Try again later.
Any idea what is causing this? Agent appears to be running - it is
performing the assigned tasks on schedule.Hi,
The SQLServerAgent has NOT started properly after a
shutdown/reboot two days ago. If you look at the service
manager, the service appears to have started, but its
really not.
Here is what you have to do:
Stop the SQLServerAgent (Not SQL Server)
Restart the service (make no errors are recorded)
Here is something else you may have not noticed, since
this error has been occurring, your scheduled jobs have
not run. You might want to backup your databases and run
any other jobs you may have.
hth
DeeJay
>--Original Message--
>For the last two days I've been getting this error
whenever I click on a Job
>in Enterprise Manager:
>Error 14258: Cannot perform this operation while
SQLServerAgent is starting.
>Try again later.
>Any idea what is causing this? Agent appears to be
running - it is
>performing the assigned tasks on schedule.
>
>.
>|||OK I've stopped and restarted the service several times. Event Viewer claims
the service started succesfully. Where else can I look for errors? The SQL
Server logs show no errors with the Agent. But you are correct - the jobs
are NOT running! Any other sugggestions on where to look for the problem?
"DeeJay Puar" <deejaypuar@.Yahoo.com> wrote in message
news:393601c48f89$d0181ff0$a501280a@.phx.gbl...
> Hi,
> The SQLServerAgent has NOT started properly after a
> shutdown/reboot two days ago. If you look at the service
> manager, the service appears to have started, but its
> really not.
> Here is what you have to do:
> Stop the SQLServerAgent (Not SQL Server)
> Restart the service (make no errors are recorded)
> Here is something else you may have not noticed, since
> this error has been occurring, your scheduled jobs have
> not run. You might want to backup your databases and run
> any other jobs you may have.
> hth
> DeeJay
> >--Original Message--
> >For the last two days I've been getting this error
> whenever I click on a Job
> >in Enterprise Manager:
> >
> >Error 14258: Cannot perform this operation while
> SQLServerAgent is starting.
> >Try again later.
> >
> >Any idea what is causing this? Agent appears to be
> running - it is
> >performing the assigned tasks on schedule.
> >
> >
> >.
> >|||I am also have a ongoing issue with this problem. Where you able to find
the root cause of this issue? Please let me know, as we are in bad need
of a solution to this problem.
Reply to thovorka@.quickutz.com
Thanks,
Todd
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!