Getting "A severe error occurred on the current command" after SP4

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Codebase has been in place for 1.5 years. Current version running since
12/2005. First use of a command object that has 14 parameters.

Now I get this error on first use, subsequents work fine. sproc work
actually completes, but error is raised.
 
Sorry for the incomplete post, I was trying to get to a meeting. Anyway, to
decipher my post here's the situation:

I have a sproc that takes about 12 params and creates a SQL Agent job.
The sproc is invoked from a command object's ExecuteNonQuery method in vb.net.
The system has worked well for 1.5 years.
The running version of the system has been in place since 12/2005.
The sproc actually does it's work, as the job is created and runs fine.
However, a client side error is raised (see below).
My code logs the error and then retries after a delay.
The retry and subsequent job creations, ALL involving open, executenonquery,
close, (about 10 per batch) work without error.
This means the initial execution that errors client side is run TWICE server
side.
The process goes on to other work and repeats on a new batch about 2 minutes
later, getting the same initial execution error.
Environment is Windows 2K3 running SQL 2K SP4, clustered, Quad, 4 GB RAM.

The major change preceeding this problem is an upgrade from SQL 2000 SP3a to
SP4. There was one other seemingly unrelated change on the system that I'll
reserve for later.

The error I get is this (not very helpful):

Error Source: .Net SqlClient Data Provider
Error Type: System.Data.SqlClient.SqlException
Error Message: A severe error occurred on the current command. The results,
if any, should be discarded.
SQLErr Details Follow--
SQLErr Index:0
SQLErr Number: 0 Message = A severe error occurred on the current command.
The results, if any, should be discarded.
SQLErr Line Number:0
SQLErr Source:.Net SqlClient Data Provider

I'm thinking the error is some prepare artifact that doesn't happen
subequently because of connection pooling? Then 2 minutes later it all
starts over...

Any ideas?
 
Hi Dwaine,

Is this a Web form app which is running under .NET framework 1.1? If so, I
suggest you try to take a look at the following KB article. This might be a
known issue which is caused by A SQL Server managed provider parses the
Tabular Data Stream (TDS) packet incorrectly. You can obtain a hotfix from
the Microsoft PSS.

http://support.microsoft.com/kb/872939/en-us

If that still doesn't work, please also install Windows 2003 service pack 1
from windows update.

Kevin Yu
Microsoft Online Community Support

============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Back
Top