October 8, 2004 at 3:59 am
Hi,
As a test I disable SQLServerAgent and ran a set of nested Stored Procedures. The procs ran with out generating errors, but returned the following message, which is not custom and not in the sysmessages table:
‘SQLServerAgent is not currently running so it cannot be notified of this action.’
The question I have are as follows:
1) Where is the message coming from? - could it be from an extended sp such as ‘xp_sqlagent_notify’ which is called by one of the procs?
2) Why isn’t an error code passed back to the calling procedure?
3) Is there any way to capture the message that is returned so I can roll back the transaction?
Thanks
Jon
October 8, 2004 at 4:02 am
i guess u r very new to sql server, there is icon in the system tray, click on that
run the agent services.
mark it as run on the startup
this should help, any problem post again
<a href="http://www.websolsoftware.com"> For IT jobs click here</a>
*Sukhoi*[font="Arial Narrow"][/font]
October 8, 2004 at 4:12 am
sukhoi971,
I'm not new to SQL Server at all. I think you have misinterpreted my question. Nowhere did I ask how to run the agent service.
October 11, 2004 at 12:50 am
In the install directory the is a file instmsdb.sql which defines sp_sqlagent_notify which calls xp_sqlagent_notify.
It uses a flag @error_flag which may help.
This looks definitely undocumented !!
October 11, 2004 at 2:03 am
Thanks for that,
@error_flag does return an error code but so does @retval. I think it is a bug in sp_add_jobserver as it does not pick up the return value when calling sp_sqlagent_notify.
Jon
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply