How to capture permission denied errors

  • AlphaTangoWhiskey


    Points: 10797

    we are implementing SP 2019 and getting an error regarding permission denied on VIEW SERVER STATE.

    The error doesn't have an account name, is there a way to via a trace flag or more verbose logging level that would force these permission denied events to show in the log? This is just a test server.

    I'm not the SP guy, just trying to track down what account is getting this error.


  • Chris Harshman


    Points: 42080

    Since the 2 errors involved, 297, 300 are just normal severity errors (16 and 14 respectively) they will not be put in the error log.  Since this is just a test server, you might be able to capture the events with an extended event session or a trace in Profiler.

  • MarkusB


    Points: 37369

    Another option would be using an database audit specification using the SCHEMA_OBJECT_ACCESS_GROUP

    [font="Verdana"]Markus Bohse[/font]

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

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