Error when clicking on 'File DSN' tab tyring to create a DSN For SQL DB

I posted this question originally in the SQL Server forum, then realize it probably is a Windows OS issue that is not specific to SQL.  I don't know how to cross post an existing question so I am re-posting it in the Windows OS forums.

Here is the question:

I am a complete NUB to SQL Server.  I am using SQL Server Developer Edition 2014 which is installed on several machines in the office.

I have been using Machine 1 (WIn7 Pro, Office Pro 2010, SQL Dev 2014) for my development.  I installed SQL created databases and set up the DSN in to connect to the files.  All without issue.

I now want to do some work on Machine 2 (Win 7 Pro, Office 2013, SQL Dev 2014) in the office.  SQL is installed but I not able to setup a DSN using the Administrative Tools of the OS.

On machine 2, as soon as I click on the ‘File DSN’ tab within ODBC date sources off the Administrative Tools in Control Panel, the app cancels and I have issues.  I have included the sequence of screen messages I see when it cancels in the attached document.  I don’t know where to proceed from here.

I didn’t even load Visual Studio 2010 on this machine but some of the messages look like unlicensed software is being used.  That is not the case.  All of my software has legitimate licenses.  

On Machine 2, I installed SQL 2014 Dev exactly the same way I did on Machine 1and everything worked fine when setting up and using the DSN.  Any ideas why I’m having issues on this one.

I also have Machine 3 (Win 8.1 Pro, Office 2013, SQL 2014 Dev) in the office.  I have had no issues setting up DSN’s on that machine.  Machine 2 is the only one with issues.

Probably worth mentioning that I had this very same issue on another machine set up the same way (SQL Dev 2014, Win 7 Pro, Office Pro 2013).  I returned the original machine when I could not resolve the problem and I am currently working with the one I bought to replace it.

Any help would be greatly appreciated.  Please see the attached messages.
 ODBCError.docx
LVL 1
mlcktmguyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ste5anSenior DeveloperCommented:
Why using a FileDSN at all?

btw, where do you need it?
mlcktmguyAuthor Commented:
In the MS Access front end I have tables linked to the SQL DB.  I need the DSN to establish that connection.

I have some procedures in the front end that execute stored procedures in the SQL DB.  I connect to those using a connection string.

What are the alternatives to using a DSN for the linked tables.
ste5anSenior DeveloperCommented:
In Access you should use DSN-less connections. Then you don't need to create and manage file DSN's.

See this support article: How to create a DSN-less connection to SQL Server for linked tables in Access

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

mlcktmguyAuthor Commented:
set5an
"In Access you should use DSN-less connections. Then you don't need to create and manage file DSN's.

 See this support article: How to create a DSN-less connection to SQL Server for linked tables in Access "

Thank you very much, I wasn't aware of either of these options.

 I used the 'Create DSN' logic to create a DSN on the problem machine (Machine 2).  However, it created a 'User DSN' not a 'File DSN'.  Is there any way this can be modified to create a 'File DSN'?

Is there any other reason to use DSNless connections than portability?  Is it faster?  I have my app setup to read an .ini file at startup that contains the connections string for that environment.  I then relink the tables using the connection string on the ini.
ste5anSenior DeveloperCommented:
It's more secure. Cause a file or user dsn could be manipulated.
mlcktmguyAuthor Commented:
Excellent, thank you.
Roller KitCommented:
Had the same problem on http://www.partworntyressthelens.co.uk - resolved now thanks guys
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.