Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server connectivity Issue


SQL Server connectivity Issue

Author
Message
dm_tapas
dm_tapas
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1026 Visits: 423
I am able to connect the server but not to the SSMS. getting the below error:

"
The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server; the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054)"

To fix it :
I have done some changes in system registry..

from the path... \System\CurrentControlSet\Control\Lsa\Kerberos\Parameters
-- Added the following registry value:
Name: MaxTokenSize
Data type: REG_DWORD
Radix: Decimal
Value: 48000
--Rebooted server

and it resolves the issue for me..

BUT it is happening weekly basis..
and every time server restart resolves the issue.

CAN ANYBODY HELP TO FIX THE ISSUE PERMANENTLY..


Details :
SQL Server 2005 -- SP4 -- Standard Edition (64-bit)
MS Windows Server 2003 R2 -- SP2-- Standard x64 Edition
RAM: 16 GB

Thanks in advance...
Ignacio A. Salom Rangel
Ignacio A. Salom Rangel
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3114 Visits: 1439
How were you trying to connect to the Server when using SSMS? Did you use the full Servername + instance (If applicable)? Did you try using the portnumber to connect? Please provide more details.




My blog

dm_tapas
dm_tapas
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1026 Visits: 423
Thank you for the reply.

Yes I am trying to connect using SSMS and with the full server name. some times it won't allow us to connect.
But after the reboot of the server , it is working fine for us. it has not been happened since 10 days. But I faced 3/4 times on last month.

Do you have any idea , what may be the cause of this issue. ??
durai nagarajan
durai nagarajan
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1107 Visits: 2771
Try these
1. using the sql server port number
2. using the sql server ip address , if this resolves the issue the server might have improper name change , i have face it once.

Regards
Durai Nagarajan
Database admin(DBA)
Database admin(DBA)
SSC Veteran
SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)

Group: General Forum Members
Points: 218 Visits: 1309
hello,

Can you switch to TCP/Ip(i.e.,ENable or disable)??? check named pipes enabled for your SQL Server??
and How many active connections are there when this occurs?
I'm sure there isn't a limit on the number of concurrent connections.

Thanks&Regards,
DBA

SQL server DBA
dm_tapas
dm_tapas
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1026 Visits: 423
Thanks for the reply.

Yesterday it happened... SQL was not allowed any new connections..but it was showing 99 % CPU usage by SQL.
we restarted the server ... and server is back. I found the error "LazyWriter: warning<c/> no free buffers found"
I think the Memory is not sufficient for the Environment or else we need to lock the memory by assigning the Lock pages in memory user right to the user account that is used as the startup account of the SQL Server service.I will try if it happened next time.. or we will increase the RAM

Thanks.
Database admin(DBA)
Database admin(DBA)
SSC Veteran
SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)

Group: General Forum Members
Points: 218 Visits: 1309
hello,

I think you need to check ,How much memory does server have? How did you config memory in sql?

and due to issues with memory configuration. Two quick things to check:

1. SQL Server 'max server memory' is set to an optimal value

2. SQL Server service account has "Lock pages in Memory" rights

Thanks&Regards
DBA

SQL server DBA
Ignacio A. Salom Rangel
Ignacio A. Salom Rangel
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3114 Visits: 1439
dm_tapas (7/12/2013)
Thanks for the reply.

Yesterday it happened... SQL was not allowed any new connections..but it was showing 99 % CPU usage by SQL.
we restarted the server ... and server is back. I found the error "LazyWriter: warning<c/> no free buffers found"
I think the Memory is not sufficient for the Environment or else we need to lock the memory by assigning the Lock pages in memory user right to the user account that is used as the startup account of the SQL Server service.I will try if it happened next time.. or we will increase the RAM

Thanks.
I'm not 100% sure that this applies to your environment, but read it and let us know if that is the case.




My blog

dm_tapas
dm_tapas
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1026 Visits: 423
yes.

There is no limit for Max server Memory,. Lock page is not yet configured... If next time it happens , I will do it..

Thank you.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search