SQL Server 2005: Error 14258...SQL Server Agent is starting

When ever I try creating a job under SQL Server 2005 I get the error message
:
"Error 14258: cannot perform this operation while SQL Server Agent is
starting; try again later".

When you look under services the service looks like it has already started.
If you try stopping the SQL Server Service or the Agent service from the
services screen they both lock up because the agent will not stop.

I am running SQL Server 2005 on Windows server 2000 SP4 under NT security.

After checking technet I did notice the question from Vsiat which looked
like the same problem under SQL Server 2000 where the problem was light
weight pooling this is not my problem.

Has anyone got any ideas.
--
Jill

Did you look at the SqlAgent log? That should give more information about
the state of the agent service. You can find the log in the equivalent of

c:\Program Files\Microsoft SQL Server\MSSQL. 1\MSSQL\LOG\sqlagent
.out.

--
Ciprian Gerea
SDE, SqlServer

This posting is provided "AS IS" with no warranties, and confers no rights.


"Jill" <Jill@discussions.microsoft.com> wrote in message
news:B4F66222-5AD6-4832-8FCF- FAE8D1D78CDC@microso
ft.com...
> When ever I try creating a job under SQL Server 2005 I get the error
> message:
> "Error 14258: cannot perform this operation while SQL Server Agent is
> starting; try again later".
>
> When you look under services the service looks like it has already
> started.
> If you try stopping the SQL Server Service or the Agent service from the
> services screen they both lock up because the agent will not stop.
>
> I am running SQL Server 2005 on Windows server 2000 SP4 under NT security.
>
> After checking technet I did notice the question from Vsiat which looked
> like the same problem under SQL Server 2000 where the problem was light
> weight pooling this is not my problem.
>
> Has anyone got any ideas.
> --
> Jill

Ciprian,  The Sql Server Agent log doesn't contain anything out of the
ordinally other then SQL Server recovering databases as per the post from
vsiat.  i.e the agent.out file contain the same information as Vsiat's.


--
Jill


"Ciprian Gerea [MSFT]" wrote:

> Did you look at the SqlAgent log? That should give more information about
> the state of the agent service. You can find the log in the equivalent of
>
> c:\Program Files\Microsoft SQL Server\MSSQL. 1\MSSQL\LOG\sqlagent
.out.
>
> --
> Ciprian Gerea
> SDE, SqlServer
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>
> "Jill" <Jill@discussions.microsoft.com> wrote in message
> news:B4F66222-5AD6-4832-8FCF- FAE8D1D78CDC@microso
ft.com... 
>
>
>

I don't know what is the other post you're referring to, but can you share
the relevant log entries? Please make sure you don't include any information
you might deem confidential.

--
Ciprian Gerea
SDE, SqlServer

This posting is provided "AS IS" with no warranties, and confers no rights.


"Jill" <Jill@discussions.microsoft.com> wrote in message
news:1242C8FE-C1ED-406A-AF6F- C8483C04A3A3@microso
ft.com...
> Ciprian,  The Sql Server Agent log doesn't contain anything out of the
> ordinally other then SQL Server recovering databases as per the post from
> vsiat.  i.e the agent.out file contain the same information as Vsiat's.
>
>
> --
> Jill
>
>
> "Ciprian Gerea [MSFT]" wrote:
> 

Ciprian,
The contents of the output file is as follows:
'2006-01-20 10:56:12 - ? [393] Waiting for SQL Server to recover databas
es...
2006-01-20 10:56:23 - ? [100] Microsoft SQLServerAgent version 9.00.1399
.06
(x86 unicode retail build) : Process ID 1800
2006-01-20 10:56:23 - ? [101] SQL Server TESTSQL2\MSSQL2005 version
9.00.1399 (0 connection limit)
2006-01-20 10:56:23 - ? [102] SQL Server ODBC driver version 9.00.1399
2006-01-20 10:56:23 - ? [103] NetLib being used by driver is DBNETLIB.DL
L;
Local host server is TESTSQL2\MSSQL2005
2006-01-20 10:56:23 - ? [310] 2 processor(s) and 1015 MB RAM detected
2006-01-20 10:56:23 - ? [339] Local computer is TESTSQL2 running Windows
 NT
5.0 (2195) Service Pack 4
2006-01-20 10:56:26 - ? [432] There are 6 subsystems in the subsystems c
ache
2006-01-20 13:38:22 - ? [131] SQLAgent$MSSQL2005 service stopping due to
 a
stop request from a user, process, or the OS...'

regards
Jill


--
Jill


"Ciprian Gerea [MSFT]" wrote:

> I don't know what is the other post you're referring to, but can you share
> the relevant log entries? Please make sure you don't include any informati
on
> you might deem confidential.
>
> --
> Ciprian Gerea
> SDE, SqlServer
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>
> "Jill" <Jill@discussions.microsoft.com> wrote in message
> news:1242C8FE-C1ED-406A-AF6F- C8483C04A3A3@microso
ft.com... 
>
>
>

I don't know what happens to yesterdays post, put here is the output file
again.

The contents of the output file is as follows:
'2006-01-20 10:56:12 - ? [393] Waiting for SQL Server to recover databas
es...
2006-01-20 10:56:23 - ? [100] Microsoft SQLServerAgent version 9.00.1399
.06
(x86 unicode retail build) : Process ID 1800
2006-01-20 10:56:23 - ? [101] SQL Server TESTSQL2\MSSQL2005 version
9.00.1399 (0 connection limit)
2006-01-20 10:56:23 - ? [102] SQL Server ODBC driver version 9.00.1399
2006-01-20 10:56:23 - ? [103] NetLib being used by driver is DBNETLIB.DL
L;
Local host server is TESTSQL2\MSSQL2005
2006-01-20 10:56:23 - ? [310] 2 processor(s) and 1015 MB RAM detected
2006-01-20 10:56:23 - ? [339] Local computer is TESTSQL2 running Windows
 NT
5.0 (2195) Service Pack 4
2006-01-20 10:56:26 - ? [432] There are 6 subsystems in the subsystems c
ache
2006-01-20 13:38:22 - ? [131] SQLAgent$MSSQL2005 service stopping due to
 a
stop request from a user, process, or the OS...'

--
Jill


"Ciprian Gerea [MSFT]" wrote:

> <resending - I sent this reply yesterday but it seems it did not make it
> through>
>
> I don't know what is the other post you're referring to, but can you share
> the relevant log entries? Please make sure you don't include any informati
on
> you might deem confidential.
>
> --
> Ciprian Gerea
> SDE, SqlServer
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>
> "Jill" <Jill@discussions.microsoft.com> wrote in message
> news:1242C8FE-C1ED-406A-AF6F- C8483C04A3A3@microso
ft.com... 
>
>
>

The last entry in the log says that agent is stopping. This could happen for
a varity of reasons, most likely a configuration problem. Did it ever work?

--
Ciprian Gerea
SDE, SqlServer

This posting is provided "AS IS" with no warranties, and confers no rights.


"Jill" <Jill@discussions.microsoft.com> wrote in message
news:C3B01A39-DC5B-419F-91DE- EA21CECDAB6B@microso
ft.com...
>I don't know what happens to yesterdays post, put here is the output file
> again.
>
>   The contents of the output file is as follows:
> '2006-01-20 10:56:12 - ? [393] Waiting for SQL Server to recover
> databases...
> 2006-01-20 10:56:23 - ? [100] Microsoft SQLServerAgent version
> 9.00.1399.06
> (x86 unicode retail build) : Process ID 1800
> 2006-01-20 10:56:23 - ? [101] SQL Server TESTSQL2\MSSQL2005 version
> 9.00.1399 (0 connection limit)
> 2006-01-20 10:56:23 - ? [102] SQL Server ODBC driver version 9.00.1399
> 2006-01-20 10:56:23 - ? [103] NetLib being used by driver is DBNETLIB.
DLL;
> Local host server is TESTSQL2\MSSQL2005
> 2006-01-20 10:56:23 - ? [310] 2 processor(s) and 1015 MB RAM detected
> 2006-01-20 10:56:23 - ? [339] Local computer is TESTSQL2 running Windo
ws
> NT
> 5.0 (2195) Service Pack 4
> 2006-01-20 10:56:26 - ? [432] There are 6 subsystems in the subsystems
> cache
> 2006-01-20 13:38:22 - ? [131] SQLAgent$MSSQL2005 service stopping due 
to a
> stop request from a user, process, or the OS...'
>
> --
> Jill
>
>
> "Ciprian Gerea [MSFT]" wrote:
> 

Not properly.  The only way you could try to start the service was to set it
as auto start when the server starts.  It looks like it starts OK, however
when you try to use it you get the error from SQL Server saying the agent is
starting try again.  If you have the service set as Manual and then manually
try to start it gets timed out.

Since adding this post I have managed to get the agent to work, however I'm
unsure what I did that maded it work.  I found an article on the web about
turning off unnecessary services which I did and after stopping and
restarting the server everything started working.   The article was called
How to perform a SQL Server Performance Audit by Brad M. McGehee.

--
Jill


"Ciprian Gerea [MSFT]" wrote:

> The last entry in the log says that agent is stopping. This could happen f
or
> a varity of reasons, most likely a configuration problem. Did it ever work
?
>
> --
> Ciprian Gerea
> SDE, SqlServer
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>
> "Jill" <Jill@discussions.microsoft.com> wrote in message
> news:C3B01A39-DC5B-419F-91DE- EA21CECDAB6B@microso
ft.com... 
>
>
>