BUG: Many WRITETEXT Calls Causes DB-Library Error 10005

 Last reviewed: December 30, 1997
Article ID: Q178642
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: Windows NT: 17696 (6.5)

SYMPTOMS

After performing approximately 32,000 WRITETEXT or UPDATETEXT operations in a stored procedure, a DB-Library application will get DB-Library error 10005: "DBPROCESS is dead or not enabled." This problem does not occur with ODBC-based clients.

WORKAROUND

To work around this problem, do any one of the following;

  • Avoid using large numbers of WRITETEXT statements in stored procedures.
  • Run the WRITETEXT statements outside of the stored procedure in a batch.
  • Add SELECT statements to return data from the stored procedure between large numbers of WRITETEXT statements.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: Process command commands st proc stproc db lib
dblib
Keywords : kbbug6.50 SSrvDB_Lib SSrvStProc SSrvTran_SQL
Version : WINNT:6.5
Platform : winnt
Issue type : kbbug
Solution Type : kbworkaround

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.