Re: Login failed for user ''. The user is not associated with a trusted SQL Server connection.



you only have to setup delegation if you want to use the clients' credentials for the sql server login - in this case he just trying to use the process account - which will not work for the ASPNET account.

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

Keep in mind that if the SQL Server is NOT on the same box as the IIS,
you have to setup delegation of the security accounts that this works.
Otherwise the SQL Server can´t check if your User is *really* the
original one.

HTH, Jens Suessmeyer.



.



Relevant Pages

  • Re: sqlserver connection - need help desperately!
    ... > You are connecting to a remote SQL Server ... > The SQL Server accepts both Windows and SQL Server authentication. ... > SQL Server login that's authorized to use your database. ... > the ASP.NET account in the SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Authenticating in SQL Server via MS Access 2002
    ... account and this account will be used by Access to authenticate with ... > 1.Database is on SQL Server 2000 ... > SQL using Windows authentication. ... > it is then that they are asked for their SQL Server login. ...
    (microsoft.public.access.externaldata)
  • Re: SQL Server on XP Home Network
    ... There is an "sa" account under the Security>Logins area. ... Does that coorelate to a SQL Server login? ... I tried setting up the connection to use that SQL Server ...
    (microsoft.public.sqlserver.setup)
  • Re: Admin User Account from Front -end Interface
    ... You can create a new SQL Server login account using sp_addlogin: ... Or you can grant an existing windows account access to SQL Server with ...
    (microsoft.public.sqlserver.security)
  • Re: Error 15401 using sp_grantlogin (not addressed by current KB articles)
    ... Restarting Windows 2000 resolved the problem for this particular account, ... confused when it sees a duplicate SID. ... > One way to get SQL Server to agree with the renamed NT ... > Preview (to ensure the script was created), ...
    (microsoft.public.sqlserver.security)