Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1280
  • Last Modified:

Access Error: ODBC Call Failed: Data source name was not found and no default drivers specified (#0)

User is first going into Control Panel and creating a new System DSN connection to the SQL instance in question.  User has proper permissions on the SQL instance/database in question.  

He gets this message when he opens a new Access Database, right clicks, selects "Link Table" and selects ODBC as the file type, then selects the System DSN he set up.  When setting up the System DSN it said "Test Completed Successfully" so I don't understand why he's getting this message.

Thanks for any ideas.
0
synapse88
Asked:
synapse88
  • 3
1 Solution
 
dqmqCommented:
One thought that comes to mind is there is a corrupt USER DSN (or artifacts of it) by the same name.   Check the USER tab of the ODBC control panel.  For grins, try using a different DSN name.
0
 
synapse88Author Commented:
I've already tried that and it was no help :(
0
 
LukeBCommented:
Sy,

I had / have similar problem ... I more or less have it tracked down.

I setup a DSN file that works fine for me and one other user but FAILS on all others :

   [ODBC]
   DRIVER=SQL Native Client
   UID=luke
   DATABASE= HGRDB
   WSID=DELLM90_C8WBL1S
   APP=Microsoft Data Access Components
   SERVER=SERVER-B\BEVTEMPSQL
   Description=HGRDB accounting

All other users get a "ODBC --call failed .  ODBC Driver Manager] Data source name was not found and no default drivers specified (#0)"

So I went to one of their machines and made another DSN, it looks like this:

   [ODBC]
   DRIVER=SQL Server
   UID=luke
   Trusted_Connection=Yes
   DATABASE=HGRDB
   WSID=BEVERLEY68
   APP=Microsoft Office 2003
   SERVER=SERVER-B\BEVTEMPSQL
   Description=Luke Test From User Machine

I am putting it down ot older machines that do not have the latest MS SQL Driver or something ...

Note that several lines are different. Give it a try , thise older format works for me (as did the first one I set up, more update version). It is working for me on a DSN files and now I am just changing my code to use the 'older' format. to make DSN-less connections.
0
 
LukeBCommented:
PS: with the second one you can omit the Trusted_Connection line to begin with, SQLServer will  pop that up if the user is known or if you do not  have iintegrated SQLServer login enabled on the server.

Even if the user is not include in SQLServer ACL then the SQLServer login prompt will come up, I just tried the updated system on one of the users that had problems before and now they can connect to the SQLServer, I just need to give them a log in

good luck
0
 
LukeBCommented:
PPS: and see  PAQ /Q_23396055.html, that tweaked me to try gong to the user's machines and ttrying that way.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now