April 15, 2009 at 4:39 pm
db mail is setup and working and the folowing runs and I get the email...
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'Public DBMail',
@recipients = 'yomama@somwhere.net',
@body = 'Test Body',
@subject = 'Test Subject';
SQL Server Agent setup with the "Enable mail profile" tik box checked. Cycled the service and the following runs and returns the "Maile queue." but I never get the email...
EXECUTE msdb.dbo.sp_notify_operator @name=N'Yomama',@body=N'testing SQL notifications'
On a SQL job set to notify via email using the profile name 'Public DBMail' and sending to operator 'Yomama', I never get the mail.
Any Ideas?
April 15, 2009 at 8:25 pm
April 16, 2009 at 10:02 am
"We enabled the SMTP service "
Huh? Why does the SMTP service need to be installed? I don't want to broaden the the vulnerability of my server by adding the SMTP service. Is this entirely necessary for DBMail to work in SQL 2008 x64?
One other item is I do not want to use any MAPI client either. This would require me to add Outlook Express to my 2008 x64 Windows server.
Anyone else have any ideas before I call M$?
April 16, 2009 at 10:09 am
The information you got is correct but it is not relevant to you hecause IIS7 comes without SMTP so yes you need another way to send SQL Server mail. I have to do some research and post back.
Kind regards,
Gift Peddie
April 16, 2009 at 10:12 am
Is the Profile set as Public and Default?
April 16, 2009 at 10:14 am
Yes it it is.
Also, for this test machine, it is the only profile.
April 16, 2009 at 10:31 am
Gift, I do not know very much about this, but firewall can be blocked port 25 ?
When we do this in my server W2K3, one of the questions was that...and our Infra Adm says when enabled smtp service the port is open..so if in IIS7 does not have a smtp service, the port 25 can be blocked ?
April 16, 2009 at 10:34 am
Windows Firewall is turned off. That was the first thing I shut off.
April 16, 2009 at 10:37 am
Huh? Why does the SMTP service need to be installed? I don't want to broaden the the vulnerability of my server by adding the SMTP service. Is this entirely necessary for DBMail to work in SQL 2008 x64?
I just used the instructions below to configure DBmail and yes SMTP information is required which is what IIS 6 and below provided free. However there is a free alternative for 10 or less users. The other alternative is to provide Exchange Server information which is not needed if you are running IIS SMTP service.
http://msdn.microsoft.com/en-us/library/ms175951.aspx
Kind regards,
Gift Peddie
April 16, 2009 at 10:42 am
When we do this in my server W2K3, one of the questions was that...and our Infra Adm says when enabled smtp service the port is open..so if in IIS7 does not have a smtp service, the port 25 can be blocked ?
I don't think port is the issue because if you use the intructions in the link below SMTP informations is required.
http://msdn.microsoft.com/en-us/library/ms175951.aspx
Kind regards,
Gift Peddie
April 16, 2009 at 10:42 am
Its good to know....Gift ...So..if i use W2k8 and i want to use database mail in sql server i need to install SMTP service like this link ?
http://www.itechtalk.com/thread2250.html
or use Exchange ....
Thats correct ?
April 16, 2009 at 10:44 am
That is correct but it was cause by what happened to you and other users who could not run IIS dependent features because Windows have disabled IIS.
Kind regards,
Gift Peddie
April 16, 2009 at 12:14 pm
Yes, DBMail works fine for me. SMTP info in the account is working.
But why doesn't the following work...
EXECUTE msdb.dbo.sp_notify_operator @name=N'YOMAMA',@body=N'testing SQL notifications'
April 16, 2009 at 12:23 pm
April 16, 2009 at 12:26 pm
Warren Peace (4/16/2009)
Yes, DBMail works fine for me. SMTP info in the account is working.But why doesn't the following work...
EXECUTE msdb.dbo.sp_notify_operator @name=N'YOMAMA',@body=N'testing SQL notifications'
sp_notify_operator ends up calling sp_send_dbmail, so it would seem that you either have an issue with the setup of your operator 'YOMAMA' or that you need to include the profile name parameter as well, since those are really the only two things that would make this call different from the one in your original post. Verify the operator is set up correctly and if so, try including the @profile_name parameter to sp_notify_operator.
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply