Problem restarting SQL Server Agent

We're running SQL Server 2000. Apparently the servers were restarted after
maintenance over the weekend (without telling me :-) and the SQL Server Job
Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
stops unexpectedly' is NOT set (and I'm not sure I have the authority to
change this option).
There were two messages in the Agent Error Log that appear relevant and
happened at about the same time..
[240] 1 engine thread(s) failed to stop after 30 seconds of waiting
[311] Thread 'JobInvocationEngine' (ID 3812) is still running
Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
automatically during a normal server startup? Also please define
'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)
Hi
"B. Chernick" wrote:

> We're running SQL Server 2000. Apparently the servers were restarted after
> maintenance over the weekend (without telling me :-) and the SQL Server Job
> Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
> stops unexpectedly' is NOT set (and I'm not sure I have the authority to
> change this option).
> There were two messages in the Agent Error Log that appear relevant and
> happened at about the same time..
> [240] 1 engine thread(s) failed to stop after 30 seconds of waiting
> [311] Thread 'JobInvocationEngine' (ID 3812) is still running
> Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
> automatically during a normal server startup? Also please define
> 'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)
These errors look like they have occurred during shutdown and not startup!
Check on the server properties in the general tab for Autostart policies
when the Operating System starts that Autostart SQL Agent is set to start.
John
|||My apologies. It looks like I appended too soon. I am not a full time DBA.
The agent option was unchecked.
(Looks like the problem is administrative, not technical.)
"John Bell" wrote:

> Hi
> "B. Chernick" wrote:
>
> These errors look like they have occurred during shutdown and not startup!
> Check on the server properties in the general tab for Autostart policies
> when the Operating System starts that Autostart SQL Agent is set to start.
> John
sql

Problem restarting SQL Server Agent

We're running SQL Server 2000. Apparently the servers were restarted after
maintenance over the weekend (without telling me :-) and the SQL Server Job
Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
stops unexpectedly' is NOT set (and I'm not sure I have the authority to
change this option).
There were two messages in the Agent Error Log that appear relevant and
happened at about the same time..
[240] 1 engine thread(s) failed to stop after 30 seconds of waiting
[311] Thread 'JobInvocationEngine' (ID 3812) is still running
Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
automatically during a normal server startup? Also please define
'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)Hi
"B. Chernick" wrote:
> We're running SQL Server 2000. Apparently the servers were restarted after
> maintenance over the weekend (without telling me :-) and the SQL Server Job
> Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
> stops unexpectedly' is NOT set (and I'm not sure I have the authority to
> change this option).
> There were two messages in the Agent Error Log that appear relevant and
> happened at about the same time..
> [240] 1 engine thread(s) failed to stop after 30 seconds of waiting
> [311] Thread 'JobInvocationEngine' (ID 3812) is still running
> Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
> automatically during a normal server startup? Also please define
> 'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)
These errors look like they have occurred during shutdown and not startup!
Check on the server properties in the general tab for Autostart policies
when the Operating System starts that Autostart SQL Agent is set to start.
John|||My apologies. It looks like I appended too soon. I am not a full time DBA.
The agent option was unchecked.
(Looks like the problem is administrative, not technical.)
"John Bell" wrote:
> Hi
> "B. Chernick" wrote:
> > We're running SQL Server 2000. Apparently the servers were restarted after
> > maintenance over the weekend (without telling me :-) and the SQL Server Job
> > Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
> > stops unexpectedly' is NOT set (and I'm not sure I have the authority to
> > change this option).
> >
> > There were two messages in the Agent Error Log that appear relevant and
> > happened at about the same time..
> >
> > [240] 1 engine thread(s) failed to stop after 30 seconds of waiting
> > [311] Thread 'JobInvocationEngine' (ID 3812) is still running
> >
> > Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
> > automatically during a normal server startup? Also please define
> > 'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)
> These errors look like they have occurred during shutdown and not startup!
> Check on the server properties in the general tab for Autostart policies
> when the Operating System starts that Autostart SQL Agent is set to start.
> John

Problem restarting SQL Server Agent

We're running SQL Server 2000. Apparently the servers were restarted after
maintenance over the weekend (without telling me :-) and the SQL Server Job
Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
stops unexpectedly' is NOT set (and I'm not sure I have the authority to
change this option).
There were two messages in the Agent Error Log that appear relevant and
happened at about the same time..
[240] 1 engine thread(s) failed to stop after 30 seconds of waiting
[311] Thread 'JobInvocationEngine' (ID 3812) is still running
Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
automatically during a normal server startup? Also please define
'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)Hi
"B. Chernick" wrote:

> We're running SQL Server 2000. Apparently the servers were restarted afte
r
> maintenance over the weekend (without telling me :-) and the SQL Server Jo
b
> Agent failed to restart. The option to 'AutoRestart SQL Server Agent if i
t
> stops unexpectedly' is NOT set (and I'm not sure I have the authority to
> change this option).
> There were two messages in the Agent Error Log that appear relevant and
> happened at about the same time..
> [240] 1 engine thread(s) failed to stop after 30 seconds of waiting
> [311] Thread 'JobInvocationEngine' (ID 3812) is still running
> Can anyone explain to me what I'm seeing here? (Shouldn't the agent resta
rt
> automatically during a normal server startup? Also please define
> 'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)
These errors look like they have occurred during shutdown and not startup!
Check on the server properties in the general tab for Autostart policies
when the Operating System starts that Autostart SQL Agent is set to start.
John|||My apologies. It looks like I appended too soon. I am not a full time DBA.
The agent option was unchecked.
(Looks like the problem is administrative, not technical.)
"John Bell" wrote:

> Hi
> "B. Chernick" wrote:
>
> These errors look like they have occurred during shutdown and not startup!
> Check on the server properties in the general tab for Autostart policies
> when the Operating System starts that Autostart SQL Agent is set to start.
> John

Problem moving msdb

Hi,
I am trying to move the msdb database, I am following the MS technet
document. I have added trace flag "-T3608" to startup parameters,
restarted the SQL server, stopped the agent, detatached the msdb
successfully. I moved the mdf and ldf to the new location and I removed
trace flag and when restarted the SQL server is not starting up, I
checked Event log it is giving this error

17052 :Could not find database ID 3. Database may not be activated yet
or may be in transition.

Please help me
Thanks in advanceI believe that database ID 3 is the "model" database....Did you also
try and move the model database?|||(nate.vu@.gmail.com) writes:
> I believe that database ID 3 is the "model" database....Did you also
> try and move the model database?

Correct. msdb is dbid = 4.

Looks like Raj should restore the trace flag, and then check what he
actually moved.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Ah OK, it does sound like the model database has been moved then. From
memory, it has to be re-attached before msdb. Also, model must be
re-attached with the trace flag on but msdb should be re-attached with
the trace flag off...