Re: Linked Server Access Problems
From: Ricky Artigas (rya@easycall.net.ph)
Date: 11/03/02
- Next message: Ricky Artigas: "Cannot generate SSPI context"
- Previous message: BP Margolin: "Re: View Security"
- In reply to: scott: "Re: Linked Server Access Problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Ricky Artigas" <rya@easycall.net.ph> Date: Sat, 2 Nov 2002 20:28:33 -0800
Try using a sql server account instead of a windows
nt/2000 account.
;o)
Ricky Artigas
>-----Original Message-----
>Yes, the simple methods spelled out by MSDN were
attempted.
>
>Scott
>
>
>"Ricky Artigas" <rya@easycall.net.ph> wrote in message
news:<48e001c28223$53ad2e80$3aef2ecf@TKMSFTNGXA09>...
>> 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
>> >.
>> >
>.
>
- Next message: Ricky Artigas: "Cannot generate SSPI context"
- Previous message: BP Margolin: "Re: View Security"
- In reply to: scott: "Re: Linked Server Access Problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
