Re: Invalid Buffer 17805
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Tue, 08 Nov 2005 20:54:39 -0700
Try using something like:
Exceptions from the Errors and Warnings event class.
SQL:StmtStarting from the T-SQL event classes
SP:Starting and SP:StmtStarting from the Stored Procedures
event classes.
Filters depend on your system. Leave the application not
like SQL Profiler filter in there and additionally add at
least SQLAgent% in the same not like application filter.
-Sue
On 8 Nov 2005 06:28:15 -0800, "salvoWJ"
<salvatore.toro@xxxxxxxxxxxxxx> wrote:
>Hello
>
>I am running SQL Server 2000 with SP 4 on Windows Server 2003
>Enterprice Edisction.
>I receive several notifications with the following:
>
>Error: Message not found. Insertion strings:Error: 17805, Severity: 20,
> 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?
>
>I catch the error with SQLagent Alerts, but I want to known what
>statement or SP lanch the error.
>
>
>Help me please
>
>Salvo
.
- References:
- Invalid Buffer 17805
- From: salvoWJ
- Invalid Buffer 17805
- Prev by Date: Re: SQL Server Management Studio is one of the worst UIs I have dealt
- Next by Date: Re: SQL Server Management Studio is one of the worst UIs I have de
- Previous by thread: Invalid Buffer 17805
- Next by thread: Access 2003 Front End for SQL 2005
- Index(es):
Relevant Pages
|
Loading