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