odbc errors on terminal server

[paul_tomlin]

We connect via terminal services to an excel spreadsheet that has an
ODBC link to an access database using a pivot table, when we try to
refresh the data within the excel spreadsheet we receive the following
error "the microsoft jet database engine cannot find the input table or
query....."

this works ok if the user connects to terminal services as the
administrator however if they connect as any other issue it won't work

Anyone got any ideas?

(have tried 2000 ts and 2003 ts)

[Erland Sommarskog]

(pa*********@hotmail.com) writes:

We connect via terminal services to an excel spreadsheet that has an
ODBC link to an access database using a pivot table, when we try to
refresh the data within the excel spreadsheet we receive the following
error "the microsoft jet database engine cannot find the input table or
query....."

this works ok if the user connects to terminal services as the
administrator however if they connect as any other issue it won't work

Anyone got any ideas?

Well, neither do I know Terminal Services, nor do I know Access. All I
can say is that a newsgroup for SQL Server is probably not the best place
to hope for an answer to your question.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

[Greg D. Moore \(Strider\)]

"Erland Sommarskog" <es****@sommarskog.se> wrote in message
news:Xn**********************@127.0.0.1...

(pa*********@hotmail.com) writes:

We connect via terminal services to an excel spreadsheet that has an
ODBC link to an access database using a pivot table, when we try to
refresh the data within the excel spreadsheet we receive the following
error "the microsoft jet database engine cannot find the input table or
query....."

this works ok if the user connects to terminal services as the
administrator however if they connect as any other issue it won't work

Anyone got any ideas?
Well, neither do I know Terminal Services, nor do I know Access. All I
can say is that a newsgroup for SQL Server is probably not the best place
to hope for an answer to your question.

Actually I'll hazard a guess.

Terminal Server isn't the issue.

ODBC is. Sounds like they setup the DSN on a per USER basis (i.e.
administrator) not a system DSN.



--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

[John Weinshel]

As others have noted, a TS list may be more helpful, but it is possible the
culprit is a combination of the two worlds (TS and ODBC). Since the setup
works for admins, I wonder if the DNS isn't setup as limited in scope to one
TS profile. If so, you can either re-configure the DNS to make it available
to all users, or create DNS's for other users. Just how this plays out would
also depend on whether or not domains are involved. But the general idea is
that, in some way or another, some privilege issue is denying access to the
DNS.
<pa*********@hotmail.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...

We connect via terminal services to an excel spreadsheet that has an
ODBC link to an access database using a pivot table, when we try to
refresh the data within the excel spreadsheet we receive the following
error "the microsoft jet database engine cannot find the input table or
query....."

this works ok if the user connects to terminal services as the
administrator however if they connect as any other issue it won't work

Anyone got any ideas?

(have tried 2000 ts and 2003 ts)