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

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

P: n/a
There are loads of post on this, but nothing that seems to cover my
exact problem ;)

I have an ASP.Net 1.1 web application running on my local machine. I
want to connect to an SQL 2005 server running on Windows 2003.

If I use SQL authentication, all is fine and dandy. If I want to use
windows authentication it gives the above error. My SQL server is set
to allow both methods (first thing I checked) and is part of the
domain (2nd thing checked).

If I create a UDL file on the local machine and connect to the SQL
server with that, it reports that the test connection is successful,
so I took the connection string from that and used it in my
web.config, but got the above error.

Here's my connection string using SQL Authentication

"Password=RagUser;Persist Security Info=True;User ID=RagUser;Initial
Catalog=KBDL_Config;Data Source=UKBOLDEV01"

and the connection string using windows authentication

"Integrated Security=SSPI;Persist Security Info=False;Initial
Catalog=KBDL_Config;Data Source=ukboldev01"

Even adding 'Trusted Connection=True' to the windows authentication
doesn't help!

SQL 2005 has errors in it's log, it shows.

10/26/2007 16:35:54,Logon,Unknown,Login failed for user ''. The user
is not associated with a trusted SQL Server connection. [CLIENT:
192.168.41.75]
10/26/2007 16:35:54,Logon,Unknown,Error: 18452<c/Severity: 14<c/>
State: 1.
10/26/2007 16:35:54,Logon,Unknown,SSPI handshake failed with error
code 0x8009030c while establishing a connection with integrated
security; the connection has been closed. [CLIENT: 192.168.41.75]
10/26/2007 16:35:54,Logon,Unknown,Error: 17806<c/Severity: 20<c/>
State: 2.
I'm baffled by this, I've even tried connecting to the server using
oSQL, that was successful, but with vb.net from a web app, it fails.
There's a code snippet below

<code>
strSQL = "SELECT * FROM LOGINS WHERE Username='" & strUsername & "'
AND Password='" & strPassword & "'"

myconnection = New
SqlConnection(ConfigurationSettings.AppSettings("C onfigCon")) 'get
from web.config
myCommand = New SqlCommand(strSQL, myconnection)

Try
If (myCommand.Connection.State <ConnectionState.Open)
Then 'check connection state
myCommand.Connection.Open() ' open connection if
needed
End If
</code>

Oct 26 '07 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Have you tried also something such as :
http://msdn2.microsoft.com/en-us/library/ms998320.aspx
--
Patrice

"eruth" <em***********@gmail.coma écrit dans le message de news:
11********************@k79g2000hse.googlegroups.co m...
There are loads of post on this, but nothing that seems to cover my
exact problem ;)

I have an ASP.Net 1.1 web application running on my local machine. I
want to connect to an SQL 2005 server running on Windows 2003.

If I use SQL authentication, all is fine and dandy. If I want to use
windows authentication it gives the above error. My SQL server is set
to allow both methods (first thing I checked) and is part of the
domain (2nd thing checked).

If I create a UDL file on the local machine and connect to the SQL
server with that, it reports that the test connection is successful,
so I took the connection string from that and used it in my
web.config, but got the above error.

Here's my connection string using SQL Authentication

"Password=RagUser;Persist Security Info=True;User ID=RagUser;Initial
Catalog=KBDL_Config;Data Source=UKBOLDEV01"

and the connection string using windows authentication

"Integrated Security=SSPI;Persist Security Info=False;Initial
Catalog=KBDL_Config;Data Source=ukboldev01"

Even adding 'Trusted Connection=True' to the windows authentication
doesn't help!

SQL 2005 has errors in it's log, it shows.

10/26/2007 16:35:54,Logon,Unknown,Login failed for user ''. The user
is not associated with a trusted SQL Server connection. [CLIENT:
192.168.41.75]
10/26/2007 16:35:54,Logon,Unknown,Error: 18452<c/Severity: 14<c/>
State: 1.
10/26/2007 16:35:54,Logon,Unknown,SSPI handshake failed with error
code 0x8009030c while establishing a connection with integrated
security; the connection has been closed. [CLIENT: 192.168.41.75]
10/26/2007 16:35:54,Logon,Unknown,Error: 17806<c/Severity: 20<c/>
State: 2.
I'm baffled by this, I've even tried connecting to the server using
oSQL, that was successful, but with vb.net from a web app, it fails.
There's a code snippet below

<code>
strSQL = "SELECT * FROM LOGINS WHERE Username='" & strUsername & "'
AND Password='" & strPassword & "'"

myconnection = New
SqlConnection(ConfigurationSettings.AppSettings("C onfigCon")) 'get
from web.config
myCommand = New SqlCommand(strSQL, myconnection)

Try
If (myCommand.Connection.State <ConnectionState.Open)
Then 'check connection state
myCommand.Connection.Open() ' open connection if
needed
End If
</code>

Oct 26 '07 #2

P: n/a
if your local asp.net site is running under iis, then you need to set to
run under a domain account with access the sqlserver.

1) if you only hit the website locally just set impersonate=true in the
web config and require authenication to ntlm in iis

2) if your local box is vista or server2003 set the app pool for the
asp.net site to the desired domain account.

3) if none of above, in web.config set impersonate with a useName and
password.

-- bruce (sqlwork.com)

eruth wrote:
There are loads of post on this, but nothing that seems to cover my
exact problem ;)

I have an ASP.Net 1.1 web application running on my local machine. I
want to connect to an SQL 2005 server running on Windows 2003.

If I use SQL authentication, all is fine and dandy. If I want to use
windows authentication it gives the above error. My SQL server is set
to allow both methods (first thing I checked) and is part of the
domain (2nd thing checked).

If I create a UDL file on the local machine and connect to the SQL
server with that, it reports that the test connection is successful,
so I took the connection string from that and used it in my
web.config, but got the above error.

Here's my connection string using SQL Authentication

"Password=RagUser;Persist Security Info=True;User ID=RagUser;Initial
Catalog=KBDL_Config;Data Source=UKBOLDEV01"

and the connection string using windows authentication

"Integrated Security=SSPI;Persist Security Info=False;Initial
Catalog=KBDL_Config;Data Source=ukboldev01"

Even adding 'Trusted Connection=True' to the windows authentication
doesn't help!

SQL 2005 has errors in it's log, it shows.

10/26/2007 16:35:54,Logon,Unknown,Login failed for user ''. The user
is not associated with a trusted SQL Server connection. [CLIENT:
192.168.41.75]
10/26/2007 16:35:54,Logon,Unknown,Error: 18452<c/Severity: 14<c/>
State: 1.
10/26/2007 16:35:54,Logon,Unknown,SSPI handshake failed with error
code 0x8009030c while establishing a connection with integrated
security; the connection has been closed. [CLIENT: 192.168.41.75]
10/26/2007 16:35:54,Logon,Unknown,Error: 17806<c/Severity: 20<c/>
State: 2.
I'm baffled by this, I've even tried connecting to the server using
oSQL, that was successful, but with vb.net from a web app, it fails.
There's a code snippet below

<code>
strSQL = "SELECT * FROM LOGINS WHERE Username='" & strUsername & "'
AND Password='" & strPassword & "'"

myconnection = New
SqlConnection(ConfigurationSettings.AppSettings("C onfigCon")) 'get
from web.config
myCommand = New SqlCommand(strSQL, myconnection)

Try
If (myCommand.Connection.State <ConnectionState.Open)
Then 'check connection state
myCommand.Connection.Open() ' open connection if
needed
End If
</code>
Oct 26 '07 #3

P: n/a
Bruce,

To address your suggestions.

1) The problem with this solution is that once this site is deployed,
the webserver will be in the DMZ, and the SQL server on the inside of
the firewall.
2) May be possible when deployed as the live servers will both be
2003, however my development box (local pc) is XPsp2
3) I'll try this and let you know.
On 26 Oct, 17:29, bruce barker <nos...@nospam.comwrote:
if your local asp.net site is running under iis, then you need to set to
run under a domain account with access the sqlserver.

1) if you only hit the website locally just set impersonate=true in the
web config and require authenication to ntlm in iis

2) if your local box is vista or server2003 set the app pool for the
asp.net site to the desired domain account.

3) if none of above, in web.config set impersonate with a useName and
password.

-- bruce (sqlwork.com)

eruth wrote:
There are loads of post on this, but nothing that seems to cover my
exact problem ;)
I have an ASP.Net 1.1 web application running on my local machine. I
want to connect to an SQL 2005 server running on Windows 2003.
If I use SQL authentication, all is fine and dandy. If I want to use
windows authentication it gives the above error. My SQL server is set
to allow both methods (first thing I checked) and is part of the
domain (2nd thing checked).
If I create a UDL file on the local machine and connect to the SQL
server with that, it reports that the test connection is successful,
so I took the connection string from that and used it in my
web.config, but got the above error.
Here's my connection string using SQL Authentication
"Password=RagUser;Persist Security Info=True;User ID=RagUser;Initial
Catalog=KBDL_Config;Data Source=UKBOLDEV01"
and the connection string using windows authentication
"Integrated Security=SSPI;Persist Security Info=False;Initial
Catalog=KBDL_Config;Data Source=ukboldev01"
Even adding 'Trusted Connection=True' to the windows authentication
doesn't help!
SQL 2005 has errors in it's log, it shows.
10/26/2007 16:35:54,Logon,Unknown,Login failed for user ''. The user
is not associated with a trusted SQL Server connection. [CLIENT:
192.168.41.75]
10/26/2007 16:35:54,Logon,Unknown,Error: 18452<c/Severity: 14<c/>
State: 1.
10/26/2007 16:35:54,Logon,Unknown,SSPI handshake failed with error
code 0x8009030c while establishing a connection with integrated
security; the connection has been closed. [CLIENT: 192.168.41.75]
10/26/2007 16:35:54,Logon,Unknown,Error: 17806<c/Severity: 20<c/>
State: 2.
I'm baffled by this, I've even tried connecting to the server using
oSQL, that was successful, but with vb.net from a web app, it fails.
There's a code snippet below
<code>
strSQL = "SELECT * FROM LOGINS WHERE Username='" & strUsername & "'
AND Password='" & strPassword & "'"
myconnection = New
SqlConnection(ConfigurationSettings.AppSettings("C onfigCon")) 'get
from web.config
myCommand = New SqlCommand(strSQL, myconnection)
Try
If (myCommand.Connection.State <ConnectionState.Open)
Then 'check connection state
myCommand.Connection.Open() ' open connection if
needed
End If
</code>
Oct 29 '07 #4

P: n/a
One final note - yes suggestion 3 did work, but on talking to the nice
security people here, I was advised that using windows authentication
might not be a good idea. So I'm going to stick with the SQL
authentication and write a series of SQL jobs that will make sure the
right users with the right permissions exist at the right time for my
web pages to connect to the database.

On 29 Oct, 09:15, eruth <emma.pearl...@gmail.comwrote:
Bruce,

To address your suggestions.

1) The problem with this solution is that once this site is deployed,
the webserver will be in the DMZ, and theSQLserveron the inside of
the firewall.
2) May be possible when deployed as the live servers will both be
2003, however my development box (local pc) is XPsp2
3) I'll try this and let you know.

On 26 Oct, 17:29, bruce barker <nos...@nospam.comwrote:
if your local asp.net site is running under iis, then you need to set to
run under a domain account with access the sqlserver.
1) if you only hit the website locally just set impersonate=true in the
web config and require authenication to ntlm in iis
2) if your local box is vista or server2003 set the app pool for the
asp.net site to the desired domain account.
3) if none of above, in web.config set impersonate with a useName and
password.
-- bruce (sqlwork.com)
eruth wrote:
There are loads of post on this, but nothing that seems to cover my
exact problem ;)
I have an ASP.Net 1.1 web application running on my local machine. I
want to connect to anSQL2005serverrunning on Windows 2003.
If I useSQLauthentication, all is fine and dandy. If I want to use
windows authentication it gives the above error. MySQLserveris set
to allow both methods (first thing I checked) and is part of the
domain (2nd thing checked).
If I create a UDL file on the local machine and connect to theSQL
>serverwith that, it reports that the testconnectionis successful,
so I took theconnectionstring from that and used it in my
web.config, but got the above error.
Here's myconnectionstring usingSQLAuthentication
"Password=RagUser;Persist Security Info=True;UserID=RagUser;Initial
Catalog=KBDL_Config;Data Source=UKBOLDEV01"
and theconnectionstring using windows authentication
"Integrated Security=SSPI;Persist Security Info=False;Initial
Catalog=KBDL_Config;Data Source=ukboldev01"
Even adding 'TrustedConnection=True' to the windows authentication
doesn't help!
>SQL2005 has errors in it's log, it shows.
10/26/2007 16:35:54,Logon,Unknown,Loginfailedforuser''. Theuser
isnotassociatedwith atrustedSQLServerconnection. [CLIENT:
192.168.41.75]
10/26/2007 16:35:54,Logon,Unknown,Error: 18452<c/Severity: 14<c/>
State: 1.
10/26/2007 16:35:54,Logon,Unknown,SSPI handshakefailedwith error
code 0x8009030c while establishing aconnectionwith integrated
security; theconnectionhas been closed. [CLIENT: 192.168.41.75]
10/26/2007 16:35:54,Logon,Unknown,Error: 17806<c/Severity: 20<c/>
State: 2.
I'm baffled by this, I've even tried connecting to theserverusing
oSQL, that was successful, but with vb.net from a web app, it fails.
There's a code snippet below
<code>
strSQL = "SELECT * FROM LOGINS WHERE Username='" & strUsername & "'
AND Password='" & strPassword & "'"
myconnection = New
SqlConnection(ConfigurationSettings.AppSettings("C onfigCon")) 'get
from web.config
myCommand = New SqlCommand(strSQL, myconnection)
Try
If (myCommand.Connection.State <ConnectionState.Open)
Then 'checkconnectionstate
myCommand.Connection.Open() ' openconnectionif
needed
End If
</code>

Oct 30 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.