Received assert dialog from what I thought was a runtime SQL Server Client library

From: mmarch (kmmarch_at_yahoo.com)
Date: 03/04/04 

Date: Thu, 4 Mar 2004 07:16:08 -0800

While using the SQL Server Client libraries for accessing a SQL Server 2000 database, I received the following two assertions:

----------------------
Program:<MyApplication>
File: q:\SPHINX\NETLIBS\nt\ssock\src\ntssockc.c
Line: 1471

Expression 1 == pConnectionObject->fCallCheck
----------------------

AND

----------------------
Program:<MyApplication>
File: q:\SPHINX\NETLIBS\nt\ssock\src\ntssockc.c
Line: 957

Expression 0 == pConnectionObject->fCallCheck
----------------------

I don't know why I am receiving assertion dialogs from what I believe is a SQL Server Client runtime library.

The operating system is Windows 2000 Server, Service Pack 2.
The version of the DB-Library and all network libraries is 8.0.194 (date 8/6/2000).

Has anybody seen this problem before?
Does anybody have an explanation for the assertion dialog?
Is there any way to ensure that I do not get assertion dialogs from an OS level?

Thanks,
mmarch

Relevant Pages

  • Re: T-SQL and OLE Automation
    ... A library created as type ActiveX.exe will run out of the SQL Server ... To deploy a .dll, you make it, using the VB6 file/make command, then copy to ... Creating COM libraries with VB6 is probably better discussed in a VB ... > OLE automation and I'm not sure how to write the application on the VB6 ...
    (microsoft.public.sqlserver.programming)
  • Re: Calling COM object from Stored Procedure
    ... I'd recommend that VB6.0 is probably the easiest route for simple libraries ... VB.Net is significantly easier to program certain ... >I know the next release of SQL Server allows .Net stored procedures, ...
    (microsoft.public.sqlserver.programming)
  • Re: Calling COM object from Stored Procedure
    ... I wish to use VB.Net because once the client has upgraded to SQL Server 2005 ... some might even say opposing technologies. ... > libraries & you'll find help here a lot easier than if you choose to ... >>I know the next release of SQL Server allows .Net stored procedures, ...
    (microsoft.public.sqlserver.programming)
  • Re: Cant connect to SQL Server, using Windows Authentication users of SQL server? help
    ... Reza ... There are two ways of connecting to SQL Server ... You can check network libraries on the SQL Server machine by opening the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: T-SQL and OLE Automation
    ... "Greg Linwood" wrote: ... > except that a library created as a .dll will run inside the SQL Server ... therefore sharing & competing for memory with the main SQL process. ... > Creating COM libraries with VB6 is probably better discussed in a VB ...
    (microsoft.public.sqlserver.programming)