Forum Discussion

mdoll's avatar
mdoll
Frequent Visitor
9 years ago
Solved

EXECUTE Permission denied

I saw a similar post...but my issue is slightly different.

I am getting the failure on only one of two stored procs.

The service account is a dbo to the database

Other proc or views access tables from the ERP database using the same service account with no errors.

 

The EXECUTE permission was denied on the object 'proc_rpt_currencyexchangerates', database 'EF_DW', schema 'dbo'.

 

Microsoft.Data.Mashup.ValueError.Number:

229

  • Have you tried specifically granting EXEC rights to that service account in SQL?

     

    USE EF_DW
    GO
    GRANT
    Execute ON [dbo].proc_rpt_currencyexchangerates TO 'domain\service_account'

     

4 Replies

  • hugoberry's avatar
    hugoberry
    Responsive Resident

    Have you tried specifically granting EXEC rights to that service account in SQL?

     

    USE EF_DW
    GO
    GRANT
    Execute ON [dbo].proc_rpt_currencyexchangerates TO 'domain\service_account'

     

  • v-qiuyu-msft's avatar
    v-qiuyu-msft
    Community Support

    Hi mdoll,

     

    Which kind of database did you access in ERP system? From the error message, the issue occurs because the service account doesn't have execution permission on the object 'proc_rpt_currencyexchangerates'. You need to check the permission firstly on ERP side.

     

    Best Regards,
    Qiuyun Yu

    • mdoll's avatar
      mdoll
      Frequent Visitor

      Thanks everyone.....because of permissions granted to the service account, we didn't think we had to explicitly give it EXECUTE....but you were right...for whatever reason we have to.

      Thanks for the response.

       

      • heidibb's avatar
        heidibb
        Helper IV

        Hello,

        I know this is marked solved, but I am running into a similar issue and just wondered where the execute permissions need to be applied. I have my data connection as noted here and I'm getting the same "execute permission denied".

         

        Is this something I can fix within my desktop file or do I need our administrator to modify something his end?

         

         

        Thanks so much.