From: toni.alfirevic@gmail.com   
      
   On Fri, 17 Dec 2010 00:07:36 +0100, Erland Sommarskog wrote:   
      
   > Toni Alfirevic (toni.alfirevic@gmail.com) writes:   
   >> Msg 0, Level 11, State 0, Line 0   
   >> A severe error occurred on the current command.  The results, if any,   
   >> should be discarded.   
   >   
   > So this is a bug. If you look in the SQL Server error log, you will   
   > probably find a stack dump. That is, SQL Server ran into some internal   
   > error like an access violation, and had to kill your process.   
   >   
   > It is also possible that the error happens on the client-side - in fact   
   > the severity of 11 indicates this possibility.   
      
   Client as a application on IIS or client as a Microsoft SQL Server   
   Management Studio?   
      
   Anyway the story goes like this. It has been brought to my attention that   
   something is not working as intended so I've tried runing that specific   
   stored procedure manually from management studio, same stored p. that ASP   
   aplication runs. And the problem is as I've described.   
      
   > Try running the same command from SQLCMD and OSQL, this may or may   
   > not give more information.   
   >   
   > What does SELECT @@version return?   
      
   @@version is on this specific system is:   
      
   Microsoft SQL Server 2008 (SP1) - 10.0.2766.0 (X64)   Feb 25 2010 12:51:37   
   Copyright (c) 1988-2008 Microsoft Corporation  Standard Edition (64-bit) on   
   Windows NT 6.1  (Build 7600: )   
      
   Same issue occurs on:   
   Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)   Apr  2 2010   
   15:48:46   Copyright (c) Microsoft Corporation  Standard Edition (64-bit)   
   on Windows NT 6.1  (Build 7600: ) (Hypervisor)   
      
   And on one version of SQL 2000 currently the VPN server is down so i cant   
   run @@version.   
      
   Odd stuff.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)