Hi,

I have a job with 3 tasks.

1) Stop a service.
2) Update the service software/configs - copies file to the service bin directory.
3) Restart service.

It is triggered by a simple trigger file in the source file directory.

However, if the service has already stopped for any reason, the job gets aborted with an unhandled exception error.

Is this by design or is there anyway to make it carry on with the job. I don't really want to create 2 jobs to do this as it then gets messy.

Any thoughts appreciated.

Thanks

Graham

You mean that the Restart service returns error if the service is already stopped?

---

No, the "service stop request" on a stopped service (task 1) causes the error.


Graham

Not sure if relevant, but this is on a remote server.

Graham

Ok, we have changed the behavior for the next version so it should not throw an error if it is already stopped. Thanks for reporting.

---

The start service command used to throw an error in version 4.9.40 if a service is already started.

Both these are fixed in version 5.0.0.

---

What if the service is already started. In the version I am running, if a service is already started, and an attempt is made to start the service then it returns an error, which should probably not be the case.

I am quite sure we fixed both. Which version are you running now?

---

4.9.40

I am 99% sure that this is fixed as well.

---

I have a couple of tasks in a row.

This is the stderr from one of them which starts the sqlagent on remote system:

Unhandled exception in Task: Cannot start service SQLSERVERAGENT on computer 'server.local.domain.com'.



Then a bit later I run another task to execute a sql agent job which returns the output:

Job 'backup_cubes' started successfully.
1>

The agent is started somehow or another given that I am able to run a sql agent job.

This is SQL server 2005, Windows 2003 x64.

What is the exception? Normally the exception is stored in stderr or stdout column.

I have a couple of tasks in a row.

This is the stderr from one of them which starts the sqlagent on remote system:

Unhandled exception in Task: Cannot start service SQLSERVERAGENT on computer 'server.local.domain.com'.



Then a bit later I run another task to execute a sql agent job which returns the output:

Job 'backup_cubes' started successfully.
1>

The agent is started somehow or another given that I am able to run a sql agent job.

This is SQL server 2005, Windows 2003 x64.

---

The output says "No Output"

Stderr and Result contain:

Unhandled exception in Task: Cannot start service SQLSERVERAGENT on computer 'server.local.domain.com'.

Do you see any other error in the log?

The output says "No Output"

Stderr and Result contain:

Unhandled exception in Task: Cannot start service SQLSERVERAGENT on computer 'server.local.domain.com'.

---

3/30/2009 4:07:05 AM Debug Task (3115) was added to processlist: Start SQL Agent
3/30/2009 4:07:05 AM Info Task started: Start SQL Agent
3/30/2009 4:07:05 AM Debug Running SQL Notification: 'Job Start - job_stats table on egovern'
3/30/2009 4:07:05 AM Debug Running SysLog Notification: 'Syslog: Task Start'
3/30/2009 4:07:06 AM Err Unhandled exception in Task: Cannot start service SQLSERVERAGENT on computer 'server.local.domain.com'.
3/30/2009 4:07:06 AM Info Task completed: Start SQL Agent
3/30/2009 4:07:06 AM Debug Setting previous task in TaskProcessCompleted: Start SQL Agent (9206776d-c727-483f-baf7-e421b8a37996) in job: Internal_Backup_PRD_ALL_Cubes_Daily_Full
3/30/2009 4:07:06 AM Debug Process status - About to SendTaskProcess (3115)
3/30/2009 4:07:06 AM Debug Process status - About to RemoveTaskProcess (3115)
3/30/2009 4:07:06 AM Debug Task (3115) was removed from processlist: Start SQL Agent
3

See attached screenshot.

Did you try the latest version? Seems like you get the error because it is already running?

---

As stated at the beginning of this thread, we were on 4.9.40. If there has been a bug fix for this release or is this in the 5.x series?

Yes, this was fixed in version 5.0.0.

As stated at the beginning of this thread, we were on 4.9.40. If there has been a bug fix for this release or is this in the 5.x series?

---