PRB: Error 10001: NULL DBPROCESS Pointer Encountered

Last reviewed: April 25, 1997
Article ID: Q78028

The information in this article applies to:

  - Microsoft SQL Server Programmer's Toolkit, version 4.2

SYMPTOMS

When using the Visual Basic Library for SQL Server, calling the SqlInit$() function causes the following VBSQL error message to occur:

   Error 10001:  NULL DBPROCESS pointer encountered

CAUSE

When the SqlInit$() function is called, VBSQL creates and maintains information about the program calling it. This prevents conflicts between programs that use VBSQL concurrently. For VBSQL to release this information, the programs must call SqlWinExit just before it exits. If SqlWinExit is not called, when another VBSQL program is run, the VBSQL program will return an error message. Despite the error message, the SQL Server connection should work properly.

WORKAROUND

To eliminate this problem, make sure that SqlWinExit is called prior to calling the SqlInit$() function. This can be accomplished by making sure SqlWinExit is called whenever a VBSQL program is closed.

Additional query words:
Keywords : kbinterop SSrvVisB
Version : 4.2
Platform : WINDOWS

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: April 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.