Assertion failed!

I'm connecting to a SQL Server 2000, sp3 running on Win2k
Server, SP3, english version from a workstation with
Win2k, sp 3, english version.
The client software is written in C# and I'm using ADO.NET
to connect.
Occasionally I get this fault:
Assertion failed!
Program: ...\..\..\Myprog.exe
File: ..\..\..\nt\ssock\src\ntsockc.c
Line: 1053 (sometimes other lines...)
Expression: 1 == pConnectionObject->fCallCheck
Any suggestions what could be wrong?
/MattiasHi Mattias,
If the Assertion is thrown by the C# application, you need to post in C# or
ADO.NET newsgroup for accurate information, e.g.
microsoft.public.dotnet.languages.csharp,
microsoft.public.dotnet.framework.adonet. The problem should be related to
SQL Server.
When the problem occurs, I suggest that you use Query Analyzer to connect
to the SQL Server from the computer where the problem occurs. If the
problem does not occur, it indicates that the problem is with the
application.
In addition, since it is a random problem, it could be quite complex. You
could also contact Microsoft Product Support Services via
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS, so that
we can have dedicated engineer to assist you.
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Bill Cheng
Microsoft Support Engineer
--
| Content-Class: urn:content-classes:message
| From: "Mattias Andersson" <mattias.andersson@.ip-consult.se>
| Sender: "Mattias Andersson" <mattias.andersson@.ip-consult.se>
| Subject: Assertion failed!
| Date: Mon, 30 Jun 2003 00:17:00 -0700
| Lines: 18
| Message-ID: <067701c33ed7$9931e2e0$a101280a@.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcM+15kxvfxven3cQMytFjuuieMjcA==| Newsgroups: microsoft.public.sqlserver.server
| Path: cpmsftngxa09.phx.gbl
| Xref: cpmsftngxa09.phx.gbl microsoft.public.sqlserver.server:22143
| NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| I'm connecting to a SQL Server 2000, sp3 running on Win2k
| Server, SP3, english version from a workstation with
| Win2k, sp 3, english version.
|
| The client software is written in C# and I'm using ADO.NET
| to connect.
|
| Occasionally I get this fault:
| Assertion failed!
| Program: ...\..\..\Myprog.exe
| File: ..\..\..\nt\ssock\src\ntsockc.c
| Line: 1053 (sometimes other lines...)
|
| Expression: 1 == pConnectionObject->fCallCheck
|
| Any suggestions what could be wrong?
|
| /Mattias
|

ASP/ODBC/Win2k - TCP Connections

Is it normal to see a new TCP connection for every SQL statement
executed [via ADODB.Recordset.Open] when connection pooling is
switched on?
When my ASP application is running there seems to be 1 constant
connection open, and 3 or 4 separate and continually opening/closing
connections. On examining the packets, it seems that each SQL gets
its own connection to the server.
Thanks
()z
If you are using ODBC this is not uncommon. ODBC determines when it needs
to spawn a new connection and does so. This can occur if a connection has
not finished processing all records and another request is sent. A new
connection has to be spawned to service this request.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks Rand
I'll not worry about them in that case.
rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<L71m5yREEHA.3244@.cpmsftngxa06.phx.gbl>...
> If you are using ODBC this is not uncommon. ODBC determines when it needs
> to spawn a new connection and does so. This can occur if a connection has
> not finished processing all records and another request is sent. A new
> connection has to be spawned to service this request.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.