quering an excel limked server

hi all,
I've configured an excel file as a linked server to my sql 2000 server (win
2003)
I used kb 814398 to do that, and now if I run a query againt the excel file
from the server I do get the results.
the problem occures when I try to run the same query from the query analyzer
on a computer in the network. ofcourse, I connect and query againt my sql
server.
I get the following massage:
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: 'I:\prices\opelfrontera9698.xls' is not a
valid path. Make sure that the path name is spelled correctly and that you
are connected to the server on which the file resides.]
OLE DB error trace [OLE/DB Provider 'microsoft.jet.oledb.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
again, if I run the same query from the query analyzer on the server, there
is no error massage.
thanks,
elad.Hi
I assume you followed the KB abd restarted the server?
If this is on a mapped network drive, you may want to try specifying a UNC
name instead.
John
"×?×?×¢×? ש×?×?×?" wrote:
> hi all,
> I've configured an excel file as a linked server to my sql 2000 server (win
> 2003)
> I used kb 814398 to do that, and now if I run a query againt the excel file
> from the server I do get the results.
> the problem occures when I try to run the same query from the query analyzer
> on a computer in the network. ofcourse, I connect and query againt my sql
> server.
> I get the following massage:
> 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: 'I:\prices\opelfrontera9698.xls' is not a
> valid path. Make sure that the path name is spelled correctly and that you
> are connected to the server on which the file resides.]
> OLE DB error trace [OLE/DB Provider 'microsoft.jet.oledb.4.0'
> IDBInitialize::Initialize returned 0x80004005: ].
> again, if I run the same query from the query analyzer on the server, there
> is no error massage.
> thanks,
> elad.

quering an excel limked server

hi all,
I've configured an excel file as a linked server to my sql 2000 server (win
2003)
I used kb 814398 to do that, and now if I run a query againt the excel file
from the server I do get the results.
the problem occures when I try to run the same query from the query analyzer
on a computer in the network. ofcourse, I connect and query againt my sql
server.
I get the following massage:
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: 'I:\prices\opelfrontera9698.xls' is n
ot a
valid path. Make sure that the path name is spelled correctly and that you
are connected to the server on which the file resides.]
OLE DB error trace [OLE/DB Provider 'microsoft.jet.oledb.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
again, if I run the same query from the query analyzer on the server, there
is no error massage.
thanks,
elad.Hi
I assume you followed the KB abd restarted the server?
If this is on a mapped network drive, you may want to try specifying a UNC
name instead.
John
"???? ????" wrote:

> hi all,
> I've configured an excel file as a linked server to my sql 2000 server (wi
n
> 2003)
> I used kb 814398 to do that, and now if I run a query againt the excel fil
e
> from the server I do get the results.
> the problem occures when I try to run the same query from the query analyz
er
> on a computer in the network. ofcourse, I connect and query againt my sql
> server.
> I get the following massage:
> 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: 'I:\prices\opelfrontera9698.xls' is
not a
> valid path. Make sure that the path name is spelled correctly and that yo
u
> are connected to the server on which the file resides.]
> OLE DB error trace [OLE/DB Provider 'microsoft.jet.oledb.4.0'
> IDBInitialize::Initialize returned 0x80004005: ].
> again, if I run the same query from the query analyzer on the server, ther
e
> is no error massage.
> thanks,
> elad.

quering an excel limked server

hi all,
I've configured an excel file as a linked server to my sql 2000 server (win
2003)
I used kb 814398 to do that, and now if I run a query againt the excel file
from the server I do get the results.
the problem occures when I try to run the same query from the query analyzer
on a computer in the network. ofcourse, I connect and query againt my sql
server.
I get the following massage:
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: 'I:\prices\opelfrontera9698.xls' is not a
valid path. Make sure that the path name is spelled correctly and that you
are connected to the server on which the file resides.]
OLE DB error trace [OLE/DB Provider 'microsoft.jet.oledb.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
again, if I run the same query from the query analyzer on the server, there
is no error massage.
thanks,
elad.
Hi
I assume you followed the KB abd restarted the server?
If this is on a mapped network drive, you may want to try specifying a UNC
name instead.
John
"???? ????" wrote:

> hi all,
> I've configured an excel file as a linked server to my sql 2000 server (win
> 2003)
> I used kb 814398 to do that, and now if I run a query againt the excel file
> from the server I do get the results.
> the problem occures when I try to run the same query from the query analyzer
> on a computer in the network. ofcourse, I connect and query againt my sql
> server.
> I get the following massage:
> 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: 'I:\prices\opelfrontera9698.xls' is not a
> valid path. Make sure that the path name is spelled correctly and that you
> are connected to the server on which the file resides.]
> OLE DB error trace [OLE/DB Provider 'microsoft.jet.oledb.4.0'
> IDBInitialize::Initialize returned 0x80004005: ].
> again, if I run the same query from the query analyzer on the server, there
> is no error massage.
> thanks,
> elad.