Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Access/SQL Server ODBC Connection Issue: Error 17 Expand / Collapse
Author
Message
Posted Sunday, June 01, 2008 2:51 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, August 12, 2008 9:56 AM
Points: 2, Visits: 12
I'm having a problem with a connection betwen SQL Server (2005, Named Pipes) and Access. Both exist on the same machine.

I've created an ODBC connection, tested it, and it works fine.
In Access, I link to the SQL Server tables, save the password, and that seems to work fine. I can open the table, and see the data.

When I close Access and reopen it, when I try to access the table, either through a query or just opening it, I get a SQL Server Error: 17. SQL Server does not exist, or access denied.

I click the 'OK' button, then the SQL Server Logon box appears. Click 'OK' here, and I'm able to get to the data.

Anyone have any ideas what is going on here?

Post #509606
Posted Monday, June 02, 2008 8:46 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Monday, April 14, 2014 1:34 PM
Points: 15,442, Visits: 9,588
Check your connection properties in Access. I've seen that problem when there were incorrect credentials stored there.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #509913
Posted Monday, June 02, 2008 9:05 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, August 12, 2008 9:56 AM
Points: 2, Visits: 12
That's a great suggestion, but how do you check the connection properties? Isn't that all being handled by the ODBC DSN?
Post #509933
Posted Monday, June 02, 2008 10:17 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 6:44 PM
Points: 7,084, Visits: 14,684
Tim -
go into design on one of the linked tables in Access, then find the table properties area. You may find that it's replicated the CONTENTS of the DSN in the connection string.

For better or worse - I've run into several versions of MDAC which "refuse" to store passwords "for security passwords", so you get prompted for the password again, even with it being saved in the conn string. "Forcing" the connection string in Access to not have the user ID and password (instead just has "ODBC;DSN=MYDSNNAME") would fix that - but every so often upon relinking/refreshing the tables, the "replace" would happen again.


----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Post #510000
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse