Linked Server problems with Visual Foxpro

My company is using SQL 2000 and a Visual Foxpro
database. In order to perform joint queries against the
two data sources, we set up a linked server definition to
the VFP data source. Everything was working perfectly
until the other day, when I noticed that the server had
not been updated in quite some time. I installed SQL 2000
SP3a, which worked just fine. However, after that, when I
submit a query that uses the VFP linked server, it does
not work like it did. If the VFP part of the query is
going against a local view defined in the VFP database,
sometimes it works, sometimes it doesn't. There are no
error messages, nothing to indicate there is a problem.
It just doesn't return any rows. This is true if I do the
query through EM, Query Analyzer, or via ODBC connection
to the server. This is a critical situation. I even went
so far as to remove SQL 2000 and re-install and NOT
upgrade to SP3a. No change. Any assitance in this area
would be greatly appreciated. Thank youJohn,
It's never a good idea to just apply service packs without testing first.
Have a look here and see if this addresses your issue:
http://support.microsoft.com/default.aspx?scid=kb;en-us;810474&Product=sql2k
--
Andrew J. Kelly
SQL Server MVP
"John" <kcmo_710@.yahoo.com> wrote in message
news:00f001c3afbb$07f640f0$7d02280a@.phx.gbl...
> My company is using SQL 2000 and a Visual Foxpro
> database. In order to perform joint queries against the
> two data sources, we set up a linked server definition to
> the VFP data source. Everything was working perfectly
> until the other day, when I noticed that the server had
> not been updated in quite some time. I installed SQL 2000
> SP3a, which worked just fine. However, after that, when I
> submit a query that uses the VFP linked server, it does
> not work like it did. If the VFP part of the query is
> going against a local view defined in the VFP database,
> sometimes it works, sometimes it doesn't. There are no
> error messages, nothing to indicate there is a problem.
> It just doesn't return any rows. This is true if I do the
> query through EM, Query Analyzer, or via ODBC connection
> to the server. This is a critical situation. I even went
> so far as to remove SQL 2000 and re-install and NOT
> upgrade to SP3a. No change. Any assitance in this area
> would be greatly appreciated. Thank you

Linked Server / "nt authority" error

The company just got a new SQL Server. *finally*, we now have a dev server
and a production server. But apparently, this huge multinational
corporation has no one that knows how to set one up.
We're trying to set each of them up with a link to the other via
"sp_AddLinkedServer"
Running the stored procedure to configure the link worked, and now, when
using EM to connect to HorSql02, we can see the link for HorSql01, but when
clicking on "tables" or "views" under the link in EM, everyone is getting
the same message:
Error 18456: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
I can't understand why this is happening, since we all connect using Windows
Authentication, we all have (at least in the dev group) dbo permissions on
HorSql01, but this error appears to everyone that attempts to connect to
HorSql01 through the link inside HorSql02.
Peace & happy computing,
Mike Labosh, MCSD
"Escriba coda ergo sum." -- vbSenseiMike,
You have to map logins between both servers. See sp_addlinkedsrvlogin and
"Security Account Delegation" in BOL.
AMB
"Mike Labosh" wrote:

> The company just got a new SQL Server. *finally*, we now have a dev serve
r
> and a production server. But apparently, this huge multinational
> corporation has no one that knows how to set one up.
> We're trying to set each of them up with a link to the other via
> "sp_AddLinkedServer"
> Running the stored procedure to configure the link worked, and now, when
> using EM to connect to HorSql02, we can see the link for HorSql01, but whe
n
> clicking on "tables" or "views" under the link in EM, everyone is getting
> the same message:
> Error 18456: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
> I can't understand why this is happening, since we all connect using Windo
ws
> Authentication, we all have (at least in the dev group) dbo permissions on
> HorSql01, but this error appears to everyone that attempts to connect to
> HorSql01 through the link inside HorSql02.
> --
> Peace & happy computing,
> Mike Labosh, MCSD
> "Escriba coda ergo sum." -- vbSensei
>
>