By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,301 Members | 1,741 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,301 IT Pros & Developers. It's quick & easy.

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

P: n/a
weīre having problems to put our Website at IIS:
We have achieved it all works using the connectionString with user and
password of the superuser (sa), but with IntegratedSecurity we get the
following message after login in our application:

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

I donīt know if it even doesnīt see the username and password I
write, or if it is a problem with permission.... What I donīt
understand is that we haven't this problem with the integrated web
server and yes with IIS...
Concerning accesing directly the Default.aspx page I have already put
it as predetermined at the virtual directory but I only achieve to see
it if I check Windows Authentication but in that case when I want to
see the page from another machine I get the authentication window... (
It happens the same to see the images/pictures I have...)

Any idea...?
Thanks!

Jan 5 '07 #1
Share this Question
Share on Google+
5 Replies


P: n/a
yes, that is exactly what I have and it works, but we donīt want to
use it like that but with Integrated Security, and we donīt know why
it doesnīt work in that case ...or how to make it work,do you...?

Jan 5 '07 #2

P: n/a
"CFTK" <cr***************@gmail.comwrote in message
news:11**********************@v33g2000cwv.googlegr oups.com...
yes, that is exactly what I have and it works, but we donīt want to
use it like that but with Integrated Security, and we donīt know why
it doesnīt work in that case ...or how to make it work,do you...?
Integrated Security means that SQL Server's security is "integrated" into
Windows security i.e. you can use a Windows login account to gain access to
SQL Server.

When you configure your connection string to use integrated security, it
will try to connect to SQL Server using the Windows security credentials of
the current context i.e. whatever user is running the current process.

The 'sa' account is not a Windows accout - it's a built-in SQL Server
account - so it can't be used with integrated security.

As a general rule, it is bad practice to use the sa account for anything
other than system administration by the DBA...
Jan 5 '07 #3

P: n/a
CFTK wrote:
weīre having problems to put our Website at IIS:
We have achieved it all works using the connectionString with user and
password of the superuser (sa), but with IntegratedSecurity we get the
following message after login in our application:

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

I donīt know if it even doesnīt see the username and password I
write, or if it is a problem with permission.... What I donīt
understand is that we haven't this problem with the integrated web
server and yes with IIS...

Do these help?

http://msdn.microsoft.com/msdnmag/is...ecurityBriefs/

http://support.microsoft.com/kb/810572

Both discussing issues with authentication, especially across multiple
machines, which is where this problem most frequently appears.

Damien

Jan 5 '07 #4

P: n/a
Thanks!!!!!!!!!!!!!!!

Jan 9 '07 #5

P: n/a
Iīm still just reading and it looks perfect, but I have ended up in
the article you referred me to

( http://support.microsoft.com/kb/810572)

where it says that to configure ASP.NET for delegation we have to put
in our web.config file <authentication mode="Windows"/>
but thatīs avoids all the membership/roles configuration I have for my
aplication... ( i.e WAT).

Canīt it be done with <authentication mode="Forms"/??? ( In that
case Iīd be lost!!)

Wait for your reply.Thanks in advance!

Jan 9 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.