Re: 'EXECUTE PERMISSION DENIED' on executing Sproc

From: Juan T. Llibre (nomailreplies_at_nowhere.com)
Date: 01/30/05


Date: Sun, 30 Jan 2005 09:32:45 -0400

Hi, Mike.

Actually, it does *not* have anything to do
with ASP.NET's settings/configurations.

It has to do with SQL Server's security settings.

Tod gave you a link with a good pointer to the answer.

The answer is to allow execution permission for the Sproc,
to the account you're using to work with your SQL server DB.

That will depend on how you've configured SQL Server,
and which account ASP.NET uses to work with SQL Server,
which in turn depends on which version of IIS you're using.

You did not mention whether you're using Windows security,
or SQL Server security, or mixed-mode security, in SQL Server,
and you did not mention which version of IIS you're running,
and you did not mention which OS you're using, and you did
not mention which version of ASP.NET/NET Framework
you're using.

Posting that information would have helped to
give you a straighter, more accurate, answer.

This is common in these newsgroups.

Everybody who posts a question here should, at the very least,
identify their OS, the version of IIS, and their .NET Framework
version/ASP.NET version. Additionally, if the question involves
database access, the version of their db platform.

That will help those who are trying to help the poster find the
answer quickly, and get the right answer back to the poster faster.

So, check which account you're using to retrieve/write data
from/to SQL Server, and give execute permission on the sproc
to that account.

The account will be either the SQL Server login you're using to retrieve
data from SQL Server (look in your connection string to know which
one it is), or the ASPNET account if you're running IIS 5, or the
Network Service account if you are running IIS 6.

Only you know which account you're using.

Juan T. Llibre
ASP.NET MVP
===========
"Mike L." <globalwebservices2005@yahoo.com> wrote in message
news:e5sULqpBFHA.4008@TK2MSFTNGP09.phx.gbl...
> Hi Tod,
>
> Is it? So it's got nothing to do with my ASP.NET settings/configurations
> or
> whatever?
> anyone else can help me with this?
>
> thks,
> mike
>
> "Tod Birdsall" <nospam1@netsalad.com> wrote in message
> news:1107067389.927132.193920@c13g2000cwb.googlegroups.com...
>> Hi Mike,
>>
>> Technically, this is the wrong group for this question. You will
>> probably have better luck posting in the following news group :
>> http://groups-beta.google.com/group/microsoft.public.sqlserver.programming
>>
>> The following news group thread will probably help :
>> http://tinyurl.com/3ohj6
>>
>> Tod Birdsall, MCP
>> http://tod1d.blogspot.com
>>
>
>



Relevant Pages

  • Re: SMS_MP_Control_Manager Errors
    ... A colleage of mine figure it out, it was "local security policy" problem, he ... IUSR_"Computer account" must be able to access the computer from the network. ... delete the Guests group from it. ... Verify that the SQL server is properly configured to ...
    (microsoft.public.sms.admin)
  • Http verification .sms_aut (port 80) failed
    ... I noticed I couldn't get SMS reports to work.... ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ...
    (microsoft.public.sms.admin)
  • Re: Http verification .sms_aut (port 80) failed
    ... I resolved a problem like this changing the Security settings on SMS_MP ... I had to go into SQL Server Configuration Manager / SQL Server 2005 Network ... I noticed I couldn't get SMS reports to work.... ... If using a standard SQL security account, ...
    (microsoft.public.sms.admin)
  • Re: Kerberos from XP to IIS hosting ASP.NET 2.0 Web Service help
    ... If your MS SQL Server is running under a custom /local/ account, ... not sure how Kerberos authentication is supposed to work. ... If SQL Server is running under a domain account, ... you are not authenticating to IIS as anonymous. ...
    (microsoft.public.inetserver.iis.security)
  • Windows Authentication with IIS on separate machines
    ... -Web Application is using Basic Authentication set in IIS ... -Added user account TESTUSER and gave read access to ... in SQL server but doesn't work if user account was ... Windows account, ...
    (microsoft.public.sqlserver.security)

Quantcast