"Severe" Linked Server Error

From: SQLDex <SirSql@xxxxxxxxxxx>
Date: Mon, 27 Aug 2007 11:16:17 -0700

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.

.

Follow-Ups:
- Re: "Severe" Linked Server Error
  - From: Erland Sommarskog

Prev by Date: Re: How can I remove Public access to SQL Express db's?
Next by Date: Re: SQL Express: is there a commandline way to set the default static port of a named instance?
Previous by thread: Re: Permissions
Next by thread: Re: "Severe" Linked Server Error
Index(es):
- Date
- Thread

Relevant Pages

Re: "Severe" Linked Server Error
... A severe error occurred on the current command. ... The thing is, set nocount on is already in the procedure, so this ... then it's some bug in SQL Server. ...
(microsoft.public.sqlserver.security)
Re: A severe error has occurred - HELP!!!
... Executing sp_addmergepublication in SQL Server requires membership in ... the sysadmin or db_owner roles--does your client app connection string ... >A severe error has occurred on the current command. ... >This is command works fine from query analyzer. ...
(microsoft.public.dotnet.framework.adonet)