Logon failed for user '(null)'. Not associated with trusted connec

Hi,
I have set up system dsn's with an sql server driver on Windows 2000 to use
SQL Server Authentication (NOT Windows Authentication) on a number of client
PC's. When I use these to connect to an sql server database (which allows
mixed mode authentication) via excel, I get the following message on some
(but not all) client PC's.
===============
Connection failed
SQLState 28000
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for
user
'(null)'.
Reason: Not associated with a trusted SQL Server connection.
================
When I click on OK, another SQL Server login pop-up box appears with the
"Use trusted connection" checkbox pre-checked. If I uncheck this then it
allows me to put in the correct user/password combination.
Why does this happen when the DSN was set up to use a User/password
combination in the first place?. It's as though it tries to connect with
Windows Authentication regardless of how it is originally set up.
Anybody have any ideas?.
Thanks,
AndyCheck for differences in MDAC versions on the PCs. There was
an issue with earlier MDAC versions where ODBC connections
would ignore the authentication mode and just use windows
authentication no matter what you selected. You can use the
component check to check mdac installations. It's available
at:
http://msdn.microsoft.com/data/mdac...ds/default.aspx
-Sue
On Wed, 4 May 2005 03:05:11 -0700, "Squirrel"
<Squirrel@.discussions.microsoft.com> wrote:

>Hi,
>I have set up system dsn's with an sql server driver on Windows 2000 to use
>SQL Server Authentication (NOT Windows Authentication) on a number of clien
t
>PC's. When I use these to connect to an sql server database (which allows
>mixed mode authentication) via excel, I get the following message on some
>(but not all) client PC's.
>===============
>Connection failed
>SQLState 28000
>SQL Server Error 18452
>[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed fo
r user
>'(null)'.
>Reason: Not associated with a trusted SQL Server connection.
>================
>When I click on OK, another SQL Server login pop-up box appears with the
>"Use trusted connection" checkbox pre-checked. If I uncheck this then it
>allows me to put in the correct user/password combination.
>Why does this happen when the DSN was set up to use a User/password
>combination in the first place?. It's as though it tries to connect with
>Windows Authentication regardless of how it is originally set up.
>Anybody have any ideas?.
>Thanks,
>Andy

Logon failed for user '(null)'. Not associated with trusted connec

Hi,
I have set up system dsn's with an sql server driver on windows 2000 to use
SQL Server Authentication (NOT Windows Authentication) on a number of client
PC's. When I use these to connect to an sql server database (which allows
mixed mode authentication) via excel, I get the following message on some
(but not all) client PC's.
===============
Connection failed
SQLState 28000
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
'(null)'.
Reason: Not associated with a trusted SQL Server connection.
================
When I click on OK, another SQL Server login pop-up box appears with the
"Use trusted connection" checkbox pre-checked. If I uncheck this then it
allows me to put in the correct user/password combination.
Why does this happen when the DSN was set up to use a User/password
combination in the first place?. It's as though it tries to connect with
Windows Authentication regardless of how it is originally set up.
Anybody have any ideas?.
Thanks,
Andy
Check for differences in MDAC versions on the PCs. There was
an issue with earlier MDAC versions where ODBC connections
would ignore the authentication mode and just use windows
authentication no matter what you selected. You can use the
component check to check mdac installations. It's available
at:
http://msdn.microsoft.com/data/mdac/...s/default.aspx
-Sue
On Wed, 4 May 2005 03:05:11 -0700, "Squirrel"
<Squirrel@.discussions.microsoft.com> wrote:

>Hi,
>I have set up system dsn's with an sql server driver on windows 2000 to use
>SQL Server Authentication (NOT Windows Authentication) on a number of client
>PC's. When I use these to connect to an sql server database (which allows
>mixed mode authentication) via excel, I get the following message on some
>(but not all) client PC's.
>===============
>Connection failed
>SQLState 28000
>SQL Server Error 18452
>[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
>'(null)'.
>Reason: Not associated with a trusted SQL Server connection.
>================
>When I click on OK, another SQL Server login pop-up box appears with the
>"Use trusted connection" checkbox pre-checked. If I uncheck this then it
>allows me to put in the correct user/password combination.
>Why does this happen when the DSN was set up to use a User/password
>combination in the first place?. It's as though it tries to connect with
>Windows Authentication regardless of how it is originally set up.
>Anybody have any ideas?.
>Thanks,
>Andy

logoff method not working

I am using RS form authentication(from RS sample), after calling Logoff
method, the other RS methods are still working! it seems Logoff method will
not invalid the client cookie! I've tried this on SSL site, not working
either! thanks guys!I know I can just set response.cookie["cookiename"].value = "" to make RS
call failing, just wondering if anyone use logoff method before and how it
works! thanks!

login windows authentication problem

Hi,

I have a problem with sql server 2005 express, when i try to connect to an sql database it says login: is not a trusted connection to an sql database. I have gone into reg edit and changed the authentication setting from windows oly mode 1 to mixed mode 2. It still has the same problem, does anyone have any idea what the problem may be?

kind regards

Chris J

Did you restart the service ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Login Resolution

Friends
I have one SQL server2000 which have Mixed Mode authentication.It is working fine in PC which server instance is situating.But I have another PC which having connectvity tools of SQL Server.When I am trying to access SQL Server from the second PC through SQL authentication access getting denied.In the same time if I am accessing any of first PC's Folder using it's administrator password.Then if try with SQL authentication I am able to connect with SQL Server in the First PC from second PC .Please note SQL server instance is not in windows authentication mode .What may be the problem.Please suggest me a resolution

Thanks in Advance
Filson

What is the error logged in the SQL Server errorlog?

Thanks
Laurentiu

Login problem with Windows Authentication

I am getting that annoying error "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
BillFor Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegroups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>

Login problem with Windows Authentication

I am getting that annoying error "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
Bill
For Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegr oups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>

Login problem with Windows Authentication

I am getting that annoying error "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
BillFor Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegroups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>

Login problem

My database server : local
My database name : MyDatabase
Mode : Windows Authentication Mode (I choose it when I first install sql server 2000)

Using the abovementioned information, I create login using the following statements:

sp_addlogin @.loginame = 'iori'
, @.passwd = '225468'
, @.defdb = 'MyDatabase'
, @.deflanguage = 'english'

After I have compiled the statements, new login is successfully created. But I am having problem to log in into sql server when I try to connect to sql server through Query Analyzer.

I click on 'connect', then a pop up box appears, then I select (local) as my sql server, and in 'connect using', I select 'SQL Server authentication', and finally, I type in my user name as 'iori' and passward as '225468'. I get an error message:

Unable to connect to server IORI...

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

Can anyone help me in this?Make Sure MS Desktop Engine's service is running, u r giving your server name as (local), which seems to be ok, u can also give dot sign (.) instead , under windows authentication mode it should work

Check for MSDEngine service or install desktop engine if u dont have one. Post again if problem persists...gud luk

Regards
BSS|||Thanks, I have solved the problem.

login page problem with reportviewer for winforms

Hi,
My reportserver has forms authentication (for web based users).
When I now try to open a report in the winform report viewer I get an error
on the viewer about the login page. How can I pass the login credentials via
code to the reportserver?:
System.Net.WebException: The request failed with the error message:
--
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a
href='/ReportServer/pages/UIlogon.aspx?ReturnUrl=%2fReportserver%2fReportExecution2005.asmx'>here</a>.</h2>
</body></html>Hello bartVDA,
Thank you for posting.
Regarding on the windows form's reportViewer control, it is
programmatically requesting the report content from reportServer
application rather than interactively like the webbrowser control. Also,
since the form based authentication require the client-side always use
webbrowser to interactively request the report, this will break the winform
reportviewer(also webform reportviewer). BTW, for wniform application, you
can also consider directly lauch webbrowser to display the report through
the actual URL or use a webbrowser control in it though they're not as good
as the well encapsulated reportviewer.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may
learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.