Error: 17832, Severity: 20, State: 7 Connection opened but invalid login packet(s) sent

Question

Post reply

Error: 17832, Severity: 20, State: 7 Connection opened but invalid login packet(s) sent

Helen-84411

Hall of Fame

Points: 3320
More actions
January 3, 2006 at 8:20 am

#103011

Hi all,
In one of my server I get this error.
Error: 17832, Severity: 20, State: 7 Connection opened but invalid login packet(s) sent. Connection closed
Please help. Any pointers

Helen
--------------------------------
Are you a born again. He is Jehova Jirah unto me
January 6, 2006 at 8:00 am

This was removed by the editor as SPAM

Viewing 11 posts - 1 through 10 (of 10 total)

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

Yelena Varshal SSC-Dedicated Points: 34286 More actions · Answer 1

Did it happen only once or it happens often?

Regards,Yelena Varsha

Ann Fassbender SSC Enthusiast Points: 170 More actions · Answer 2

I am having this same error. Did you find a resolution?

Ann Fassbender SSC Enthusiast Points: 170 More actions · Answer 3

We found the resolution to our problem. We turned off "Force Protocol Encryption" in the SQL Server Network Utility.

Helen-84411 Hall of Fame Points: 3320 More actions · Answer 4

Hi Ann,

thanks a ton

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

vallabhai Ramisetty SSC Enthusiast Points: 157 More actions · Answer 5

"Force Protocol Encryption" was always unchecked on my server but I still get this error.

rsvpte Valued Member Points: 73 More actions · Answer 6

I see same error despite "Force Protocol Encryption" being unchecked??

Could there be any other reason for this error?

RSVP

free_mascot One Orange Chip Points: 27168 More actions · Answer 7

Troubleshoot with the following MS link:

http://support.microsoft.com/kb/827422

Hope this will help

---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."

HBhagat Hall of Fame Points: 3331 More actions · Answer 8

Hi,

even I was also getiting the same messages. Later on our tech team replied to the mail as they had installed some kind of monitoring check they had configured in the server. So every few mins the messages were coming. They have removed it and the messages stopped comming.

Now we are not getting any messages.

I hope this can also be helpful...

Thanks,

Harsha

BLADE-1043594 SSCrazy Points: 2576 More actions · Answer 9

This error occurs if a client starts to connect but never successfully completes the attempt because of a client operating system, application, or network failure. Wide area networks (WANs) are more susceptible than local area networks (LANs) to this type of problem, because such networks often have many routers and other network devices that can delay data packet delivery and/or cause other difficulties in the delivery of data packets due to improper packet fragmentation or misrouting.

However, the very occurrence of these errors in the errorlog or event log does not necessarily indicate any real problems with your SQL Server connectivity. Even in normal operations, this error may still occur at times, due to the unreliable nature of networks, especially wide area networks. In addition, improper use of applications (such as restarting the computer in the middle of a login process) can also cause this error to occur.

To determine whether or not you are facing a real problem, you may want to check the following:

1. Check with the end users to see whether they have experienced any difficulties in making connections to SQL Server. If nobody reports any connectivity problems, you can usually ignore these errors.

2. Check the frequency of this error in the errorlog. If it occurs very frequently, it indicates some potential problems, even if no one is complaining about any connectivity problems.

for more details visit http://support.microsoft.com/kb/169521

[font="Comic Sans MS"]+++BLADE+++[/font]:cool: