Linked Server Access Problems

From: Ricky Artigas (rya@easycall.net.ph)
Date: 11/02/02 

From: "Ricky Artigas" <rya@easycall.net.ph>
Date: Fri, 1 Nov 2002 19:52:55 -0800

Hi Scott. Have you tried mapping your user's login to the
Admin user of your mdb and setting the password as blank?
In access databases/mdb files, there is a default Admin
user id which has no password.
Under SQL Server's Linked Servers, you can specify the
login mappings from there. Hope this helps.

>-----Original Message-----
>I have recently struggled with granting access to a
linked server
>database on a SQL 2K box. Only administrators could log
in to the
>client application and access the data in the linked
server tables,
>simple domain users could not. All a simple domain user
would receive
>is an Error 7399: OLE DB
Provider 'Microsoft.Jet.OLEDB.4.0' reported
>an error. The SQL Server service (i.e. all SQL Services)
was running
>the under the DOMAIN\Administrator account. The non-
secure access
>database was linked using a (UNC first then) named path,
i.e.
>E:\SQLData\Linked.mdb. I experimented with various
linkedsvrlogins
>all to no avail. I was only able to finally grant access
to the
>simple domain users by allowing this group "Local Group"
permissions
>as Administrators on the SQL box. Incidentally, the
folder where my
>linked database was stored had wide open "everyone"
permissions.
>
>There is no way this behavior is by design. Can someone
tell me what
>is missing from this puzzle?
>
>SQL 2K Service pack 3
>Jet Service Pack 5
>Access 97 database
>
>Thanks,
>Scott
>.
>

Relevant Pages

  • Re: Linked Server Access Problems
    ... > Under SQL Server's Linked Servers, ... >>database on a SQL 2K box. ...
    (microsoft.public.sqlserver.security)
  • Linked Server Access Problems
    ... I have recently struggled with granting access to a linked server ... The SQL Server service was running ... database was linked using a named path, ... I experimented with various linkedsvrlogins ...
    (microsoft.public.sqlserver.security)
  • Re: Help with error 3624.
    ... This is the exact location for SQL 7 service pack 4. ... >> select in a database. ... >> The dump is somethin like this. ...
    (microsoft.public.sqlserver.server)
  • Re: The parameter is Incorrect
    ... of the database, try running a trace to see where the error ... Try applying the latest service pack on the PC where you get ... SQL Server 2005. ...
    (microsoft.public.sqlserver.clients)
  • Re: Linked Server Access Problems
    ... Try using a sql server account instead of a windows ... >>>database on a SQL 2K box. ...
    (microsoft.public.sqlserver.security)