Re: Hotfix 815495 -> Invalid buffer received from client

From: Kevin (ReplyTo_at_Newsgroups.only)
Date: 07/30/03 

Date: Wed, 30 Jul 2003 07:34:49 -0700

I don't have any technical advice to offer on your problem, but I think it's
important to mention that if unavailability or errors cause major business
impact, then CHANGES should be MANAGED. That means not only testing, but
developing (and testing) a rollback. There really has never been a SQL
service pack or hotfix that was easy to roll-back.

SOP is re-install SQL, re-install service packs and hotfixes to the previous
point, and restore system databases. This technique, while overkill in
somecases, will always work.

----------------------------------------------------
The views expressed here are my own
and not of my employer.
----------------------------------------------------
"Sami" <sami_nygard@hotmail.com> wrote in message
news:477b01c3566a$cc629240$a001280a@phx.gbl...
> Hi,
>
> We ran the hotfix 815495 MS03-031 and after that our MSSQL
> 2000 started to report the event 17052 Invalid buffer
> received from client. In the .Net application, that was
> reporting this, we reduced the single packet size of the
> DB transactions to 3072b Unicode from 4096b after which
> everything was running smoothly again and the application
> didn't crash anymore.
>
> Any idea what could be causing this as the network packet
> size configuration on the SQL server has remained the same
> throughout this all?
>
>
> Sami
>
> p.s. If Microsoft people are reading this then you should
> consider including a form of an automated deinstall/
> rollback of the hotfixes you provide as they might in
> these sort of cases have a major impact on the business.