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
Showing posts with label agent. Show all posts
Showing posts with label agent. Show all posts
Wednesday, March 28, 2012
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
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
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
Monday, March 12, 2012
Problem notifying operator SS2005
Hi there!
I expercience some problems in sending the alert mails to the operator when an Agent Failure Alert happens.
I have setup MSSQL 2005 with merge replication and have setup mail the ss2005 way. I also can send test mails via the Database mail context menu.
I have setup a operator with a valid emailadress and enabled is checked
On the notifications page 'Agent Failure Alert' is checked.
When this alert fires the number of occurences in the history of this alert is incremented (as I can see via the alertsection-Agentfailure-history) this alert is also enabled. The problem is that the operator does not get notified!
So I can send test email from the DB, have setup an Operator with emailadress, have enabled an alert and see the number of occurences of this alert increment. I don't get any alert mails. The notifications attempt in the history page of the operator does not increment. It says: [never emailed]
Well I hope you can help!
Sincerley
Edward
Problem solved.
The SQL Agent still needed a pointer to the mailservice.
|||Can someone please explain this to me ... I am having the exact same problem mentioned above (test emails work with database mail but jobs do not actually show any attempt to sed notifications).
I do not understand what is meant by "SQL Agent still needs a pointer to the mailservice".
Problem notifying operator SS2005
Hi there!
I expercience some problems in sending the alert mails to the operator when an Agent Failure Alert happens.
I have setup MSSQL 2005 with merge replication and have setup mail the ss2005 way. I also can send test mails via the Database mail context menu.
I have setup a operator with a valid emailadress and enabled is checked
On the notifications page 'Agent Failure Alert' is checked.
When this alert fires the number of occurences in the history of this alert is incremented (as I can see via the alertsection-Agentfailure-history) this alert is also enabled. The problem is that the operator does not get notified!
So I can send test email from the DB, have setup an Operator with emailadress, have enabled an alert and see the number of occurences of this alert increment. I don't get any alert mails. The notifications attempt in the history page of the operator does not increment. It says: [never emailed]
Well I hope you can help!
Sincerley
Edward
Problem solved.
The SQL Agent still needed a pointer to the mailservice.
|||Can someone please explain this to me ... I am having the exact same problem mentioned above (test emails work with database mail but jobs do not actually show any attempt to sed notifications).
I do not understand what is meant by "SQL Agent still needs a pointer to the mailservice".
Subscribe to:
Posts (Atom)