Login failed for user ''. Reason: Not associated with a trusted SQL Server connection.

Hi,

I have 2 windows 2003 server, i instllaed sql server 2005 enterprise edition on the first one (Mixed Mode), and i am trying to install sql server reporting 2000 on the second one,

I installed the sql 2000 connectivity only on the second one , and i installed the sql server sp4 also, while installing reporting services i used the sql login account (sa,pwd)

i got the following error :

Cannot connect to sql server instance ...

Login failed for user ''. Reason: Not associated with a trusted SQL Server connection.

NB1: Allow Remote connection is enabled on sql server 2005.

NB2: I tried to connect from server 2 to server 1 from odbc and it worked properly with (sa,pwd) i have only a problem from reporting server.

Please any help?

Tarek Ghazali

SQL Server MVP

Are the machines in the same domain? What is the network configuration? What does "sql 2000 connectivity" mean?

Have you checked the errorlog? Is there any additional information on the failure there?

Try running a Profiler trace on the SQL Server machine to see if you can find any additional information on the login attempt.

Thanks
Laurentiu

|||

Here's a thread that may be related to the issue you are seeing: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=422598&SiteID=1

Thanks
Laurentiu

|||

Hi Laurentiu,

Thx for your reply,

I have 2 servers on the same domain and under vmware virtual

server (the new release beta 2) ,about sql 2000 connectivity you can install sql server 2000 as (database server or client or connectivity).

I don't have any log error.

Thanks,

Tarek Ghazali

SQL Server MVP

|||

Login failures are normally logged. Are you sure you checked the log on the right server - the one you were trying to connect to? Also, have you got any insights from running a Profiler trace?

Thanks
Laurentiu

|||

Hi Laurentiu,

I created a user on the domain , and i logged on windows by this user on the second server, i added this user to have access login on the first server and it worked fine.

Regards,

Tarek Ghazali

SQL Server MVP

Login failed for user ''. Reason: Not associated with a trusted SQL Server connection.

Hi,

I have 2 windows 2003 server, i instllaed sql server 2005 enterprise edition on the first one (Mixed Mode), and i am trying to install sql server reporting 2000 on the second one,

I installed the sql 2000 connectivity only on the second one , and i installed the sql server sp4 also, while installing reporting services i used the sql login account (sa,pwd)

i got the following error :

Cannot connect to sql server instance ...

Login failed for user ''. Reason: Not associated with a trusted SQL Server connection.

NB1: Allow Remote connection is enabled on sql server 2005.

NB2: I tried to connect from server 2 to server 1 from odbc and it worked properly with (sa,pwd) i have only a problem from reporting server.

Please any help?

Tarek Ghazali

SQL Server MVP

Are the machines in the same domain? What is the network configuration? What does "sql 2000 connectivity" mean?

Have you checked the errorlog? Is there any additional information on the failure there?

Try running a Profiler trace on the SQL Server machine to see if you can find any additional information on the login attempt.

Thanks
Laurentiu

|||

Here's a thread that may be related to the issue you are seeing: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=422598&SiteID=1

Thanks
Laurentiu

|||

Hi Laurentiu,

Thx for your reply,

I have 2 servers on the same domain and under vmware virtual

server (the new release beta 2) ,about sql 2000 connectivity you can install sql server 2000 as (database server or client or connectivity).

I don't have any log error.

Thanks,

Tarek Ghazali

SQL Server MVP

|||

Login failures are normally logged. Are you sure you checked the log on the right server - the one you were trying to connect to? Also, have you got any insights from running a Profiler trace?

Thanks
Laurentiu

|||

Hi Laurentiu,

I created a user on the domain , and i logged on windows by this user on the second server, i added this user to have access login on the first server and it worked fine.

Regards,

Tarek Ghazali

SQL Server MVP

sql

Login failed for user

I installed Sales Logix (a database program) which uses
SQL Server MSDE. When you install Sales Logix, it
installs SQL Server; however, I was having trouble getting
SQL to install so worked with a Microsoft tech and we got
a default instance of SQL Server MSDE installed. Now,
when I try to attach my SLX database using the SalesLogix
Attach Remote utility, I get the following error:
[Microsoft][ODBC SQL Driver][SQL Server Driver][SQL Server]
Login failed for user 'sa'. Reason: Not associated with
a trusted SQL Server connection.
How would I associate this with a trusted SQL Server
connection? Any help would be greatly appreciated!
Leesa
hi Leesa,
"Leesa" <leesaforeman@.fccef.com> ha scritto nel messaggio
news:2f55001c46c41$0fa2ad50$a301280a@.phx.gbl...
> I installed Sales Logix (a database program) which uses
> SQL Server MSDE. When you install Sales Logix, it
> installs SQL Server; however, I was having trouble getting
> SQL to install so worked with a Microsoft tech and we got
> a default instance of SQL Server MSDE installed. Now,
> when I try to attach my SLX database using the SalesLogix
> Attach Remote utility, I get the following error:
> [Microsoft][ODBC SQL Driver][SQL Server Driver][SQL Server]
> Login failed for user 'sa'. Reason: Not associated with
> a trusted SQL Server connection.
> How would I associate this with a trusted SQL Server
> connection? Any help would be greatly appreciated!
> Leesa
MSDE install by default granting only Windows NT trusted connections, so SQL
Server authenticated connections, using "user" + "pwd" credential are not
allowed...
you can change this behaviour both at install time and later, using the
advices provided at
http://support.microsoft.com/default...b;en-us;285097
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

Login error: 18456, Severity: 14, State: 11.

Hi,
we did an clean install of MOSS2007 and SQL2005. Both on different servers.
Everything worked well and suddenly we are getting this error and MOSS2007
stops working. The second message in the error log is: 'Login failed for user
'Domain\user'.
If I put the user in the SysAdmin serverrole they are able to connect.
Strange thing is that this is also happening on our SP2003/SQL2000 servers.
But on these servers it's gone after an short period.
Someone any idea?
--
Robert Hartskeerl, MCTS, MCITPHi Robert
State 11 is "Login is valid, but server access failed." my guess is that the
default database is wrong or you don't have access to it. You could try
logging in as that user and use SQLCMD or osql to change the database you
connect to. sp_defaultdb can be used to change the default database.
John
"Robert Hartskeerl" wrote:
> Hi,
> we did an clean install of MOSS2007 and SQL2005. Both on different servers.
> Everything worked well and suddenly we are getting this error and MOSS2007
> stops working. The second message in the error log is: 'Login failed for user
> 'Domain\user'.
> If I put the user in the SysAdmin serverrole they are able to connect.
> Strange thing is that this is also happening on our SP2003/SQL2000 servers.
> But on these servers it's gone after an short period.
> Someone any idea?
> --
> Robert Hartskeerl, MCTS, MCITP|||Hello, Robert
Maybe one of following will help:
http://blogs.msdn.com/sql_protocols/archive/2007/06/18/connecting-to-sql-server-2005-on-vista-and-longhorn.aspx
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
Razvan Socol
SQL Server MVP|||Thanks for your response John.
We already solved this with the information on connect.microsoft.com.
We had created extra tcp enpoints for different users. What happens is that
SQL Server removes the public role from TCP-Connect. So while the other
applications that used the non-default endpoints only sa's are able to
connect to the default endpoint.
After adding TCP-Endpoint to the public role we can connect.
Robert Hartskeerl
--
Robert Hartskeerl, MCTS, MCITP
"John Bell" wrote:
> Hi Robert
> State 11 is "Login is valid, but server access failed." my guess is that the
> default database is wrong or you don't have access to it. You could try
> logging in as that user and use SQLCMD or osql to change the database you
> connect to. sp_defaultdb can be used to change the default database.
> John
>
> "Robert Hartskeerl" wrote:
> > Hi,
> >
> > we did an clean install of MOSS2007 and SQL2005. Both on different servers.
> > Everything worked well and suddenly we are getting this error and MOSS2007
> > stops working. The second message in the error log is: 'Login failed for user
> > 'Domain\user'.
> >
> > If I put the user in the SysAdmin serverrole they are able to connect.
> >
> > Strange thing is that this is also happening on our SP2003/SQL2000 servers.
> > But on these servers it's gone after an short period.
> >
> > Someone any idea?
> > --
> > Robert Hartskeerl, MCTS, MCITP