I ran this on the 32-bit SQL Server 2000, and it appears to have resolved the issue.

Full credit must go to uber1024 (http://ncane.com/awh).

USE master

go

create procedure sp_tables_info_rowset_64

@table_name sysname,

@table_schema sysname = null,

@table_type...

I'm just guessing here, but it sounds like the transaction log is getting corrupted, or you're running out of space on the drive where tempdb is stored. Another suggestion is...

Why do you ask?

I haven't come up with a solution, so I installed SQL 2005 on the same machine as SQL 2000 (32-bit) and linking works fine. This is not an adequate solution...

Yes - I can ping the 2000 server from 2005 (see original post).

I did also run instcat.sql yesterday already.

I think Microsoft PSS is the best option for now.

Output for your question:

name,network_name,status,id,collation_name,connect_timeout,query_timeout

MYSERVER,MYSERVER,data access,use remote collation,1,NULL,0,0

From Management Studio, I try:

1. New Linked Server

2. Choose a name, e.g. MYSERVER. This matches the server name on the network.

3. Server Type: it...

ODBC won't work either - Microsoft provides a 32-bit DLL for that, but SQL is running 64-bit. Like I said, everything works EXCEPT linked servers, no matter what I've tried.

Thanks...

I've tried that. It also didn't work.

Hi Markus

It did not work. I still get the same error:

Msg 7399, Level 16, State 1, Line 1

The OLE DB provider "SQLNCLI" for linked server "MYSERVER" reported an error. The...

Hi Markus

I will check it out tomorrow and let you know the outcome. I'm sitting in Johannesburg so it's 6:40pm right now.

Randolph