Ads 720 x 90

Error 17832 : The login packet used to open connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.[Client: xxx.xxx.xxx.xxx ]

One of my client was experiencing this strange error while trying to logon to the sql server using windows authentication, he tried logging in from different machines still got the same error.


"ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing connection was forcibly closed by the remote host ..."

To resolve this problem, increase the MaxTokenSize value of the server computer, to a size large enough to contain the largest token of any user in your organization. To research the correct token size for your organization, consider using the Tokensz application. For more information, see http://go.microsoft.com/fwlink/?LinkId=111047http://go.microsoft.com/fwlink/?LinkId=111047 .


Incorrectly editing the registry can severely damage your system. Before making changes to the registry, we recommend that you back up any valued data on the computer.

To change the MaxTokenSize on the server computer

  1. On the Start menu, click Run.

  2. Type regedit, and then click OK. (If the User Account Control dialog box appears, click Continue.)

  3. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters.

  4. If the MaxTokenSize parameter is not present, right-click Parameters, point to New, and then click DWORD (32-bit) Value. Name the registry entry MaxTokenSize.

  5. Right-click MaxTokenSize, and then click Modify.

  6. In the Value data box type the desired MaxTokenSize value. I put 20,000 Decimal


    Hexadecimal value ffff (decimal value 65535) is the maximum recommended token size. Providing this value would probably solve the problem, but could have negative computer-wide effects with regard to performance. We recommend that you establish the minimum MaxTokenSize value that allows for the largest token of any user in your organization and enter that value.

  7. Click OK.

  8. Close Registry Editor.

  9. Restart the computer.

Related Posts

There is no other posts in this category.

Total Pageviews

Subscribe Our Newsletter