FIX: You receive an exception when you call an extended stored procedure from an ASP.NET Web application

This article has been archived. It is offered "as is" and will no longer be updated.
When you call an extended stored procedure that raises an error that has a low severity of less than 10 from a Microsoft .NET Framework Web application, you may receive one of the following exception error messages:

Error message 1
A severe error occurred on the current command. The results, if any, should be discarded.
Error message 2
General network error. Check your network documentation.
The connection is returned to the connection pool. The next calls that are made by using the same connection fail.
A SQL Server managed provider parses the Tabular Data Stream (TDS) packet incorrectly.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
  Date         Time   Version            Size    File name--------------------------------------------------------------15-Jul-2004  18:56  1.1.4322.1061   1,294,336  
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
A call to the same stored procedure from a standard Microsoft ASP.NET Web page by using classic Microsoft ADO displays the correct error message and does not cause any connection problems.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
156099 How to debug an extended stored procedure
190987 How to use extended stored procedures

Article ID: 872939 - Last Review: 10/27/2013 06:00:17 - Revision: 1.3

  • Microsoft ADO.NET 1.1
  • kbnosurvey kbarchive kbfix kbbug kbhotfixserver kbqfe KB872939