Parse: severe error occurred on the current command

Question

Parse: severe error occurred on the current command

pdb DBA

SSC-Addicted

Points: 407
More actions
April 17, 2009 at 5:06 pm

#133187

We have a dev server box that, expectedly, everyone abuses so this could be any number of things. However, when I am connected to the server and attempt to parse a query (of any kind - even something as simple as select * from sys.columns on master DB) I get the following error:
.Net SqlClient Data Provider: Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
This happens if I'm on my local, personal copy of SSMS connected to the server or if I RDC into the dev server's SSMS and connect to the SQL Server instance running on this server. It does NOT happen if I am connected to any other server (either from my desktop or from the RDC session).
Results of xp_msver:
1ProductNameNULLMicrosoft SQL Server
2ProductVersion5898241ProductNameNULLMicrosoft SQL Server
2ProductVersion5898249.00.4035.00
3Language1033English (United States)
4PlatformNULLNT AMD64
5CommentsNULLNT AMD64
6CompanyNameNULLMicrosoft Corporation
7FileDescriptionNULLSQL Server Windows NT - 64 Bit
8FileVersionNULL2005.090.4035.00
9InternalNameNULLSQLSERVR
10LegalCopyrightNULL© Microsoft Corp. All rights reserved.
11LegalTrademarksNULLMicrosoft® is a registered trademark of Microsoft Corporation. Windows(TM) is a trademark of Microsoft Corporation
12OriginalFilenameNULLSQLSERVR.EXE
13PrivateBuildNULLNULL
14SpecialBuild264437760NULL
15WindowsVersion2483819575.2 (3790)
16ProcessorCount44
17ProcessorActiveMask4 f
18ProcessorType8664NULL
19PhysicalMemory81918191 (8588869632)
20Product IDNULLNULL
3Language1033English (United States)
4PlatformNULLNT AMD64
5CommentsNULLNT AMD64
6CompanyNameNULLMicrosoft Corporation
7FileDescriptionNULLSQL Server Windows NT - 64 Bit
8FileVersionNULL2005.090.4035.00
9InternalNameNULLSQLSERVR
10LegalCopyrightNULL© Microsoft Corp. All rights reserved.
11LegalTrademarksNULLMicrosoft® is a registered trademark of Microsoft Corporation. Windows(TM) is a trademark of Microsoft Corporation
12OriginalFilenameNULLSQLSERVR.EXE
13PrivateBuildNULLNULL
14SpecialBuild264437760NULL
15WindowsVersion2483819575.2 (3790)
16ProcessorCount44
17ProcessorActiveMask4 f
18ProcessorType8664NULL
19PhysicalMemory81918191 (8588869632)
20Product IDNULLNULL
Any ideas?

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Atif-ullah Sheikh SSChampion Points: 12495 More actions · Answer 1

Check Event Log... you might get something from there...

There are many reasons of this error, print statements, wrong parameter settings, etc. But as for your scenario, i think it is relate dto the authentication problems. also check your rights on the SQL Server.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Sometimes, winning is not an issue but trying.
You can check my BLOG [font="Arial Black"]here[/font][/url][/right]

Gail Shaw SSC Guru Points: 1004514 More actions · Answer 2

Just a thought, can you run a consistency check on the databases on that server?

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

Any errors in the SQL Error log?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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

pdb DBA SSC-Addicted Points: 407 More actions · Answer 3

I log in with sa so authentication issues are doubtful.

No relevant messages in the SQL logs or Windows event logs.

DBCC CHECKDB returns no errors for master, msdb or a few of the random other DB's I checked.

SQL Server is running under LocalSystem account. (I know, I know - I didn't set this machine up.)

Steve Jones - SSC Editor SSC Guru Points: 738643 More actions · Answer 4

Very strange. Does it happen for

sp_who2

select user_name()

select 1

pdb DBA SSC-Addicted Points: 407 More actions · Answer 5

Same error (as above) for all three.

Everything else appears to run fine, it's just the "Parse" functionality.

pdb DBA SSC-Addicted Points: 407 More actions · Answer 6

I think I found it:

http://support.microsoft.com/kb/959028

If I issue SET XACT_ABORT OFF; before hand the parse runs without error (for that session).

Dev machine is on 9.00.4035 so it makes sense I guess. My dev machine is at 9.00.3042.

So now to request the CU and see how that works.

pdb DBA SSC-Addicted Points: 407 More actions · Answer 7

Just to update, applying CU2 did indeed fix the issue.