|
Home > Archive > MS SQL Server ODBC > August 2005 > Non- Admin connection
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Non- Admin connection
|
|
| Mark A. Sam 2005-08-03, 8:23 pm |
| I am testing an Access Database on network workstations with linked tables
to SQL Server. I set up a DSN and have no problem logged in as myself with
Admin rights to the server. But when I login as a user with no admin rights
I am denied access with this message:
Connection failed:
SQL Server State '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'dayoubunc1\Sales'.
The network server is Windows 2003 Server, the workstation is Windows 2000
Pro and the SQL Server is a runtime version which came with a Veratis backup
system.
The purpose of moving the tables to SQL Server is security. A user can
steal an Access backend, so I don't want the user to have admin rights to
use the DB. What can I do.
Thanks and God Bless,
Mark A. Sam
| |
| Scot T Brennecke 2005-08-03, 8:23 pm |
| Are you sure that it is related to admin rights? Maybe you just need to add a user named "Sales" to
the SQL Server permissions?
"Mark A. Sam" <msam@Plan-It-Earth.Net> wrote in message
news:u2oqViHmFHA.3448@TK2MSFTNGP12.phx.gbl...
>I am testing an Access Database on network workstations with linked tables
> to SQL Server. I set up a DSN and have no problem logged in as myself with
> Admin rights to the server. But when I login as a user with no admin rights
> I am denied access with this message:
>
> Connection failed:
> SQL Server State '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'dayoubunc1\Sales'.
>
>
> The network server is Windows 2003 Server, the workstation is Windows 2000
> Pro and the SQL Server is a runtime version which came with a Veratis backup
> system.
>
> The purpose of moving the tables to SQL Server is security. A user can
> steal an Access backend, so I don't want the user to have admin rights to
> use the DB. What can I do.
>
> Thanks and God Bless,
>
> Mark A. Sam
>
>
| |
| Mark A. Sam 2005-08-03, 8:23 pm |
| Hello Scot,
I don't know how I would do that. I opened Enterprise manager and tried to
add a new user but the Network users weren't available. I am very
inexperienced with SQL Server, but I think I recall from another client db
that the users network users were listed. And thinking about they, they had
many users who only had to log in and the DB worked, even through terminal
service sessions. It seems as though I only set up the DSNs on those
workstations.
God Bless,
Mark
| |
| Mark A. Sam 2005-08-04, 9:23 am |
| I tried adding full Control to the user for the SQL Server Folder as well as
the database folder, but it didn't get me any further. Authenticated Users
also have access to the SQL Folder.
Could it me that it is a Run Time Version (that is what I was told) of SQL
Server? Does the client need to purchase the full version?
|
|
|
|
|