.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

SQL Native Client Physical connection is not usable

Posted By:      Posted Date: October 27, 2010    Points: 0   Category :Sql Server

MessageWay Application receives this error a few times a month (always in the evenings).

, 08S01, [Microsoft][SQL Native Client]Session Provider: Physical connection is not usable [xFFFFFFFF]. Unable to open message - mid: [201010262102102blios] orig-mid: [201010262102102blios]

Messageway is on a Windows 2003 Vitural server.  The database is on Windows 2003/SQL server 2005 SP3 physical server. 

Each time we receive this error the following groups check for problems and can not find any: Networking, VMWare Administrator, WIndows Administrator, SQL Server Administrator.

Any suggestions?


View Complete Post

More Related Resource Links

SQL Server Native Client Connection String



Currently we are using many config files with SQLNCLI. Is there a way if we would like to use SQLNCLI10 features without changing so many files?



Install SQL Server2005 Error:[Native Client]Encryption not supported on the client

Product: Microsoft SQL Server 2005 -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

Connection problem while connecting from client to server.

Hello, i am trying to connect sql server 2005 express using c#.net 3.5. my connection string is "Server=.\SQLExpress;AttachDbFilename=C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\db_naren.mdf;Database=db_naren; Trusted_Connection=Yes;" this is working fine when i am connecting to sql server from the local machine. When i am trying to connect from someother machine to server it is giving error like A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) i added previliges in add new administrator on SQL Server 2005 Surface Area Configuration . and i made changes on SQL Server 2005 Surface Area Configuration  page, on Database Engine --> Remote Connections -->Local and remote connections --> Using both TCP/IP and named pipelines. still same error i am getting from client machine i am using connection string as "Server=MyServer\SQLExpress;AttachDbFilename=C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\db_naren.mdf;Database=db_nare; Trusted_Connection=Yes;" is there any thing i need to do to connect from client machine to server?please

The SMTP server requires a secure connection or the client was not authenticated.........

i am using asp.net & have a emailing modulewhen i use gmail host i amable 2 send the mail but when i am using yahoo host i get  error msgthe yahoo id & password are right  but still getting the below msg ---------------------------Windows Internet Explorer---------------------------  ' The SMTP server requires a secure connection or the client was not authenticated. Authentication Required. '   ---------------------------OK   ---------------------------

SQL Server allowing access with NATIVE CLIENT Protocols are disabled.

I have disabled all client protocols from SQL Server Configuration Manager -> Sql Native Client configuration -> Client Protocols.Still I am able to access sql server with all client protocols disabled. Why ?Also I stopped the SQL Server Services and restarted it again. Then also the system is allowing me to connect with all the client protocol disabled.

Where is SQL Native Client 10.5.xxxx for Visio 2010

When attempting to use Reverse Engineer tool in Visio 2010 Professional for the Database Model Diagram, selecting SQL Native Client as the data source provider only gives the ODBC SQL Server Native Client as 10.0 (SQL Server 2008). How do I use 10.5.xxxx to connect to a SQL Server 2008 R2 database. Obviously the 10.0.xxxx provider won't understand the newer data types available in 2008 R2.

The SMTP server requires a secure connection or the client was not authenticated. The server respons

  here everything with images     http://img704.imageshack.us/img704/5520/problem1w.png http://img704.imageshack.us/img704/2116/problem2j.png   http://img530.imageshack.us/img530/5445/problem3.png   http://img829.imageshack.us/img829/6345/problem4.png            

SQL Server Native Client is substitute of WDAC (MDAC)?

Forking this subquestion from my question Does SQL Server clients use (WDAC, MDAC) and when? Having read msdn article  SQL Server 2008 R2 Native Client Programming I could not understand: Is SQL Server Native Client (SSNC) intended to be used as advanced substitute for MDAC (currently renamed as WDAC)? what one could have understood from th? article... Except that this article tells: "The SQL Server Native Client ODBC driver is always used in conjunction with the ODBC Driver Manager supplied with Windows DAC" From one side it sounds that SQL Server Native Client (SSNC) provide the same functionalities that MDAC (WDAC) and more being "a stand-alone data access API,". From the other side, it is written that SSNC is dependent on MDAC(WDAC) components (drivers, dll) and vice versa. So, why 2 parallel, having essentially the same functionalities, data access structure duplicates?

The client was unable to reuse a session with SPID 58, which had been reset for connection pooling.

HI I am getting the below error on - Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86)   Apr  2 2010 15:53:02   Copyright (c) Microsoft Corporation  Standard Edition on Windows NT 6.0 <X64> (Build 6002: Service Pack 2) (WOW64)  ----------------------------------------------------------------------------------------------------------------------------------------------------------------- 2010-09-08 14:34:08.81 spid58      Error: 18056, Severity: 20, State: 29. 2010-09-08 14:34:08.81 spid58      The client was unable to reuse a session with SPID 58, which had been reset for connection pooling. The failure ID is 29.  This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. ----------------------------------------------------------------------------------------------------------------------------------------------------------------- I restart the IIS server and SQL server since then until today I haven't face similar error. However, I want to understand the reason for it and how to avoid such errors in future. Thanks

MS Access ADP projects need to be able to use SQL Native Client

Microsoft, PLEASE update the Access ADP platform to be able to connect to SQL Server 2005 using the SQL Native Client.  ADP is a great in-house development platform, but MS seems to have decided to stop supporting it.The problem is, the sql ole db driver that the ADP projects use, cause problems when querying complicated views or stored procedures on SQL Server 2005.  Queries that worked great under SQL Server 2000, time out under 2005.  When run directly on the server, there is no problem.  When they are run from the ADP file, the execution plan of the query is totally messed up.  I watched what SQL Server 2005 does with tracing, it's running certain segments of the query over and over.If I run that same query in Access, through an ADO connection, where I specify the Native Client as the provider, then I don't have that problem, which proves that the problem is the old SQL OLE DB driver. So we need the project's default connection needs to be work properly with SQL Server 2005.

Client Connection Issues

We are seeing a 1,000's of sql connection issues with the same message below from different IP's.  Any ideas on how to solve?   <   Record id="4057" type="RING_BUFFER_CONNECTIVITY" time="221730345"> <   ConnectivityTraceRecord> <   RecordType>LoginTimers</RecordType> <   Spid>0</Spid> <   SniConnectionId>AAA9B8C6-03CB-455F-959E-FBA1B0184B69</SniConnectionId> <   SniConsumerError>17830</SniConsumerError> <   SniProvider>7</SniProvider> <   State>11</State> <   RemoteHost></RemoteHost> <   RemotePort>31280</RemotePort> <   LocalHost></LocalHost> <   LocalPort>1433</LocalPort> <   RecordTime>9/7/2010 9:34:23.93</RecordTime> <   TdsBuffersInformation> <   TdsInputBufferError>10054</TdsInputBufferError> <   TdsOutputBufferError>0</TdsOutputBufferError> <   TdsInputBufferBytes>0</TdsInputBufferBytes> </   TdsBuffersInformation> <   LoginTimers> <   TotalLoginTimeInMilliseconds>5</TotalLoginTimeInMilliseconds> <   LoginTaskEnq

Error with database connection - API client not supported

I keep getting a weired alert on the SQL Server 2005 Box, I would appreciate if some one can assist me in this. However my application is running smoothly, just wondering if any of you have seen such an error 'Alert 1:  Critical Failure in log file for Monitor_DB: Monitor_DB: :__FAILURE__: error with database connection 'HOSTNAME\INSTANCE@master' with error message: API client not supported' I am not sure what API client is trying to connect, I have a BizTalk server which connects to the SQL Server box, and the connections and processing are going on smooth, but still I keep getting this error. Can anyone assist me. Thanks in advance.

User Profile Service Synchronization Connection: Client Timout

Hi, I have scenario on configuring User Profile Synchronization service on customer site as below. Window AD Server 2003 Domain NetBIOS: foo FDQN: foo.bar.com  User Account to connect: foo\ad-connect This account already set permission as describe in http://technet.microsoft.com/en-us/library/ee721049.aspx  when I try to create connection, system took long time to process then return error as "Client Timeout". I try to check FIM and it's seems to work fine (no error return and can get users data). So could anyone told me what's wrong? Since I've didn't have much knowledge on Network and AD, please advice.Theeraphat.P SharePoint Information Worker

SQL Server Native Client install fails during prerequisites

Hi I'm trying to install sharepoint 2010 on a new windows 2k8r2 which is a member server on our domain. The server is fully updated. The SQL Server native client installation fails. This is the entry in the error log;   2010-09-15 08:57:26 - Beginning download of Microsoft SQL Server 2008 Native Client 2010-09-15 08:57:26 - http://go.microsoft.com/fwlink/?LinkID=160387 2010-09-15 08:57:28 - Size of download of "Microsoft SQL Server 2008 Native Client" in bytes is "8073728" 2010-09-15 08:57:28 - Download of "Microsoft SQL Server 2008 Native Client" completed successfully 2010-09-15 08:57:28 - Installing Microsoft SQL Server 2008 Native Client 2010-09-15 08:57:28 - "C:\Windows\system32\msiexec.exe" /i "C:\Users\myadmin\AppData\Local\Temp\SQLCF11.tmp.msi" /quiet /norestart 2010-09-15 08:57:28 - Install process returned (0X660=1632) 2010-09-15 08:57:28 - [In HRESULT format] (0X80070660=-2147023264)   If I run the SQL native client installer manually I get the following error; The installer has encountered an unexpected error. The error code is 2755. Server returned unexpected error 1632 attempting to install package.   Any ideas why this is happening? I've had a quick google and can't see anything for SQL Native Client for that error code. Thanks   Olly

get error The SMTP server requires a secure connection or the client was not authenticated. The serv

 Hi,I was able to send mail with no trouble before few days.Then due to some reason, i Formatted pc &  re-installed visual studio & IIS Now when i try to send mail, i get this error.The SMTP server requires a secure connection or the client was not authenticated.In my web.config file i write<mailSettings>      <smtp from="myemail@gmail.com">        <network host="smtp.gmail.com" port="587" userName="myemail" password="xxxx" defaultCredentials="false"/>      </smtp>    </mailSettings>  </system.net>  And on SEND MAIL Button click event I write ( CODE BEHIND)   Dim smtp As New System.Net.Mail.SmtpClient()  Dim smail As New System.Net.Mail.MailMessage smail.To.Add(New System.Net.Mail.MailAddress("contactperson@yahoo.co.in"))        smail.From = New System.Net.Mail.MailAddress("myemail@gmail.com")        smail.Subject = "HELLOO ..HOW R U?"        smail.IsBodyHtml = "true"        smail.Body = "" & txtmail.Text        s

Should I move ODBC Apps from the SQL Server driviver to SQL Server Native Client 10.0

I have a suite of applications written for SQL Server 2000 in Access 2000 and Access 2007 and running under Access 2007 (12.0.6423,1000 SP2 MSO 12.0.6425.1000) via ODBC with the SQL Server ODBC driver (2000.85.1132.00) under Windows XP Professional (2002 SP3).  I have maintained all the data modules in Access 2000 format so that they can be accessed by SQL Server 2008 if required and am gradully upgrading the data modules to SQL Server.  The server they are connected to is Microsoft SQL Server Standard Edition (10.0.2531.0 running on a 32-bit Wndows Server 2008 Standard (SP2).  As a security improvement I intend to move a number of the applications to the server itself.  My choice of driver for ODBC is between SQL Server (6.00.6002.18005) and SQL Server Native Client 10.0 (2007.100.2531.00).  I have yet to discover any differences in application behavior or performance between the two interfaces My assumption is that I will have have fewer problems if I configure the ODBC links using the SQL Server driver.  However, I was wondering if there is a reason to gradually move them over to the SQL Server Native Client 10.0 driver. Thanks, Harry

How to insert SQL2008 date data type using ADODB.Recordset and Native Client?



I am working with a classic ASP application that we are trying to keep hobbling along while it gets rewritten.  The underlying database has been upgraded many times and is currently running on SQL Server 2008.

Recently a column of table was updated from a smalldatetime (with a check constraint to ensure it didn't have any time values) to simply the date type, but the code now does not work.  I was originally using SQLOLEDB, and was confident that treating the date as a string would be find with our client.  Unfortunately it does not, nor does it work using the SQLNCLI10 client.

This is the stripped down code:

Set adoConnection = aspServer.CreateObject("ADODB.Connection")
adoConnection.Open "Provider=SQLNCLI10"  ' Details Removed
Set adoRS = aspServer.CreateObject("ADODB.Recordset")
adoRS.CursorLocation = adUseClient
adoRS.Open "SELECT * FROM TestTable WHERE id = 0", adoConnection, adOpenKeyset, adLockOptimistic, adCmdText
adoRS("datecolumn") = "09/20/2010"

On the update line, I get the following error:

Microsoft SQL Server Native Client 10.0 error '80040e07'
Error convertin

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend