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



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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C3B01A39-DC5B-419F-91DE-EA21CECDAB6B@xxxxxxxxxxxxxxxx
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 Windows
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:

<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
information
you might deem confidential.

--
Ciprian Gerea
SDE, SqlServer

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


"Jill" <Jill@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1242C8FE-C1ED-406A-AF6F-C8483C04A3A3@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B4F66222-5AD6-4832-8FCF-FAE8D1D78CDC@xxxxxxxxxxxxxxxx
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








.



Relevant Pages

  • Re: Network traffic with transactional replication with immediate updates (SQL 2005)
    ... publisher/distributor running on the main office and a subscriber at the ... This is a new SQL Server 2005 behaviour, ... the agent should execute them (maybe the agent just ... I cannot find a way to explain why Distributor Agents are to ...
    (microsoft.public.sqlserver.replication)
  • Re: Network traffic with transactional replication with immediate updates (SQL 2005)
    ... publisher/distributor running on the main office and a subscriber at the ... the agent should execute them (maybe the agent just launches ... Looking for a SQL Server replication book? ... I cannot find a way to explain why Distributor Agents are to ...
    (microsoft.public.sqlserver.replication)
  • Re: SQL Server 2005 replication monitor questions
    ... >> To get to the agents expand SQL Server Agent jobs, ... click on your publication in Enterprise ... >> bottom half you will see your snapshot and distribution agent. ... >> monitor it there (through replication monitor). ...
    (microsoft.public.sqlserver.replication)
  • Re: Server CE 2.0 Merge Replication
    ... This morning I am not able to access sscesa20.dll both from the emulator nor ... To change your connection settings, ... > your first goal should be to access the server agent from Pocket IE ... >> My SQL Server instance name be YYY ...
    (microsoft.public.sqlserver.ce)
  • Re: sp_replcmds
    ... It is possible that there is an open transaction ... Looking for a book on SQL Server replication? ... >> Stop SQL Server agent, restart it and see if this clears the error. ... Use Replication Monitor to view the details of> this ...
    (microsoft.public.sqlserver.replication)