RE: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()

Hi Charles,
I think I got it. I went to configuration tool-->surface area configuration-->
Database Engine -->remote connection -->on the right-hand side local and
remote connection. should I just check named pipes only or both TCP/IP and
named pipes

thanks
--
Betty


"Charles Wang[MSFT]" wrote:

Hi Betty,
I understand that you encountered the ODBC error message on your ecommerce
site intermittently. The error always occurred at the line
conn.Execute(sQry) from different programs.
If I have misunderstood, please let me know.

From my research, this issue may happen if you are using TCP/IP protocol to
connect to your SQL Server instance and if there are intermittent network
disconnections in your LAN. When you have established the connection with
TCP/IP protocol to your SQL Server instance by calling conn.Open, something
happens and causes a momentary loss of connectivity to your SQL Server
instance (You can use SQL Profiler on your SQL Server side to monitor your
SQL Server instance and see if there is a connection reset when this issue
happens), then the call conn.Execute would fail. You may try configuring
your ODBC source using Named Pipes protocol for your client connections. On
your Web server, open Administrative Tools from Control Panel, double click
Data Sources (ODBC), select your DSN and click Configure..., click Next,
click Client Configuration..., check Named Pipes and then click OK. Please
also ensure that Named Pipes protocol is enabled at your SQL Server side.

Regarding ODBC Connection Pooling, you may use Performance Monitor to
monitor it on your Web server side. You may refer to this KB article:
How to Enable ODBC Connection Pooling Performance Counters
http://support.microsoft.com/kb/216950/EN-US/

Also if this issue persists, I recommend that you try using ADO to connect
to your SQL Server to see if it helps. For example:
<%@LANGUAGE=VBSCRIPT%>
<%
Option Explicit
Dim strConnection, conn, rs, strSQL

strConnection = "Provider=sqloledb;Data Source=SQLServerName;" & _
"Initial Catalog=DBaseName;User Id=sa;Password=password;"

Set conn = Server.CreateObject("ADODB.Connection")
conn.Open strConnection

Set rs = Server.CreateObject("ADODB.recordset")
strSQL = "SELECT * FROM myTable"
rs.open strSQL, conn, 3,3

rs.MoveFirst
WHILE NOT rs.EOF
Response.Write(rs("myField") & "<br/>")
rs.MoveNext
WEND

rs.Close
Set rs = Nothing

conn.Close
Set conn = Nothing
%>

Hope this helps. If you have any other questions or concerns, please feel
free to let me know. Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================



.

Relevant Pages

  • Re: Strange Problems with ODBC connection to SQL Server
    ... When accessing Jet data, use DAO. ... This way you are not exposing connection information in clear ... >accesses an SQL Server 2000 repository via ODBC data source. ...
    (microsoft.public.data.odbc)
  • RE: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()
    ... the ODBC source using named pipe, but I don't know how to enable named pipes ... If it is not working I am going to use ado to connect to sql server. ... Microsoft Online Community Support ...
    (microsoft.public.sqlserver.connect)
  • Re: Access and processor usage
    ... and you are using an ODBC connection, that would be your bottle neck. ... bottleneck - need to step up to Sql Server. ...
    (comp.databases.ms-access)
  • RE: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()) er
    ... I understand that you encountered the ODBC error message on your ecommerce ... TCP/IP protocol to your SQL Server instance by calling conn.Open, ... SQL Server instance and see if there is a connection reset when this issue ... Microsoft Online Community Support ...
    (microsoft.public.sqlserver.connect)
  • Re: Performance of ODBC
    ... ODBC / MDB is a waste of time. ... Usiing Access front-end to connection a back end through ... the database via ODBC with the Jet database engine. ... that Access is the front end, and the SQL server is the back end. ...
    (microsoft.public.access.adp.sqlserver)