Link to home
Start Free TrialLog in
Avatar of Aleks
AleksFlag for United States of America

asked on

connection to SQL 2012 error in windows 10

I installed SQL 2016  in a windows 10 computer.
I am using mixed authentication and I am able to open Enterprise Manager fine.

When I try to create an ODBC32 connection to the database it fails. I get the attached error.
The server is there since I can connect to it and the credentials are correct, It looks like a permissions problem but I don't know how to fix it.

User generated image
I also tried 2016 on a different computer and it connects but its super slow, it takes forever to open each ASP. If i install it on the same computer using 2012R2 I have no issues.

Any ideas ?
ASKER CERTIFIED SOLUTION
Avatar of HainKurt
HainKurt
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Aleks

ASKER

Yes. In this particular case I need to create ODBC32  so I am using the first one in your list. That is the one giving me the error.
Is there anywhere in SQL where it would reject a connection from ODBC32 ?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Aleks

ASKER

SQL and the ODBC32 are in the same computer, no firewalls.

I search ODBC32 in windows, the program comes up and I try to setup a System DNS connection.
The same connection in 2012 works fine, but now upgraded to 2016 it does not.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Aleks

ASKER

Yes, I can enter the details of the connection but when I enter the server and enter the user/password on the next page that is when i get the error above.
Cannot connect .. etc ..
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Aleks

ASKER

ODBC version:  File version 10.0.14393.0
How do I get all the other details on that file ?
at the end, just before test
Microsoft SQL Server ODBC Driver Version 10.00.14393

Data Source Name: MyDB
Data Source Description: 
Server: HAINKURT
Database: (Default)
Language: (Default)
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Regional Settings: No
Prepared Statements Option: Drop temporary procedures on disconnect
Use Failover Server: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes
Data Encryption: No

Open in new window


what about the other driver...

in my case, they both worked fine
probably you disabled some of Named/Pipes here...
enable them and try again...
and when you setup DSN, what do you select here
Screenshot---2017-05-04---10_24_05-P.png
Avatar of Vitor Montalvão
What needs ODBC32 to connect to SQL Server locally?
Did you also install the latest SSMS version?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Aleks

ASKER

As I mentioned before the ODBC is local I also posted the version of 2016 SQL.
Enterprise Manager can connect to the database with no problem with windows authentication or mixed authentication.

The only problem is when I try to create a system ODBC connection, and get the error initially posted.
If I don't have a solution by 6 pm today we will reinstall and use SQL 2012 which I know works fine.
Avatar of Aleks

ASKER

We ended up uninstalling SQL 2016 and installing SQL 2012. This solved the issue. There is no solution for the above.
I will award points to those who tried to help.
Avatar of Aleks

ASKER

SQL 2012 was installed. Problem solved.