Error: 17805, Severity: 20, State: 3

1 system transfer from a server (Win2k SP4,SQL2k SP3) to a server (Win2k
SP4,SQL2k SP4), the system can not run and got the error message in log
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
Is this SQL2k SP4 new bug?
Hi
No, I've seen those errors since SQL Server 6.0. If a packet gets messed up
at network level, you end up with SQL Server receiving bad packets.
Setup SQL Server to only listen on TCP/IP and see if your problem goes away
(In EM, Server Properties. Network Configuration, Restart the server)
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"HB" <HB@.discussions.microsoft.com> wrote in message
news:50B3B161-06D7-4311-8D92-A3E13A5592C4@.microsoft.com...
>1 system transfer from a server (Win2k SP4,SQL2k SP3) to a server (Win2k
> SP4,SQL2k SP4), the system can not run and got the error message in log
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Is this SQL2k SP4 new bug?
|||We have this exact issue to, we have got around one issue with inserting or
updating text/image columns by specifying an explicit SQLDbType. But we are
now getting the same issue with other stored procedures. If we amend the sql
client to talk named pipes the the problem goes away, but this is not an
option for us. Any help much appreciated.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> No, I've seen those errors since SQL Server 6.0. If a packet gets messed up
> at network level, you end up with SQL Server receiving bad packets.
> Setup SQL Server to only listen on TCP/IP and see if your problem goes away
> (In EM, Server Properties. Network Configuration, Restart the server)
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "HB" <HB@.discussions.microsoft.com> wrote in message
> news:50B3B161-06D7-4311-8D92-A3E13A5592C4@.microsoft.com...
>
>