'out-of-band' error
Patrick Nee
What does this error mean? It is occuring in a medium length query (5
minutes) from ISQL.
____
DB-Library: Possible network error: Error in sending out-of-band data to
SQL Server.
Net-Library error 232: ConnectionWrite (GetOverLappedResult()).
DB-Library Process Dead - Connection Broken
_____
Patrick Nee
pat...@sitesoft.com
Sitesoft, LLC
Neil Pike
Patrick,
It's a bug in SQL Server (one example below). What version of SQL/SP
are you using. What net-lib? How are you submitting the query (via
ISQL/W, ODBC, ASP etc.)?
Can you post a repro script?
---------------------------------
PSS ID Number: Q170994
Article last modified on 03-06-1998
WINNT:6.5
winnt
======================================================================
-----------------------------------------------------------------------
----
The information in this article applies to:
- Microsoft SQL Server, version 6.5
-----------------------------------------------------------------------
----
BUG #: 17053
SYMPTOMS
========
When updating a cursor, SQL Server generates an access violation (AV)
and
generates a stack trace and a dump file. From ISQL, users receive the
following error:
DB-Library: Possible network error: Error in sending out-of-band
data to
SQL Server.
Net-Library error 232: ConnectionWrite (GetOverLappedResult()).
ODBC users receive the following error and the client application
typically
stops responding (including the development environment, such as Visual
Basic):
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
In Visual Basic, the AV occurs when an Edit/Update is performed against
a
recordset of a VIEW that contains an ANSI style INNER JOIN, or when an
equi-
join to a SQL Server cursor is opened and an attempt is made to update
that
cursor. The recordset's cursor type (KEYSET, DYNAMIC, or FORWARD_ONLY)
has
no effect on the failure. That is, it fails no matter what cursor type
is
used.
This problem does not occur with a STATIC cursor because a STATIC
cursor is
read-only, and the AV occurs during the attempt to update.
WORKAROUND
==========
To work around this problem, create the view using Transact-SQL style
outer
joins (for example, *= or =*).
For example, use the following statements to create the view:
CREATE VIEW view_TEST AS select authors.* from authors,
authors_useraccess where authors.au_id *= authors_useraccess.au_id
and
user = authors_useraccess.usercode
GO
Neil Pike MVP/MCSE
Protech Computing Ltd