Re: Receive Error: 17805 Invalid buffer received from client
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Wed, 26 Oct 2005 13:38:34 -0600
You should be able to track it down quickly if it's
happening every hour. You get capture exceptions using the
Errors and Warnings class. You can then see the spid that
generated this error. If you also capture the T-SQL
statements and stored procedures at the same time, you will
see what the spid that generated the exception was
executing.
What you filter on depends more on your system. You can at
least filter out the applications SQL Profiler and SQLAgent%
-Sue
On Fri, 21 Oct 2005 15:33:20 -0700, "Brett Davis"
<bdavis123@xxxxxxx> wrote:
>Hello
>
>I am running SQL Server 2000 with SP 4 on Windows Server 2003. Every hour I
>receive several notifications with the following:
>
> Reply: Message not found. Insertion strings:Error: 17805, Severity: 20,
> State: 3 Invalid buffer received from client.
>
>I want to create a SQL Profiler trace that will help me to identify which
>sql statements \ stored procedures are causing this error. What will i need
>to specify in the trace to identify the transaction that is causing this
>error and what kind of filter if any do i need to apply?
>
>Please advise..
>
>Cheers!
>
>Brett
>
.
- References:
- Receive Error: 17805 Invalid buffer received from client
- From: Brett Davis
- Receive Error: 17805 Invalid buffer received from client
- Prev by Date: Re: select problem
- Next by Date: Re: sp_addlogin from vb.net security
- Previous by thread: Receive Error: 17805 Invalid buffer received from client
- Next by thread: sp_addlogin from vb.net security
- Index(es):
Relevant Pages
|
