![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Anyone, any clues? Suggestions? Ideas? Anything? |
#3
| |||
| |||
|
|
On Thu, 16 Dec 2010 16:10:12 +0100, Hugo Kornelis wrote: On Thu, 16 Dec 2010 15:55:20 +0100, Toni Alfirevic toni.alfirevic (AT) gmail (DOT) com> wrote: (snip) Anyone, any clues? Suggestions? Ideas? Anything? Without seeing the code, or the error messagesd (if any) returned when running the code? No. I'm not actually gonna put in the whole procedure. Just the code that is problematic. *snip* |
#4
| |||
| |||
|
|
Msg 0, Level 11, State 0, Line 0 A severe error occurred on the current command. The results, if any, should be discarded. |
#5
| |||
| |||
|
|
Toni Alfirevic (toni.alfirevic (AT) gmail (DOT) 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. |
|
Try running the same command from SQLCMD and OSQL, this may or may not give more information. What does SELECT @@version return? |
#6
| |||
| |||
|
|
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. |
|
@@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 <X64> (Build 7600: ) |
![]() |
| Thread Tools | |
| Display Modes | |
| |