I have an Access database that exists on a network share
that I'm trying to link to as a linked server from SQL
Server. Sitting at the SQL server machine, I can create
the linked server (both by EM and sql), connect to the
access db, query data, see tables, etc with no problems.
However, if I go to another machine and try to access the
linked database, either through EM or through sql, I get
this error message:
Server: Msg 7399, Level 16, State 1, Procedure
sp_tables_ex, Line 20
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 '\\server\path\database.mdb'. It is already opened
exclusively by another user, or you need permission to
view its data.]
OLE DB error trace [OLE/DB
Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
The SQL server service is running as a domain user with
full access to the network share.
Any help?"Hobbes159" <anonymous@.discussions.microsoft.com> wrote in message
news:eQDAz289DHA.3436@.tk2msftngp13.phx.gbl...
> I have an Access database that exists on a network share
> that I'm trying to link to as a linked server from SQL
> Server. Sitting at the SQL server machine, I can create
> the linked server (both by EM and sql), connect to the
> access db, query data, see tables, etc with no problems.
> However, if I go to another machine and try to access the
> linked database, either through EM or through sql, I get
> this error message:
> Server: Msg 7399, Level 16, State 1, Procedure
> sp_tables_ex, Line 20
> 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 '\\server\path\database.mdb'. It is already opened
> exclusively by another user, or you need permission to
> view its data.]
> OLE DB error trace [OLE/DB
> Provider 'Microsoft.Jet.OLEDB.4.0'
> IDBInitialize::Initialize returned 0x80004005: ].
> The SQL server service is running as a domain user with
> full access to the network share.
Does the domain user account have MODIFY permissions at the NTFS file layer?
The sql server service account must have the ability to create files, such
as the associated *.ldb file.
Steve|||Yes, the domain account has full access to the share (read, write, delete).
The linked database works fine from the SQL server machine, it just won't
work from any other machine.
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:OWnvfl99DHA.1428@.TK2MSFTNGP12.phx.gbl...
> "Hobbes159" <anonymous@.discussions.microsoft.com> wrote in message
> news:eQDAz289DHA.3436@.tk2msftngp13.phx.gbl...
> > I have an Access database that exists on a network share
> > that I'm trying to link to as a linked server from SQL
> > Server. Sitting at the SQL server machine, I can create
> > the linked server (both by EM and sql), connect to the
> > access db, query data, see tables, etc with no problems.
> > However, if I go to another machine and try to access the
> > linked database, either through EM or through sql, I get
> > this error message:
> >
> > Server: Msg 7399, Level 16, State 1, Procedure
> > sp_tables_ex, Line 20
> > 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 '\\server\path\database.mdb'. It is already opened
> > exclusively by another user, or you need permission to
> > view its data.]
> > OLE DB error trace [OLE/DB
> > Provider 'Microsoft.Jet.OLEDB.4.0'
> > IDBInitialize::Initialize returned 0x80004005: ].
> >
> > The SQL server service is running as a domain user with
> > full access to the network share.
> Does the domain user account have MODIFY permissions at the NTFS file
layer?
> The sql server service account must have the ability to create files, such
> as the associated *.ldb file.
> Steve
>|||Have you installed the latest Jet service pack and MDAC release on your SQL
Server?
Steve
"Hobbes159" <anonymous@.discussions.microsoft.com> wrote in message
news:e3$m6p#9DHA.3176@.TK2MSFTNGP11.phx.gbl...
> Yes, the domain account has full access to the share (read, write,
delete).
> The linked database works fine from the SQL server machine, it just won't
> work from any other machine.
> "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> news:OWnvfl99DHA.1428@.TK2MSFTNGP12.phx.gbl...
> >
> > "Hobbes159" <anonymous@.discussions.microsoft.com> wrote in message
> > news:eQDAz289DHA.3436@.tk2msftngp13.phx.gbl...
> > > I have an Access database that exists on a network share
> > > that I'm trying to link to as a linked server from SQL
> > > Server. Sitting at the SQL server machine, I can create
> > > the linked server (both by EM and sql), connect to the
> > > access db, query data, see tables, etc with no problems.
> > > However, if I go to another machine and try to access the
> > > linked database, either through EM or through sql, I get
> > > this error message:
> > >
> > > Server: Msg 7399, Level 16, State 1, Procedure
> > > sp_tables_ex, Line 20
> > > 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 '\\server\path\database.mdb'. It is already opened
> > > exclusively by another user, or you need permission to
> > > view its data.]
> > > OLE DB error trace [OLE/DB
> > > Provider 'Microsoft.Jet.OLEDB.4.0'
> > > IDBInitialize::Initialize returned 0x80004005: ].
> > >
> > > The SQL server service is running as a domain user with
> > > full access to the network share.
> >
> > Does the domain user account have MODIFY permissions at the NTFS file
> layer?
> > The sql server service account must have the ability to create files,
such
> > as the associated *.ldb file.
> >
> > Steve
> >
> >
>|||Yup, everything is up to date on both machines...
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:uNwFIN$9DHA.2932@.TK2MSFTNGP10.phx.gbl...
> Have you installed the latest Jet service pack and MDAC release on your
SQL
> Server?
> Steve
> "Hobbes159" <anonymous@.discussions.microsoft.com> wrote in message
> news:e3$m6p#9DHA.3176@.TK2MSFTNGP11.phx.gbl...
> > Yes, the domain account has full access to the share (read, write,
> delete).
> > The linked database works fine from the SQL server machine, it just
won't
> > work from any other machine.
> >
> > "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> > news:OWnvfl99DHA.1428@.TK2MSFTNGP12.phx.gbl...
> > >
> > > "Hobbes159" <anonymous@.discussions.microsoft.com> wrote in message
> > > news:eQDAz289DHA.3436@.tk2msftngp13.phx.gbl...
> > > > I have an Access database that exists on a network share
> > > > that I'm trying to link to as a linked server from SQL
> > > > Server. Sitting at the SQL server machine, I can create
> > > > the linked server (both by EM and sql), connect to the
> > > > access db, query data, see tables, etc with no problems.
> > > > However, if I go to another machine and try to access the
> > > > linked database, either through EM or through sql, I get
> > > > this error message:
> > > >
> > > > Server: Msg 7399, Level 16, State 1, Procedure
> > > > sp_tables_ex, Line 20
> > > > 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 '\\server\path\database.mdb'. It is already opened
> > > > exclusively by another user, or you need permission to
> > > > view its data.]
> > > > OLE DB error trace [OLE/DB
> > > > Provider 'Microsoft.Jet.OLEDB.4.0'
> > > > IDBInitialize::Initialize returned 0x80004005: ].
> > > >
> > > > The SQL server service is running as a domain user with
> > > > full access to the network share.
> > >
> > > Does the domain user account have MODIFY permissions at the NTFS file
> > layer?
> > > The sql server service account must have the ability to create files,
> such
> > > as the associated *.ldb file.
> > >
> > > Steve
> > >
> > >
> >
> >
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment