SQL ServerAgent Notifications

  • Assistance Please

    I have a couple of scheduled jobs that are failing to e-mail notifications on completion (via SQL Agent Mail).

    I can send a Test e-mail without any problems. I can run the jobs manually, and the e-mail notification works effectively.

    Left to run according to the schedule, and no e-mail notification is generated.

    Any assistance greatly appreciated.

    Thanks

  • Manual tests are probably run under your user context where as the automated schedules are running under the security context of the SQL Server instance. You need to verify that the instance has the right security settings to connect up & run email.

    ----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software

  • Hi,

    did you check that the job ran at all on schedule? Check in the job history for any messages. If the job ran on schedule but no email was received then check if email was generated and logs on your email server.

    Granted is correct, it should be authentication problem on any step: running the job itself, sending an email from Agent, accessing email server. Looks like your Windows account does have rights to do it.

    There are several places where authentication is defined: 1. Who runs the job on schedule in Agent: in the job properties on General tab Owner... and in the step properties on the Advanced tab Run As User...   2. What identity Agent  and SQL server are using to perform external tasks on behalf of your job. Which may very well depend on what account Agent is using to login to SQL Server. Which in turn depends on what is on the Connection tab of Agent properties. And check what are startup accounts of Agent and SQL Server. Check how proxy account is defined.

    I would start with Event Viewer on the server and check all 3 logs close to the scheduled time on any related messages.

    Yelena

    Regards,Yelena Varsha

  • Great answer. I should have thought to add all of that but didn't. Thanks for help.

    ----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply