July 22, 2009 at 1:15 pm
I recently modified our SQL Profiles and SQL Accounts because the previous DBA set it up under his email address instead of some generic address. When I get a message about a job failure, I'd like the sender to be something like sql@servername.com instead of joe@company.com. I completely removed his profile and account under the database mail configuration and sent a test mail with the GUI and I did indeed receive the message from sql@servername.com as I had changed it to. Yay!
Then I ran a couple of jobs and had it send me a notification upon completion and the sender of this message was joe@company.com. I double and triple-checked to make sure that I did indeed drop his profile and account from the database mail configuration and from what I can tell there's absolutely no reference to joe@company.com there.
I've tried dropping the maintenance plan along with its related jobs and re-creating it, but every time, it keeps picking up joe@company.com.
Can anyone give me any direction here? Am I missing some step? Does the SQL Agent operate under different mail configurations than Database Mail?
I tried restarting the agent and now no notification can be sent at all. I'm guessing this is because joe@company.com no longer exists in the Database Mail configuration anymore. The Database Mail test still works as expected.
Any help would be appreciated.
July 22, 2009 at 1:58 pm
Figured out my problem after poking around more on Google.
1. reconfigure the surface area
2. DISabling Database Mail stored procedures.
3. Restart SQL Agent
4. REenable Database mail.
July 22, 2009 at 2:46 pm
Thanks for posting the answer you found.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
July 24, 2009 at 11:43 am
I ran into this problem again on another one of our servers and attempted to use the solution I posted before and it did not fix the problem. So, after a little poking around with the server settings, I believe I found a solution that appears to work every time I've run into this error.
1. Make your changes to the Database Mail configuration as desired
2. Find your SQL Agent node in the SQL Server Management Studio, right click and choose Properties
3. Navigate to Alert System on the Left and uncheck the first box on that page for Enable mail profile
4. Click OK
5. Restart your agent service
6. Go back into the Alert System page and check the first box for Enable mail profile (make sure that the desired profile is selected in the drop-down)
7. Restart your agent service
This has worked for me every time that I've changed the profile/account information, so hopefully this might help someone else at some point.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply