user dsn tests successfully but datasource specified does not exist


   I have created a User DSN on a Windows 2012 server that connects to a database MS SQL2012 on another Windows 2012 server.
On the first windows 2012 box, which contains the application, I set  a connection string to the db (windows integrated) under the User DSN tab. I am using the C:\Windows\SysWow64\odbcad32.exe (note application using the db is 32 bits), . On Test connectivity it is successful. When I go to my application and log in using this User DSN I get the error:

Datasource you specified does not exist. !!!

Note: I have also created System DSN with the same specs and this works fine both on test connectivity and through the app. Can someone tell me why a user dsn on test connectivity through odbc works but may not be working through the app? (App is on the first Windows 2012 box where odbc was being set up)
Who is Participating?

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

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.

Try using the 32-Bit ODBC driver because you must have created it on the 64-Bit by default.  Check link below.

Create a 32-bit DSN on 64-bit machine for SQL Server:
LuckyLucksAuthor Commented:
Its in the right place. Used below to verify:
Sorry, yes did specify that.  "Datasource you specified does not exist." sounds like your app is not referring to the Datasource properly.

A user dsn is only visible to the user who created that dsn.  A system dsn is visible to all users on that machine.

Did you launch the app using the same user account you created the USER DSN with?  If not then that's a problem.
LuckyLucksAuthor Commented:
Yes, with the same account. I logged on to the server, created it in ODBC exe and then launched the app with my account again.
Vitor MontalvãoMSSQL Senior EngineerCommented:
Try to create the same DSN but in ODBC 64bits.

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'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 Server 2012

From novice to tech pro — start learning today.