Sunday, March 11, 2012

Error: 14258

Hi Guru,
I just found out that one of my SQL 2005 reporting server is
experiencing this issue.
"Error 14258: Cannot perform this operation while SQLServerAgent is
starting. Try again later."
I've seen lots people fixed this issue by switching to thread mode.
However, the server has only 1 CPU and of course is running on default
configuration(thread mode).
We had a vendor used their tool (JAVA BASED) to pull data from Oracle
to SQL Server. I terminated this process a week ago when I found out
this tool would take three weeks to import 18 million records from
Oracle to SQL Server. SQL Server has been rolling back more than a week
and expecting a few more days to be completed.
Is this rolling back causing error 14258?
Thanks so much,Not likely from the rollback but more likely from the SQL Agent
service being stuck in a starting state (as opposed to a started
state). Did you check the SQL Agent error log - the SQLAgent.out file
in the default log directory for your installation?
Did you try restarting SQL Agent?
Did you check the System event log on the server where SQL Agent is
suppose to be running and check for any errors related to the service?
-Sue
On 21 Nov 2006 10:28:57 -0800, smounkhaty@.bremer.com wrote:

>Hi Guru,
>I just found out that one of my SQL 2005 reporting server is
>experiencing this issue.
>"Error 14258: Cannot perform this operation while SQLServerAgent is
>starting. Try again later."
>I've seen lots people fixed this issue by switching to thread mode.
>However, the server has only 1 CPU and of course is running on default
>configuration(thread mode).
>We had a vendor used their tool (JAVA BASED) to pull data from Oracle
>to SQL Server. I terminated this process a week ago when I found out
>this tool would take three weeks to import 18 million records from
>Oracle to SQL Server. SQL Server has been rolling back more than a week
>and expecting a few more days to be completed.
>Is this rolling back causing error 14258?
>Thanks so much,|||Sue,
Thanks very much for your response. Below is the output from
SQLAgent.out file. I veriffied SQLAGENT is running from:
Configuration Manager - Started
Serice Applet - Started
EXEC master..xp_servicecontrol 'QueryState','SQLServerAgent' status is
running.
GO
I stopped and restart agent many times with both NT domain and
localsystem account but nothing worked.
Other than that, I don't see any related errors on both NT and SQL
logs.
Please let me know if you have different thoughts now.
Thanks,
2006-11-21 09:59:05 - ? [393] Waiting for SQL Server to recover
databases...
Sue Hoegemeier wrote:[vbcol=seagreen]
> Not likely from the rollback but more likely from the SQL Agent
> service being stuck in a starting state (as opposed to a started
> state). Did you check the SQL Agent error log - the SQLAgent.out file
> in the default log directory for your installation?
> Did you try restarting SQL Agent?
> Did you check the System event log on the server where SQL Agent is
> suppose to be running and check for any errors related to the service?
> -Sue
> On 21 Nov 2006 10:28:57 -0800, smounkhaty@.bremer.com wrote:
>|||Still not from the rollback...The error in general is almost
always related to a configuration issue. Other things you
would want to check -
Verify that lightweight pooling is not enabled again - run
sp_configure and check the run value and the config value
for lightweight pooling. The run value for this one is
important as if it's different from the config value, a
restart of SQL Server is needed on this configuration for
changes to take effect.
Also remove any mail profile associated with Agent Mail.
You most likely have some hints or clues in the SQLAgent.out
file.
The other thing I've seen cause problems is the service
account used to run SQL Agent. Have you tried creating a new
domain account to use for the service?
-Sue
On 21 Nov 2006 12:26:33 -0800, smounkhaty@.bremer.com wrote:
[vbcol=seagreen]
>Sue,
>Thanks very much for your response. Below is the output from
>SQLAgent.out file. I veriffied SQLAGENT is running from:
>Configuration Manager - Started
>Serice Applet - Started
>EXEC master..xp_servicecontrol 'QueryState','SQLServerAgent' status is
>running.
>GO
>I stopped and restart agent many times with both NT domain and
>localsystem account but nothing worked.
>Other than that, I don't see any related errors on both NT and SQL
>logs.
>Please let me know if you have different thoughts now.
>Thanks,
>2006-11-21 09:59:05 - ? [393] Waiting for SQL Server to recover
>databases...
>Sue Hoegemeier wrote:

No comments:

Post a Comment