Permission denied

[Guest]

I have an application that uses an ODBC link via Access 2002 to a backend SQL
database. When I run it on an XP machine, it is ok. When I run it as an
administrator on my 2003 server as an administrator, it is ok.

When I run it from the 2K3 server as a non administrator it comes up with
"permission denied" errors, but it lets me in. I then get further
"permission denied" errors , but can see my data.

I have made the user a local power user, no help. I have given the user
full rights to the local "C" drive, no help. When I make the user a local
administrator it then works perfectly.

The regular IT administrator says there is no special permissions on the
database.

Any/all help is appreciated.

Thanks

Stephen Berger
Premier Network Solutions

 

[Wolfgang Kais]

Hello Stephen.

I have an application that uses an ODBC link via Access 2002 to a
backend SQL database. When I run it on an XP machine, it is ok.
When I run it as an administrator on my 2003 server as an
administrator, it is ok.

When I run it from the 2K3 server as a non administrator it comes
up with "permission denied" errors, but it lets me in.
I then get further "permission denied" errors, but can see my data.

It sounds like you are using Windows Authentication connecting to
the SQL Server database. If so, the permissions you have depend
on your Windows user account.

I have made the user a local power user, no help.

The power users group does not have SQL Server permissions by default.

I have given the user full rights to the local "C" drive, no help.

That's because it isn't the user but SQL Server that accesses the SQL Server
database files, so file permissions do not apply in this case. Also:
permissions for database objects are stored in the database, not in the
filesystem.

When I make the user a local administrator it then works perfectly.

The local administrators group of a SQL Server computer by default has full
control of the SQL Server, because it's a memeber of the fixed server role
sysadmin (system administrators).

The regular IT administrator says there is no special permissions on the
database.

Maybe you should show her/him how to verify that:
Log on as a member of the local administrators group of the SQL Server
computer. Use SQL Server Enterprise Manager to verify the permissions on the
database and on the database objects that you have problems with.

 

[Guest]

Thanks for your quick response . Unfortuantely I left out some details which
may have changed your answer.

My SQL server is a Windows 2000 server not part of the domain. There are
local users setup on it with the same usernames and passwords as the domain
has.

My Windows 2003 server (in the domain) is running Terminal services. When a
"user" tries to access the database ,either via Terminal services or logged
in at the console, it fails. When I make the user a local (not domain) admin
on the 2003 server, it works. I have not changed any permissions or rights
on the 2000 SQL server at all.

Yes, we are using Windows authentication.

Thanks

 

[Wolfgang Kais]

Hello Stephen.

Thanks for your quick response. Unfortuantely I left out some details
which may have changed your answer.

My SQL server is a Windows 2000 server not part of the domain.
There are local users setup on it with the same usernames and
passwords as the domain has.

My Windows 2003 server (in the domain) is running Terminal services.
When a "user" tries to access the database, either via Terminal
services or logged in at the console, it fails. When I make the user a
local (not domain) admin on the 2003 server, it works. I have not
changed any permissions or rights on the 2000 SQL server at all.

Yes, we are using Windows authentication.

The problem is likely caused by a lack of permissions for the folder
the mdb file is located in. Probably users have only read permissions,
administrators also have change rights. So this is what to verify next.