April 27, 2009 at 7:29 pm
THE SQL server LOGIN error message:
===================================
cannt connect to server server_name。
===================================
connect to the server succssfull，but error occured during the login period。 (provider: the shared memory program, error: 0 - there is no thread on the other side of the pipeline。) (.Net SqlClient Data Provider)
------------------------------
about help ,please click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
------------------------------
server name: server_name
error number: 233
seriousness : 20
state: 0
------------------------------
location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
when i restart the SQLserver service,everyting will ok,but after some days ,will happen again,
eager to know how to do !
thanks for your advice!
April 27, 2009 at 9:10 pm
Hello,
May be take a look at the following article, especially to see if one of the comments relates to your particular scenario:-
http://blogs.msdn.com/sql_protocols/archive/2006/07/26/678596.aspx
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
April 28, 2009 at 3:16 am
Are you still facing the problem?
Whats the service pack you are using?
April 28, 2009 at 6:19 am
my sp is sp3.thank you.
April 29, 2009 at 9:07 pm
Are you by any chance using AD?
I think I have encountered this error a long tome ago. If I remember correctly we had an AD group whose users where granted right on the SQL box. During Logon / Authentication if the AD was unavailable or took time to respond we had this error. We got around it by setting SQL server to authenticate using SQL and Windows. Then creating SQL users with specific rights. And using only these SQL users in our web.config connection strings. Interactive users still continued under Windows Authentication.
May 3, 2009 at 8:33 pm
Now ,i think ,it is the program of client caused this problem :because ,I have 3 DBserver with the same configuration ,
only one will occur which client program is different from the others,and when this happen,the DBserver can't reach any
machine with telnet ,the port 1433 or 80 will both report error message(connt open the connection,at port ...),when restart the DB server ,the error will disappear.
May 4, 2009 at 2:50 am
please check is there any application configured with same port?
stop all applications and services.
start sql server.
this will permit sql server to take control over port 1433.
Manoj
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply