[AccessD] A2003: SQL Trusted Connection Error to SQL Server 2000

Darren D darren at activebilling.com.au
Mon Nov 17 16:28:18 CST 2008


Hi Stuart

Yes this is the frustrating part - this user (this is why I think it is the
machine) is set up with admin credentials - Same as mine on the SQL DB. Even
when we pass the sa credentials in the ConnString on that machine it still gives
us this error. However this machine can start query analyser (with credentials
not trusted connection) with a command line same as me though - Interesting.

On my machine I can connect in both manners. With Trusted Connections = true in
the ConnString or with credentials in the ConnString - No issue either way on my
machine. But sa and my credentials (using the same ConnString) gives me this
error message and the subsequent logon screen.

Many thanks
 
Darren

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Monday, 17 November 2008 5:36 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] A2003: SQL Trusted Connection Error to SQL Server 2000

Is the server set up for User AND Wndows authentication 

>From the error message, it looks as though it is set up to use Windows
authentication.
Does the *logged in user* on the problem machine have access rights to SomedB?


On 17 Nov 2008 at 17:11, Darren D wrote:

> Hi Team
> 
>  
> 
> I have one machine that regardless off what I do it just will not 'connect' to
> anything in our SQL Server Databases
> 
> I am running some on the fly pass through code for running queries etc in the
> SQL dB - (I can forward that if needed)
> 
>  
> 
> The passthrough code works like a charm on my machine but always always always
> fails on this one machine - I am convinced there is something setup or not
setup
> on that machine
> 
>  
> 
> Anyway even when I pass the user name and password in the connection string
for
> the SQL Connection it still fails (Debug.print below)
> 
>  
> 
> DEBUG.PRINT RESULTS OF THE CONNECTION STRING: ODBC;Driver={SQL
> Server};Server=OurServer;Database=SomedB; -u dd; -p xxx123xxx (credentials
> changed but you get the idea)
> 
>  
> 
> Error Message:
> 
>  
> 
> "Connection Failed"
> 
> SQL State: '28000'
> 
> SQL Server error; 18452 [Microsft] [ODBC SQL Server Driver] [SQL Server] Login
> failed for user '(null)'. Reason: not associated with a trusted SQL Server
> Connection 
> 
>  
> 
> So - It claims I am passing a null value in the connection string for the user
-
> but this is not true 
> 
> Then when the user clicks ok there is a small SQL server logon screen with the
> users name in the Username field
> 
> This is killing me - Any suggestions? - Anyone dealt with this before?
> 
>  
> 
> DD
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list