Error has happend.(SQLServerProfiler)

  • I made [Stored Procedure] refer to Article of "Automate Profiler Trace with xp_trace_"

    (http://www.sqlservercentral.com/scripts/contributions/446.asp)

    The Script is setted "startup".

    (exec sp_procoption N'<Script Name>', N'startup', N'true')

    Almost all the script is runned normaly, but rarely strange log showed in EventLog.

    The following is a log.

    [41302555] SQLServerProfiler

       Type:     ERROR

       Computer: PJ01DNT1

       Time:     2005/12/26 17:11:14   ID:       998

    E:\MSSQL7\binn\sqlservr.exe Invalid_Pointer ..\..\..\..\src\filters.c 193 

    Invalid_Pointer are showed in

    ..\..\..\..\src\tokentst.c 119 

    ..\..\..\..\src\tokentst.c 161

    ..\..\..\..\src\addtoq.c 746

    ..\..\..\..\src\filters.c 193

    I want reasons.

    And I want take measures to meet the situation.

    The following is my script.

    ------------------------------

    CREATE PROCEDURE MyTraceScript

    AS

    BEGIN

     SET NOCOUNT ON

     

     DECLARE @rc int

     DECLARE @queue_handle int 

     DECLARE @column_value int 

     DECLARE @trace_file varchar(50)

     DECLARE @cmd nvarchar(1000)

     DECLARE @appfilter varchar(255)

     

     SET @trace_file = 'F:\SQL_Trace\profile_' + CONVERT(varchar(8),getdate(),112 ) + '_' + REPLACE(CONVERT(varchar(8),getdate(),108),':','') + '.trc'

     

     SET @cmd = N'del ' + QUOTENAME(@trace_file,'"')

     EXEC master.dbo.xp_cmdshell @cmd

     SET @cmd = N'del ' + QUOTENAME(REPLACE(@trace_file,'.trc','_*.trc'),'"')

     EXEC master.dbo.xp_cmdshell @cmd

     

     SET @column_value = 1|4|16|32|128|256|512|1024|2048|4096|8192|16384|32768|65536|131072|67108864

     EXEC @rc = xp_trace_addnewqueue 1000,

      5,

      95,

      90,

      @column_value,

      @queue_handle OUTPUT

     

     if (@rc != 0) goto error_handler

     

     EXEC xp_trace_seteventclassrequired @queue_handle,

      10, 1 --RPC:Completed

     EXEC xp_trace_seteventclassrequired @queue_handle,

      12, 1 --SQL:BatchCompleted

     EXEC xp_trace_seteventclassrequired @queue_handle,

      14, 1 --Connect

     EXEC xp_trace_seteventclassrequired @queue_handle,

      15, 1 --Disconnect

     EXEC xp_trace_seteventclassrequired @queue_handle,

      20, 1 --LoginFailed

     EXEC xp_trace_seteventclassrequired @queue_handle,

      28, 1 --Insert

     EXEC xp_trace_seteventclassrequired @queue_handle,

      29, 1 --Update

     EXEC xp_trace_seteventclassrequired @queue_handle,

      30, 1 --Delete

     EXEC xp_trace_seteventclassrequired @queue_handle,

      31, 1 --Select

     EXEC xp_trace_seteventclassrequired @queue_handle,

      33, 1 --Exception

     EXEC xp_trace_seteventclassrequired @queue_handle,

      41, 1 --SQL:StmtCompleted

     EXEC xp_trace_seteventclassrequired @queue_handle,

      45, 1 --SP:StmtCompleted

     

     EXEC xp_trace_sethostfilter @queue_handle,

      NULL, --'include_hosts'

      'MyServer1' --'exclude_hosts'

     

     SET @appfilter = 'Microsoft SQL Server;SQL%Profiler%;SQLAgent%;DTS%'

     EXEC xp_trace_setappfilter @queue_handle,

      NULL, --'include_only_applications'

      @appfilter --'exclude_applications'

     

     EXEC xp_trace_setsysobjectsfilter @queue_handle,

      1

     

     EXEC xp_trace_setqueuedestination @queue_handle,

      2,

      1,

      NULL,

      @trace_file

     

     EXEC xp_trace_startconsumer @queue_handle

     

     SELECT @queue_handle

     

     goto finish

     

     error_handler:

     SELECT ErrorCode=@rc

     

     finish:

     

    END

    GO

    SET QUOTED_IDENTIFIER OFF

    GO

    SET ANSI_NULLS ON

    GO

    exec sp_procoption N'MyTraceScript', N'startup', N'true'

    GO

    ------------------------------

    #I am not strong in English.

     

  • I've not seen that error before with Profiler. However, given you're getting a pointer error from several c modules within SQL Server, this is probably something you should call Microsoft Support on. If it's a bug (and it looks to be), they'll typically not charge you for the support call.

    K. Brian Kelley
    @kbriankelley

Viewing 2 posts - 1 through 2 (of 2 total)

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