SYMPTOMS
If an Open Data Services (ODS) application, such as SQL Server, is
processing a large number of client disconnection events, you may receive a
handled access violation (AV) within Open Data Services.
Open Data Services is designed to shut down upon encountering an access
violation. Therefore, when this problem occurs, the ODS application (such
as SQL Server) will also be stopped.
With SQL Server, the ERRORLOG file will contain output that looks something
like the following before the process exits:
8/05/02 01:19:03.93 spid180 ******************************************
8/05/02 01:19:03.96 spid180 *
8/05/02 01:19:03.98 spid180 * STACK DUMP:
8/05/02 01:19:03.98 spid180 *
8/05/02 01:19:04.00 spid180 * Exception Address = 002780ab
8/05/02 01:19:04.01 spid180 * Exception Code = c0000005
8/05/02 01:19:04.03 spid180 * Access Violation occurred reading
address 001a7a30
The following errors may also be seen prior to encountering this particular ODS Access Violation:
98/05/13 13:56:14.93 ods Error : 17832, Severity: 18, State: 0
98/05/13 13:56:14.93 ods Unable to read login packet(s).
98/05/13 13:56:15.03 ods Error : 17824, Severity: 10, State: 0
98/05/13 13:56:15.03 ods Unable to write to ListenOn connection
'\\.\pipe\sql\query', loginname 'sa', hostname ''.
98/05/13 13:56:15.03 ods OS Error : 232, The pipe is being closed.
98/05/13 13:56:15.06 ods Error : 17824, Severity: 10, State: 0
98/05/13 13:56:15.06 ods Unable to write to ListenOn connection
'\\.\pipe\sql\query', loginname 'sa', hostname ''.
98/05/13 13:56:15.06 ods OS Error : 109, The pipe has been ended.
98/05/13 13:56:15.24 spid42 Error : 1608, Severity: 21, State: 2
98/05/13 13:56:15.24 spid42 A network error was encountered while
sending results to the front end. Check the SQL Server errorlog for more
information.
98/05/13 23:32:36.42 ods Error : 17805, Severity: 18, State: 0
98/05/13 23:32:36.42 ods Invalid buffer received from client.
However, these errors can also be encountered without seeing an ODS Access Violation. For more information about troubleshooting errors 17824 and 17832, please see the following articles in the Microsoft Knowledge Base:
STATUS
Microsoft has confirmed this to be a problem in SQL Server
6.5. This problem has been corrected in U.S. Service Pack 5
for Microsoft SQL Server 6.5. For information about
how to download and install the latest SQL Server Service Pack, see
the following Microsoft Web site:
For more information, contact your primary support provider.