SQL Server Performance Forum – Threads Archive

SQL Log: Invalid login packet(s) sent

Error: 17832, Severity: 18, State: 8
"ods Connection opened but invalid login packet(s) sent. Connection closed." Microsoft KB Link :-
http://support.microsoft.com/kb/q239883/ According to above link :-
SYBASE clients using a CT-Library based on Tabular Data Stream (TDS) 5.0 (including Open Client 10.0.4 and 11.1.1) cannot connect to Microsoft SQL Server 7.0. But i am not using anything like that. Can anyone tell what is this error ? Rajeev Kumar Srivastava
–ALWAYS BE POSITIVE!–

anyway that link says that this has corrected from the sp2 .
did you install it and checked

I am using SQL Server 7.0 with SP3. Rajeev Kumar Srivastava
–ALWAYS BE POSITIVE!–

You should test and apply SP4 which is last and latest SP on SQL ver 7.
ODS errors are common if there is a mismatch with the drive used to connect from other data sources. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Thanks Satya, Can we get which driver is causing this error? Because we don’t use Sybase client as it is said in Microsoft link. Or is their any way to do some workaround to eliminate this error. Rajeev Kumar Srivastava
–ALWAYS BE POSITIVE!–

We had the same issue with a WebLogic JDBC driver. A patch had to be installed for the JDBC driver to get it to work. So check if you use any non standard or old ODBC drivers etc that could have such an issue.

May also search in SYBASE website for relevant compatible driver.
Als ensure to test and apply SP4 to SQL Server. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Argyle, As you said that you had faced same problem, this should had come every time when you use that driver. But here I rarely get this error. Correct me if I am wrong. Satya: I am not using sybase client.
Rajeev Kumar Srivastava
–ALWAYS BE POSITIVE!–

Ok, can you tell us when and where you’re getting this error. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

In SQL Error Log this error is coming and source is "ods". And no fix time is there. Rajeev Kumar Srivastava
–ALWAYS BE POSITIVE!–

Then you need more granular monitoring of server about the occurence of these errors.
Can you explain what sort of jobs and applications connections against the database server, any issues reported with them. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

It doesn’t have to happen all the time. It could happen only when there is a client machine with old drivers that connect.

]]>