[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 69
  • Last Modified:

SQL server Database Mail Error-SQL Server 2008 R2

Hi there,
  I am receiving the following error when i try to run the Agent Job which tries to send an email.

Executed as user: UserXXX. The EXECUTE permission was denied on the object 'sp_send_dbmail', database 'msdb', schema 'dbo'. [SQLSTATE 42000] (Error 229).  The step failed.

Just for the test purpose, I have assigned the user-UserXXX to sysadmin privileges but still no luck.

I am running the job step Advanced->"Run as user -UserXXX' to execute this Job.

I have manually added the user UserXXX to the msdb database role 'DatabaseMailUserRole' also.

Have checked the sp_send_dbmail has the grant permission and the GranteeName- 'DatabaseMailUserRole'

Please let me know how to solve this issue?

thanks
Deepak
0
Deepak Kumar
Asked:
Deepak Kumar
  • 6
  • 5
2 Solutions
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Did you enable the Database Mail?
You can check that by running the following command:
exec sp_configure 'Database Mail XPs'

Open in new window

0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
If isn't enabled you can enable it by using the Database Mail Configuration Wizard:
DatabaseMailConfigure.PNG
0
 
Deepak KumarEngineerAuthor Commented:
Hi Vitor,
Thank you for your reply! When i ran the exec sp_configure 'Database Mail XPs'.I got the output.

name      minimum      maximum      config_value      run_value
Database Mail XPs      0      1      1      1

Please Note: Already database mail is working for other jobs which sends the DB mail.
I have configured this job to run as different User-UserXXX  using Advanced option in Job steps, because of this, I am getting this error.

thanks
Deepak
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Already database mail is working for other jobs which sends the DB mail.
What this job has different from the others? Only the user? The way it's sending emails? Other things?
0
 
Deepak KumarEngineerAuthor Commented:
The user has been changed -"Run as user" and Job Owner "to different user which again has sysadmin privileges".
0
 
Deepak KumarEngineerAuthor Commented:
Hi Vitor,
  I have executed this command which was found in forum , after which the job was executed as the user which i gave in "Run as user"

GRANT EXECUTE ON object::sp_send_dbmail TO DatabaseMailUserRole.

but i have few questions on the internal calls by SQL server when the db mail job had happened.

EXEC @rc = msdb.dbo.sysmail_verify_profile_sp
EXEC @retValue = sp_SendMailMessage @contract_name, @message_type, @message_data
EXEC @rc = sp_SendMailQueues @sendmailxml
EXEC @rc = msdb.dbo.sysmail_help_configure_value_sp @parameter_name = N'DatabaseMailExeMinimumLifeTime',
EXEC msdb.dbo.sysmail_help_configure_value_sp @parameter_name = N'ReadFromConfigurationFile',
                                                  @parameter_value = @parameter_value OUTPUT

Few of the above mentioned queries were captured in SQL profiler where the Login Name still shows as 'SA'

I have made the job owner to other user and also the run as "different user" but still i can see the internal queries were executed as 'SA'

Can you tell if i disable the 'SA' login what would the Login Name for this internal calls as opposed to 'SA' now?

thanks
Deepak
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Those are undocumented stored procedures and only users with sysadmin role can execute them. With that said this might mean that internally those SPs are using SA to run.

Documented SP is sp_send_dbmail and request less privileges.
0
 
Deepak KumarEngineerAuthor Commented:
Hi Vitor,
I have executed the Same job with the SA enbaled once and SA login disabled once and still found that the undocumented stored procedures related to DB mail are logged as 'SA' in  Login Name.

My question on this,
1)Is this the intended behaviour of SQL server to execute these undocumented SP's under the 'SA' Login?

2)Even after the 'SA' login is disabled, why the login name shows as 'SA' for these internal SP's?

Please help me on this as I must explain it to client with brief information.

thanks
Deepak
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
I don't know the answer for question 1 since I never worked with those SPs.
For question 2, SA sometimes can mean SQL Server account.
0
 
Deepak KumarEngineerAuthor Commented:
Hi Vitor,
   I have found why the System internall calls are logged as 'SA'. The main reason for this is due to the ownership of the msdb database which has the internal stored procedures.

I have tested it by changing the msdb database(in test environment) to other user who have sysadmin privileges . To my surprise those calls were called with the new database owner.

Anyway thanks vitor for your help!!

thanks
Mohan
0
 
Deepak KumarEngineerAuthor Commented:
I have given the test on my own to find out the real cause.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now