Using SQL2K SP4, I'm getting a weird error when I run a stored
procedure from a remote server:

exec remoteserver.database.dbo.proc

returns:

Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command.  The results, if any,
should be discarded.

Googling around, I did find a reference to the 'set nocount on'
command as a fix for this.  Sure enough, when a add the clause above
the exec statement, the error goes away.

The thing is, set nocount on is already in the procedure, so this
shouldn't happen.  Or so I thought.   The data does return, but I and
our monitoring tools do not like to see "severe error" messages.

Any ideas as to what is going on?  As this is 2K, and not 2005, I
don't think kb928372 applies.

TIA.