Login failed for user (null). Not associated with a trusted S

I'm new to this so I'll answer the best I can. Its my understanding that SQ
L
Server should be using the user account of the person logged in. There is a
n
account set up in sql server for this user with permissions to the database.
"Mark Rae" wrote:

> "Sherri" <Sherri@dotnet.itags.org.discussions.microsoft.com> wrote in message
> news:869C31CE-EFCF-4BC7-B406-F217FEB815D0@dotnet.itags.org.microsoft.com...
>
> By specifying Integrated Security, you've told ASP.NET to try to connect t
o
> SQL Server with the account that it's currently running under.
> You've also told ASP.NET not to run under its default account, but to
> impersonate a different account instead.
> So, have you set up the account that ASP.NET is impersonating as a valid
> user in the SQL Server database that you're trying to connect to...?
>
>"Sherri" <Sherri@.discussions.microsoft.com> wrote in message
news:EE2CD5F3-0293-49C6-81BC-5C89B484A18C@.microsoft.com...

> I'm new to this so I'll answer the best I can. Its my understanding that
> SQL
> Server should be using the user account of the person logged in. There is
> an
> account set up in sql server for this user with permissions to the
> database.
1) Interrogate the servervariables collection on any of the aspx pages in
your site, specifically the AUTH_USER or LOGON_USER variables - that will
tell you which user your site is running under. If it's not what you think
it should be, then there's your problem...
2) From SQL Server Management Studio, try to connect to the server in
question by logging in as the user you think your ASP.NET app should be
using... Can you get in? Can you access the database(s) your ASP.NET app
needs to access...? If not, then there's your problem...