Hello,
I am trying to create an Linked Server for MS Access in SQL 7.0. I have
executed the following stored procedures with no problem:
exec sp_addlinkedserver
@.server = "PECRM",
@.srvproduct = "Access 97",
@.Provider = "Microsoft.Jet.OLEDB.4.0",
@.datasrc = "\\apollo\sys\apps\datastor\appdata\contdata.mdb"
exec sp_addlinkedsrvlogin
@.rmtsrvname = "PECRM",
@.useself = "false",
@.locallogin = "sa",
@.rmtuser = "Admin",
@.rmtpassword = Null
When I execute the following SQL Statement
SELECT * FROM PECRM...ContAddr
I get the error:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine cannot
open the file '\\apollo\sys\apps\datastor\appdata\contdata.mdb'. It is
already opened exclusively by another user, or you need permission to view
its data.]
In SQL EM I get the dreaded 7399 error, I have followed the suggestions of
changing the SQL server login to an account that I know has access to a temp
directory but with the same results. Can any one help?
Thanks,
DanHello Solex (wonder if this is your real name, remember post with real names
here)
Seems to be that you are using a LDB file to secur your access database.
Information about this
file must be provided too. Look in the provider settings and provide the
path and name
to this security information file.
Jens Süßmeyer.|||Jens,
The access databaes is not using a WorkGroup database for security. In fact
the database is not secured at all.
Any other suggestions?
Thanks,
Dan
"Jens Süßmeyer" <jsuessmeyer@.[REJECT_SPAM]web.de> wrote in message
news:%23w%23XcV1ZDHA.1004@.TK2MSFTNGP12.phx.gbl...
> Hello Solex (wonder if this is your real name, remember post with real
names
> here)
> Seems to be that you are using a LDB file to secur your access database.
> Information about this
> file must be provided too. Look in the provider settings and provide the
> path and name
> to this security information file.
> Jens Süßmeyer.
>|||Hello Dan !
Did you set the database to exclusive ? Does another Lock-File exists, that
you can´t open the db. Look in the
directory of the mdb and search for a lck file. Delete it und try again.
Somethings Access hangs and stop responing which such suspects errors, and
there is nothing left than restarting the host system of the access mdb (if
killing all processes to the network share doesn´t help to fix it)
Jens Süßmeyer.
"solex" <solex@.nowhere.com> schrieb im Newsbeitrag
news:u4mjr41ZDHA.652@.tk2msftngp13.phx.gbl...
> Jens,
> The access databaes is not using a WorkGroup database for security. In
fact
> the database is not secured at all.
> Any other suggestions?
> Thanks,
> Dan
> "Jens Süßmeyer" <jsuessmeyer@.[REJECT_SPAM]web.de> wrote in message
> news:%23w%23XcV1ZDHA.1004@.TK2MSFTNGP12.phx.gbl...
> > Hello Solex (wonder if this is your real name, remember post with real
> names
> > here)
> >
> > Seems to be that you are using a LDB file to secur your access database.
> > Information about this
> > file must be provided too. Look in the provider settings and provide the
> > path and name
> > to this security information file.
> >
> > Jens Süßmeyer.
> >
> >
>
No comments:
Post a Comment