Database Mail

  • On my SQL 2005 I have configured Database Mail and I can send email notifications from Management Studio using an SMPT profile.  I created a test job to test it but am unable to get it to send me notification upon successful or failure completion. 

    The SQL Server Agent does not allow me (it ghosts the otpion) to test the profile.  Any ideas??

     

    Thanks, 

  • This was removed by the editor as SPAM

  • Did you create an Operator and assign the server to send mail to the operator upon completion?

  • Ivan,

    the fact that SQL Agent grey's out the Test button seems to be some bug in Management Studio, I have the same problem even after installing SP1.

    About SQL Agent not sending job notifications, you need to restart the Agent service after you make changes to the database mail profile or account or if you add a new profile.

    Hope this helps

    Markus 

    [font="Verdana"]Markus Bohse[/font]

  • Thank you all for your reply.  It turns out that I was using Local System Account rather than a domain account for the SQL Server Agent service.   Once I made the appropriate change I was able to send e-mails successfully.

    Once again, thank you all.

    Ivan

     

  • Hello,

    I'm getting the same problem.  The only issue is we have 3 cluster servers running 64-bit and, for some reason, the one that is running most of the jobs and is the distributor for our replication, cannot send an email via job notification.  The other two clusters work fine.

    We have dropped and added everything a couple of times and restarted SQL Server Agent.  I checked and the SQL Server Agent is running under the domain account.  But we still get "[264] An attempt was made to send an email when no email session has been established" in the SQL Server Agent log.  Also have a "[355] The mail system failed to initialize; check configuration settings" error, but I was playing with switching it to SQLMail, so this might be erroneous.

    Any help would be appreciated.

  • Never mind.  I just noticed the version on the cluster that is failing is 1399, not 2047.

Viewing 7 posts - 1 through 6 (of 6 total)

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