We have a third-party product which used jTDS to connect from the client PC application (on Windows 7) to an MS SQL Server 2008 R2 database. Most of the users can connect properly, but a few of them get the following error message in the SQL Server log when their logon is refused:
2012-03-30 10:40:25.16 Logon Error: 17836, Severity: 20, State: 16.
2012-03-30 10:40:25.16 Logon Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: ]
The only difference we can find is that the users with the problem have slightly longer AD usernames, but when we get them to run a script connecting to the same database via ADO there are no errors and the logon completes successfully.
Is there some kind of setup or config change we need to make to SQL Server to allow jTDS to connect for these users? Can the length of the username really make a difference? Our usernames are first initial + surname, so the range isn't all that great.
Thanks in advance,
I've never seen such problem before, but in theory it might be possible that longer user names might cause a problem. Could you please specify jTDS connection property "packetSize=8192" and see whether that makes any difference?
Thanks for your reply - it's always nice to know one is unique :-)
It's a third-party application and we really shouldn't mess about with the config file, but what the Hell; we'll have a go and I'll post back what happens.
Log in to post a comment.