SQL 2000 DISTRUBUTED QUERIES FAIL

[Styl_US]

We recently upgraded our SQL 7 servers to 2000, and we have a good
deal of distributed queries in the form of Stored Procedures that run
between them throughout the day. After the upgrade, I began getting
the "CONNECTION BUSY PROCESSING RESULTS FROM ANOTHER COMMAND" error.
This is intermittent but is wreaking havoc on our operations. The same
query ran fine on the 7 server setup. I have exhausted all options
that I know of. All of the postings I have seen on these boards
relate to recordsets and ADO and having cursorlocations set
incorrectly, our stored procedure simply selects a count(*) from a
table on a remote server. Doesn't seem to make sense. Anyone seen
this before or know a remedy? Thanks in advance.

Dave

[Simon Hayes]

dm*******@hotmail.com (Styl_US) wrote in message news:<16**************************@posting.google. com>...

We recently upgraded our SQL 7 servers to 2000, and we have a good
deal of distributed queries in the form of Stored Procedures that run
between them throughout the day. After the upgrade, I began getting
the "CONNECTION BUSY PROCESSING RESULTS FROM ANOTHER COMMAND" error.
This is intermittent but is wreaking havoc on our operations. The same
query ran fine on the 7 server setup. I have exhausted all options
that I know of. All of the postings I have seen on these boards
relate to recordsets and ADO and having cursorlocations set
incorrectly, our stored procedure simply selects a count(*) from a
table on a remote server. Doesn't seem to make sense. Anyone seen
this before or know a remedy? Thanks in advance.

Dave

I don't know what the issue is, but it would help if you could give
some additional information about your environment. Have you got the
latest servicepacks installed? Are the linked servers also MSSQL, or
some other database? How are you calling the stored procedures (ADO,
ODBC)? Do you get the errors if you execute the procedures directly in
Query Analyzer? Etc.

Simon