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
===========