Post reply

EXECUTE permission denied on object 'sp_fulltext_getdata'

  • October 12, 2007 at 7:18 am

    #180145

    I enabled auditing of "permission denied" messages on a server. I am not seeing "EXECUTE permission denied on object 'sp_fulltext_getdata'" whenever the following statements are run.

    Exec sp_fulltext_table N'[dbo].[TableName]', N'start_incremental'

    Exec sp_fulltext_catalog N'FullTextCatalogName', N'start_incremental'

    When I execute the statement as a scheduled job or through query analyzer neither returns an error. However if I enable profiler I receive the error below.

    2007-10-12 08:12:17.87 spid75 Error: 229, Severity: 14, State: 5

    2007-10-12 08:12:17.87 spid75 EXECUTE permission denied on object 'sp_fulltext_getdata', database 'master', owner 'dbo'..

    Why is this occurring?

    Thanks, Dave

  • October 12, 2007 at 7:40 am

    #741552

    Hi Dave,

    How did you enable the auditing?

    -- Erik http://blog.rollback.hu

  • October 12, 2007 at 8:40 am

    #741588

    This command tells SQL Server to log error 229

    sp_altermessage 229, 'WITH_LOG', 'true'

    GO

    The script below creates the alert. I have the alert start a job that essentially captures the results of sp_who2 so I can see more details then what is written to the SQL Server error log

    Use MSDB

    GO

    IF (EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'Permission Denied'))

    ---- Delete the alert with the same name.

    EXECUTE msdb.dbo.sp_delete_alert @name = N'Permission Denied'

    BEGIN

    EXECUTE msdb.dbo.sp_add_alert @name = N'Permission Denied', @message_id = 229, @severity = 0, @enabled = 1, @delay_between_responses = 60, @include_event_description_in = 1, @job_name = N'Monitor User Activity', @category_name = N'[Uncategorized]'

    EXECUTE msdb.dbo.sp_add_notification @alert_name = N'Permission Denied', @operator_name = N'DBAs', @notification_method = 1

    END

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

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