Problem with SQL Agent using Database Mail

All,
I posted this message to a thread dated 11/25/2004... I guess I should have
started a new thread.
Anyway, I am having a problem with database mail and the SQL agent. The
error from the maintenance history notification step is:
Executing the query "EXECUTE msdb.dbo.sp_notify_operator
@.name=N'JimmyV',@.body=N'Database Verification Failed!'
" failed with the following error: "No global profile is configured. Specify
a profile name in the @.profile_name parameter.". Possible failure reasons:
Problems with the query, "ResultSet" property not set correctly, parameters
not set correctly, or connection not established correctly.
I've configured the database mail system, created a database mail account
and profile which is the default for the agent. I created the agent user
account in msdb in the DatabaseMailUser role. And I've created the operator.
I've also tried public default profiles and they fail too.
I can send test messages from Database Mail.
The interseting thing is that the 'Test' button is dimmed on the SQL Agent,
Alert System, Mail Session page even though the correct profile is selected!
Please, any help will be greatly appreciated.
Thanks,
Jim
I had a somewhat similar problem. In my case, I assigned the operators
and the Notification recipients prior to configuring the SQL Agent to
use Database Mail. Even though the jobs were set to notify on
completion (success/failure), I never received any e-mails. However,
restarting the SQL Agent service fixed it.
-Prabhakar
JimmyV wrote:
> All,
> I posted this message to a thread dated 11/25/2004... I guess I should have
> started a new thread.
> Anyway, I am having a problem with database mail and the SQL agent. The
> error from the maintenance history notification step is:
> Executing the query "EXECUTE msdb.dbo.sp_notify_operator
> @.name=N'JimmyV',@.body=N'Database Verification Failed!'
> " failed with the following error: "No global profile is configured. Specify
> a profile name in the @.profile_name parameter.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameters
> not set correctly, or connection not established correctly.
> I've configured the database mail system, created a database mail account
> and profile which is the default for the agent. I created the agent user
> account in msdb in the DatabaseMailUser role. And I've created the operator.
> I've also tried public default profiles and they fail too.
> I can send test messages from Database Mail.
> The interseting thing is that the 'Test' button is dimmed on the SQL Agent,
> Alert System, Mail Session page even though the correct profile is selected!
> Please, any help will be greatly appreciated.
> Thanks,
> Jim
|||Do you have Outlook installed on your server? I believe that it is required
to create the profiles that can be assigned in the server properties and in
the SQL Agent properties. After you install Outlook, go to the control
panel and create a profile on the server using the account the SQL Server
service uses. You then should be able to assign the profile to both the
server mail properties and the SQL Agent properties.
If you have Outlook installed, use Query analyzer and try sending an email
message using xp_sendmail. If you get an error message, issue the following
commands...
exec xp_stopmail
exec xp_startmail
This should get you started in trying to get SQL mail to work for you on
your server.
"preddy" <prvangala@.gmail.com> wrote in message
news:1138730276.706755.82690@.f14g2000cwb.googlegro ups.com...
>I had a somewhat similar problem. In my case, I assigned the operators
> and the Notification recipients prior to configuring the SQL Agent to
> use Database Mail. Even though the jobs were set to notify on
> completion (success/failure), I never received any e-mails. However,
> restarting the SQL Agent service fixed it.
> -Prabhakar
> JimmyV wrote:
>
|||> Do you have Outlook installed on your server?
Database Mail (in contrast to SQL Mail) does *not* need Outlook as it isn't using MAPI. Database
mail makes SMTP calls, so it is only dependent on TCP being available. Database Mail is new to SQL
Server 2005.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Scott Cupstid" <scupstid@.tampabay.rr.com> wrote in message news:drob90$2chn$1@.news3.infoave.net...
> Do you have Outlook installed on your server? I believe that it is required to create the
> profiles that can be assigned in the server properties and in the SQL Agent properties. After you
> install Outlook, go to the control panel and create a profile on the server using the account the
> SQL Server service uses. You then should be able to assign the profile to both the server mail
> properties and the SQL Agent properties.
> If you have Outlook installed, use Query analyzer and try sending an email message using
> xp_sendmail. If you get an error message, issue the following commands...
> exec xp_stopmail
> exec xp_startmail
> This should get you started in trying to get SQL mail to work for you on your server.
> "preddy" <prvangala@.gmail.com> wrote in message
> news:1138730276.706755.82690@.f14g2000cwb.googlegro ups.com...
>
|||I tried what you suggested and unfortunately it still fails in the same way.
The really strange thing is that the 'Test' button will not activate; telling
me something is still wrong.
Jim
"preddy" wrote:

> I had a somewhat similar problem. In my case, I assigned the operators
> and the Notification recipients prior to configuring the SQL Agent to
> use Database Mail. Even though the jobs were set to notify on
> completion (success/failure), I never received any e-mails. However,
> restarting the SQL Agent service fixed it.
> -Prabhakar
> JimmyV wrote:
>