SQL 2014 connection from an ODBC client on Excel queries created by administrator.

Hello,
I found a topic with the above subject, but the solution is not what I am looking for.

A bit of a background.
We changed our ERP sytem. A to B.
For the ERP A I would create two ODBC connections (System DSNs), for 32 and 64 bits with the same name / settings on each computer, using SQL Server authentication.
Any Excel query / report created using the above connection could be open any computer with access to the location where the report was.
The above was SQL Server 2005 and any Windows / Excel combination.

Knowing that a lot of users already are familiar with Excel I did the same setup. I should say similar setup.
I created two ODBC system DSNs for ERP B, (32 and 64), named those same on all computers. Used With Windows NT Authentication.... Connection test worked fine.
Using SQL Server authentication did not work, but queries / reports could be created in Excel using this DSN.

The problem now comes when a user opens an Excel report created by administrator and tries reading the new ERP B SQL 2014 database / Windows 10.
Connection failed: error pops up.
SQLState: '28000'
SQL Server Error:18456
[Microsoft][ODBC SQL Server Driver][SQL Server[Login failed for user 'DOMAIN\user'.
After click on OK, in the SQL Server Login pop up, with Use Trusted Connection box checked, appears my domain name.
Even after the Use Trusted Connection box is unchecked and admin or user credentials are entered the connection doesn't work.

What settings am I missing on the server / local workstation / active directory that this connection doesn't work for domain users.
MezczyznaAsked:
Who is Participating?
 
Vadim RappCommented:
Verify that sql server 2014 has logon domain\group under Security, where group is any group your users belong to, with windows authentication and user mapping to the database representing ERP B.

You can experiment by opening Properties of the connection in excel, copying the connection string, and creating one-line .vbs file:

createobject("adodb.connection").open(your-connection-string)

Run it and see if there's an error.
0
 
MezczyznaAuthor Commented:
This was it.
Security on the database itself.
Thank you.
0
 
MezczyznaAuthor Commented:
Thank you.
This was the resolution, adding security group from domain to logins on security and the security tree of the database being accessed.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.