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

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server 2005 General Discussion » A severe error occurred on the current...

33 posts, Page 1 of 4

1 2 3 4 »»»

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

Rate Topic

Display Mode

Topic Options

Author

Message

Arshad khan-791094

Posted Monday, June 23, 2008 2:31 AM

Grasshopper

Group: General Forum Members
Last Login: Sunday, November 07, 2010 11:37 PM
Points: 14, Visits: 17

Hi all, i have some problem with my SQL Server, if i am creating any new Db, and i am accessing through my .NET Application, that time its giving error like that, but if i am Executing any query from my Managememnt Studio then its working fine, but while my Asp.net page its giving Error Like that

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

Plz, check this problem and let me know.

Thanks

Post #521583

Suresh B.

Posted Monday, June 23, 2008 7:15 AM

Ten Centuries

Group: General Forum Members
Last Login: Wednesday, June 12, 2013 2:54 AM
Points: 1,076, Visits: 5,128

>> i am accessing through my .NET Application, that time its giving error like that, but if i am Executing any query from my Managememnt Studio then its working fine, but while my Asp.net page its giving Error

Are you using stored procedure? If NO, create a stored procedure and call it from your .NET application. It may work.

Post #521748

Avishkar Meshram

Posted Tuesday, June 24, 2008 6:12 AM

SSC Rookie

Group: General Forum Members
Last Login: Tuesday, January 29, 2013 12:23 AM
Points: 42, Visits: 310

There is a Hotfix available on microsoft site.
Pl refer http://support.microsoft.com/kb/910416

Post #522479

josp

Posted Friday, December 10, 2010 2:04 PM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, September 20, 2012 3:26 PM
Points: 7, Visits: 18

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

Changed my delete query to delete based on primary key

"delete from table where pk in (select pk from table where num=5)"

for whatever reason "delete from table where num=5" was giving severe error

Post #1033223

GSquared

Posted Friday, December 10, 2010 2:18 PM

SSCoach

Group: General Forum Members
Last Login: 2 days ago @ 1:45 PM
Points: 15,442, Visits: 9,572

Might be a recursion problem with the sub-query.

I have to ask, why the sub-query at all, or are these two different tables?

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

Post #1033233

GilaMonster

Posted Friday, December 10, 2010 3:02 PM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 9:16 AM
Points: 38,086, Visits: 30,379

Just in case, run the following and check that it doesn't return anything.

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1033240

SQL-DBA-01

Posted Tuesday, December 21, 2010 9:47 AM

Right there with Babe

Group: General Forum Members
Last Login: Yesterday @ 6:02 AM
Points: 738, Visits: 1,147

I too am facing the same error..

Msg 0, Level 11, State 0, Line 0

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

This is occurring while running the below script.

update <tab_name> set code = 'CANCELLED' where nbr = 'A325'

Unable to figure out whether this is due to dependency to this table or some other issue. The server timeout value is set as: 10 mins which is quite good.

Any suggestion would be highly helpful.

Thanks.

Post #1037817

SQL-DBA-01

Posted Wednesday, December 22, 2010 6:15 AM

Right there with Babe

Group: General Forum Members
Last Login: Yesterday @ 6:02 AM
Points: 738, Visits: 1,147

Any suggestion please??

Thanks.

Post #1038215

SQL-DBA-01

Posted Monday, December 27, 2010 10:55 AM

Right there with Babe

Group: General Forum Members
Last Login: Yesterday @ 6:02 AM
Points: 738, Visits: 1,147

Can anyone please recommend further?

Thanks.

Post #1039507

Congruent Influence

Posted Saturday, January 08, 2011 7:20 PM

Valued Member

Group: General Forum Members
Last Login: Thursday, June 06, 2013 10:08 AM
Points: 70, Visits: 136

I recently ran across this issue in one of my data conversions for a client. Same error but different symptoms. I was able to narrow the issue down to a specific concatenation of dateparts and then converting to a datetime as well as a specific join causing the problem on one of my queries.

My issue was resolved by adding indexes on the join table.

example:
select convert(datetime, A.MO + '/' + A.DY + '/' A.YR)
from A
join B on A.id = b.id
left join C on A.id = C.id
AND a.id2 = C.id2

In the example above there weren't indexes on table C. As soon as I added them on id and id2 the error went away. Hope this inspires you to look a different direction and resolve your issue.

Remember this when a developer tells you it will just be temporary. Temporary = Permanent.

Post #1044933

« Prev Topic | Next Topic »

33 posts, Page 1 of 4

1 2 3 4 »»»

Permissions