login failed for user null: not associated with a trusted SQL Server connection

Question

login failed for user null: not associated with a trusted SQL Server connection

Hendrik-124941

SSC Enthusiast

Points: 187
More actions
July 7, 2006 at 2:46 am

#67561

Hi, we're experiencing problems with a Win2000/Access 2000 -> NT4 server SP6/SQL 2000 connection. The workstation is a fresh Win2000 install with all the latest updates. When I use our personell planning forms (in Access 2000) which retrieve data from the SQL server it returns the following error (translated from dutch);
connection failed:
SQLState: 01S00
SQL Server-error: 0
[Microsoft][ODBC SQL Server Driver]invalid connection string attribute
Connection failed:
SQLState: 37000
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
I found several articles on the net but most of them are related to ASP.net, IIS and Active Directory but we're not using any of those in this situation. The SQL server is set to mixed mode authentication and the user is added (as usual) to security with the proper rights. All other users have the same settings but aren't experiencing problems. This is however the only Win2000 machine we're using for this. There's one 98 and the others are XP Pro. All machines and servers mentioned are in the same domain.
help much appreciated!

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Mark Harr SSCrazy Eights Points: 9921 More actions · Answer 1

You have a problem with the connection string ("Invalid connection string attribute"), and it is causing the connection to attempt a Windows Authenticated logon ("Not associated with a trusted SQL Server connection"). I suspect your misspelled "UserID" or "Password" or "IntegratedSecurity" parameters in the connection string.

Hope this helps

Mark

Jorge Herrera SSC Enthusiast Points: 166 More actions · Answer 2

Hendrik,

Did you get this problem solved?

I have the same problem as you, and it only happens to servers that Have many users and no IIS or websphere.

Cory Perkins SSChasing Mays Points: 638 More actions · Answer 3

When I've run into this, it's because I was using Windows Authentication, but did not give access to the database in SQL Server for the Windows User/Group. You might check that if you haven't.