Re: Windows permissions to run Jet OLEDB 4.0

By ACLs do you mean folder & file permissions accessible through
Folder .. Properties .. Security?

Both Windows logins have full control over the folder and the file which is
actually an .mde file



"Mary Chipman [MSFT]" wrote:

Check the ACLs for the non-admin user on the folders that contain the
..mdb and see if that's it. It doesn't matter whether you're a sysadmin
in SQL Server or not when you have to go outside of the server to the
file system to get access to the .mdb file.

--Mary

On Wed, 12 Jul 2006 04:13:02 -0700, Lolik
<Lolik@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi Mary, Thanks for replying.

Actually I was talking about Windows logins. You see, I am trying to link
.mdb files
to SQL Server. I've done so OK when logged in to the SQL server using
Windows admin a/c, but as soon as I login to the SQL Server as a [Windows]
user, attempts to retrieve data from the linked server lead to the error
message below.

Again, as far as SQL Server is concerned, both [Windows] admin, and user
logins are both in sysadmin roles.

There is no security whatsoever (user-level or not) implemented on the mdb
file.



"Mary Chipman [MSFT]" wrote:

When you talk about admin and non-admin, are you talking about Jet
logins? If so, then my advice would be to remove Access/Jet user-level
security and have everyone log on as Admin with no password. Jet
security has never played well when it comes to linked servers --
there are workarounds, like editing registry keys, but considering how
feeble (some would say oxymoronic) Access/Jet security is, these
workarounds hardly worth the effort (plus they also have limitations
and caveats). If that's not the problem, then I haven't understood the
question :-)

--Mary

On Sat, 8 Jul 2006 05:33:01 -0700, Lolik
<Lolik@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Having a problem with SQL Server 2005 linked to Access .mdb file using Jet
OLEDB 4.0:

Two windows logins - one admin and another - non-admin, are both setup in
sysadmin roles. Both can create a linked server (Access .mdb file using Jet
OLEDB 4.0).

However while ADMIN login CAN successfully execute SELECT queries from this
linked server, non-admin can not, generating:

<QUOTE>
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server
"linked_server_1" returned message "Unspecified error".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider
"Microsoft.Jet.OLEDB.4.0" for linked server "linked_server_1".
</QUOTE>

Both windows logins have very similar permissions in SQL Server.

Is it possible that the issue may be with some folders used by OLEDB, for
which admin login has sufficient permissions, and non-admin does not?


.

Relevant Pages

  • Re: Beginner security questions
    ... If your goal is to learn how security works by playing with it, ... create SQL logins and ... Once you've tested and debugged security using SQL logins to ... Windows logins to the roles you've created and set your security mode ...
    (microsoft.public.sqlserver.security)
  • Re: Inexplicable security lapse?
    ... If logins are being audited, you can check what login the ... >> ignored and windows authentication is always used. ... the ODBC DNS is specifically set up to use SQL Server authentication. ... >>>Anyway, this seems a terrible breach of security, which I MUST ...
    (microsoft.public.sqlserver.security)
  • RE: Error 18452
    ... "standard" SQL login but your SQL server is ... configured to only accept Windows logins. ... To allow standard logins you ... Click the Security tab. ...
    (microsoft.public.sqlserver.connect)
  • Re: logins
    ... My question was about the security (logins). ... there are differences between MSDE and SQL Server. ...
    (microsoft.public.sqlserver.msde)
  • Re: Windows Auth v/s Sql Server Auth
    ... The only security related stuff that the NT admin will do is to create ... network logins, ... enable those logins to access SQL Server. ... What you do in the end really depends on your security requirements. ...
    (microsoft.public.sqlserver.server)