Annoying Error Message

Hello,

I recently migrated from 2000 to 2005 database. On the new server, I kept getting this type of error message when there is some sort of join involved and they are not complex join either.

Error - "A severe error occurred on the current command. The results, if any, should be discarded."

ie

select A.Cookie1, A.Cookie2
into BookersLookers_Cookie
from BookersLookers_DataSet A
LEFT JOIN ActionSetup B on A.ActionID = B.ActionID
group by A.Cookie1, A.Cookie2

Is there something in the code where I could prevent this error from happening?

Any insight is appreciated,

-Lawrence

Moving to engine forum|||

Hi SQLChamp,

What is the build of your SQL server?

What is the exact error message you are getting?

Any errors in theerror log?

Jag

|||

Hello Jag Sandhu,

What is the build of your SQL server? 9.00.3042 (X64)

What is the exact error message you are getting? "A severe error occurred on the current command. The results, if any, should be discarded."

Any errors in theerror log? no error log set up

-Lawrence

|||

You encounter an old bug which should have been fixed if you're running sp2.

http://support.microsoft.com/default.aspx/kb/910416

The error log we're interested in is the sql log. You can get it by executing the following sproc.

exec sp_readerrorlog

Please post the result of "select @.@.version" while you're at it.

|||

I posted select @.@.version earlier - 9.00.3042 (X64)

I would find out any logs from sp_readerrorlog

If all else fails, I guess this is a big bug, and hopefully SP2 will fix it.

-Lawrence

|||

Hi

From your buildnumber it seems like you are running SP2 already.

Let us know what you get from error logs.

Jag

|||

Hello,

I received the following error message from sp_readerrorlop

2007-04-30 12:51:18.620 Server Error: 17310, Severity: 20, State: 1.

2007-04-30 12:51:18.620 Server A user request from the session with SPID 57 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.

|||

You should probably do what the message says.

Contact Product Support Services with the dump produced in the log directory.

Or possibly post the .mdmp file on Connect for analysis.

|||

I was wondering if anyone had a fix for this type of error/bug? Any hotfx or work-around?

Our IT Support contacted MS, but MS Production Support is not very responsive in this case. "Severe Error" still occurs in simple join. Any additional help would be much appreciated.

Sincerely,

-Lawrence

|||

SP1 works fine, so I would NOT recommend applying SP2.

-Lawrence