SQLState: 37000, SQL Server Error: 18452

• Juanita

  SSCertifiable

  Points: 5300

  More actions

  July 14, 2006 at 3:28 pm

  #60930

  HI

  We have an access front end application that was using an access database. We recently migrated the access database into sql server 2000. The developer changed the connection in the access front end and all was well with MOST users. I now have 2 users who have tried the application(1st time since the migration to sql) and they are getting the following errors: 

  Connection Failed:

  SQLState: '01500'

  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 wtih a trusted connection.

  The security setting on the server is set to sql server and windows. Now both of these users can use other applications that do connect to this sql server with no problems. This application is running from a shared drive on the network so it is not installed on each users pc. Can it be because of some type of ODBC connection on their pc?

  Any suggestions?

  Juanita 

   

• Juanita

  SSCertifiable

  Points: 5300

  More actions

  July 14, 2006 at 4:12 pm

  #649388

  My coworker got it figured out! The user had an old MDAC. All is well on the front.

  Juanita

   

   

• john_rossitter

  SSC Rookie

  Points: 48

  More actions

  April 1, 2008 at 12:18 pm

  #796779

  I figured I would throw this out there.

  I was fighting this one for 2 days and finally figured a solution for it.

  My Scenario was was old server was SQL Server 2000 on Domain A and the new server is SQL Server 2005x64 on Windows 2003 x64 on Domain B.

  As some of you know the odbc drivers available to x64 are limited as best.

  Wehen I tried to connect a new linked server from my SQL 2005 to my SQL 2000 I kept getting this error too.

  I tried everything I could think of....until:

  Here was my solution.

  I was logging into Management Studio with Windows authentication under my Domain B account.

  I finally reset my SQL Server 2005 sa password to match my old SQL 2000 sa password.

  Then I logged back into Management studio with the sa account and setup the linked server without error.

  Hope this helps...