Login packets and 17832 error

• Helen-84411

  Hall of Fame

  Points: 3320

  More actions

  January 27, 2006 at 11:29 pm

  #111733

  Hi,

  I get this error at regular intervels in SQL error log namely (04:30, 12:38)

  Error: 17832, Severity: 20, State: 7

  Connection opened but invalid login packet(s) sent.  Connection closed..

  The frequency of this error..

  2006-01-11 04:30:10.17

  2006-01-11 08:28:41.45

  2006-01-11 12:21:51.84

  2006-01-12 05:54:27.07

  2006-01-12 08:30:22.12

  2006-01-12 14:54:01.21

  2006-01-13 04:29:49.65

  2006-01-13 08:29:01.59

  2006-01-13 14:37:41.18

  2006-01-14 04:18:45.18

  2006-01-14 08:15:55.98

  2006-01-15 04:39:50.85

  2006-01-15 12:38:23.35

  2006-01-16 04:40:28.54

  2006-01-17 04:49:25.92

  2006-01-17 12:59:01.84

  2006-01-18 04:39:25.16

  2006-01-18 12:09:53.85

  2006-01-19 06:10:03.34

  2006-01-20 04:34:40.57

  2006-01-20 12:46:21.33

  2006-01-21 04:34:03.22

  2006-01-21 12:34:13.50

  2006-01-22 04:31:51.35

  2006-01-22 12:34:24.35

  2006-01-23 04:31:24.04

  2006-01-23 12:37:50.86

  2006-01-24 04:34:11.51

  2006-01-24 12:40:26.29

  2006-01-25 04:31:17.38

  2006-01-26 06:08:50.09

  2006-01-27 04:31:33.35

  2006-01-27 12:38:33.78

  Followed by series of errors like

  2006-01-27 10:15:04.23 logon     Login failed for user 'AAA\DCD$'.

  2006-01-27 02:17:47.44 logon     Login failed for user 'NT AUTHORITY\SYSTEM'.

  2006-01-25 23:07:48.03 logon     Login failed for user 'abc'.

  2006-01-25 22:57:25.32 logon     Login failed for user 'hdfd'.

  2006-01-11 01:26:15.74 logon     Login failed for user 'sa'.

  Where as our normal backup jobs and database consistency check jobs continue to run normally. Users complain that they are not able to login and they receive an error message like this

     "Unable to Update SVB. It is currently locked by ''".

  Any suggestion how I should go about trouble shooting like

  1. Check if in client side  anti-virus software is configured to scans all files, named pipes (which are considered files) may be affected adversely. In this case, named pipes may be opened in invalid mode, causing these errors on the server side???

  2. Checking ODBC driver version on client side??

  3. Watchout for network speed??

  4. DB Library error on client side

  5. Will a network tracing to findout as to who is connecting around that time help??

  The worrying factor is SQL users are getting locked up

  Thanks for your help

   

   

  
  Helen
  --------------------------------
  Are you a born again. He is Jehova Jirah unto me