Post reply

SQL Server connectivity Issue

  • July 3, 2013 at 4:16 am

    #275721

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

  • July 9, 2013 at 5:12 am

    #1630735

    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

  • July 9, 2013 at 10:12 pm

    #1631056

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

  • July 9, 2013 at 11:47 pm

    #1631067

    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

  • July 12, 2013 at 2:34 am

    #1631846

    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

  • July 12, 2013 at 6:40 am

    #1631918

    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.

  • July 12, 2013 at 7:24 am

    #1631937

    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

  • July 12, 2013 at 8:14 am

    #1631974

    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[/url] applies to your environment, but read it and let us know if that is the case.



    My blog

  • July 14, 2013 at 8:37 pm

    #1632275

    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.

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply