I have a task running a stored procedure on SQL Server. Very simple syntax, and the same SP runs perfectly fine from Query Analyzer, but keeps giving me a the following error in the 24x7 logs...

"Job Job_Name execution error. Exit code: -1. Database error occurred. Request has been cancelled."

I know this is a standard SQL Server error code, but I don't get this error when I run the job in any other program. So my question is: what is 24x7 seeing that triggeres this error?

Thanks,
Ryan

How do you connect to the database?
Did you set the AutoCommit option in the database profile?

: I have a task running a stored procedure on SQL Server. Very simple syntax,
: and the same SP runs perfectly fine from Query Analyzer, but keeps giving
: me a the following error in the 24x7 logs...

: "Job Job_Name execution error. Exit code: -1. Database error occurred.
: Request has been cancelled."

: I know this is a standard SQL Server error code, but I don't get this error
: when I run the job in any other program. So my question is: what is 24x7
: seeing that triggeres this error?

: Thanks,
: Ryan

: How do you connect to the database?
: Did you set the AutoCommit option in the database profile?

How do I connect? I setup a database profile in 24x7, used the odbc datasource that was already setup. Is that what you mean?
AutoCommit is turned on...should it be?
Also worth noting is that this DB task is one of many, and it's the only one that's having this issue. So my assumption is that it's something specific to this task. But I don't know what 24x7 is seeing (and causing to fail) that I'm not.
Thanks for your help.
Ryan

Please check if "Asynchronous operations" option is disabled in the database profile settings. If it is not - disable it and try again. Also set the job not to run as an asynchronous job.

If that does not help, turn on "database trace enabled" option in Tools/Options; Log.
Rerun the failed job and then user Log Viewer in 24x7 to view the generated log file. In that file you should be able to find what happens before the process is canceled or aborted.
After you are done with the trace analysis, turn off the trace option.

As a last resort you can turn on ODBC trace options in the ODBC Driver Manager.
The ODBC Driver Manager Trace tool records information about the ODBC API calls made by the 24x7 Scheduler while connected to an ODBC data source. ODBC Driver Manager Trace writes its output to a file named SQL.LOG (by default) located in the Windows home directory or to a log file that you specify. You can view the ODBC Driver Manager Trace log at any time by using any text editor.

: How do I connect? I setup a database profile in 24x7, used the odbc
: datasource that was already setup. Is that what you mean?
: AutoCommit is turned on...should it be?
: Also worth noting is that this DB task is one of many, and it's the only one
: that's having this issue. So my assumption is that it's something specific
: to this task. But I don't know what 24x7 is seeing (and causing to fail)
: that I'm not.
: Thanks for your help.
: Ryan

I disabled the "asynchronous operations" on the db profile, and set the task to asynchronous also. Worked perferctly. Thanks a lot.

: Please check if "Asynchronous operations" option is disabled in the
: database profile settings. If it is not - disable it and try again. Also
: set the job not to run as an asynchronous job.

: If that does not help, turn on "database trace enabled" option in
: Tools/Options; Log.
: Rerun the failed job and then user Log Viewer in 24x7 to view the generated
: log file. In that file you should be able to find what happens before the
: process is canceled or aborted.
: After you are done with the trace analysis, turn off the trace option.

: As a last resort you can turn on ODBC trace options in the ODBC Driver
: Manager.
: The ODBC Driver Manager Trace tool records information about the ODBC API
: calls made by the 24x7 Scheduler while connected to an ODBC data source.
: ODBC Driver Manager Trace writes its output to a file named SQL.LOG (by
: default) located in the Windows home directory or to a log file that you
: specify. You can view the ODBC Driver Manager Trace log at any time by
: using any text editor.