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...
"
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...