Search account got - Insufficient sql database permissions for user. EXECUTE permission was denied on the object proc_Gettimerrunningjobs RRS feed

  • Question

  • Dear all,

    I am troubleshooting a critical error showed up on Event log.  It said:

    Insufficient sql database permissions for user 'Name:domain\wss_search ....... EXECUTE permission was denied on the object 'proc_GetTimerRunningJobs', database 'SharePoint_Config', schema 'dbo'

    domain\wss_search is the default content access account. According to http://technet.microsoft.com/en-us/library/cc678863.aspx I should not grant it the Farm Administrators permission.

    In the Search Center I am able to search out documents as expected so I think the search service is fine.   However I have no clue why this account is trying to access 'proc_GetTimerRunningJobs'.


    Thursday, February 6, 2014 9:13 AM


All replies

  • Hi Mark,

    This issue was caused by the search account’s permission. For resolving your issue, please do as the followings:

    1. Expand your SharePoint Configuration database 'SharePoint_Config' and navigate to ‘proc_GetTimerRunningJobs’ under Programmability ->Stored Procedures
    2. Right-click proc_GetTimerRunningJobs and choose Properties
    3. Click on Permission on the left launch
    4. Select the Search button and browse for ‘WSS_Content_Application_Pools’
    5. Provide ‘Execute’ permissions for ‘WSS_Content_Application_Pools’
    6. Click OK

    Here are some similar posts for you to take a look at:



    I hope this helps.



    Wendy Li
    TechNet Community Support

    Monday, February 10, 2014 6:40 AM
  • A simpler and supported configuration to fix this issue would be to grant the SPDataAccess database role to the SharePoint search service account in question.

    Steps below.

    SQL Server Management Studio > Security > Logins > Properties for the service account > User Mappings > User Mapping > select the Sharepoint_config database > select SPDataAccess check box click OK.

    Although altering the properties of the stored procedure will make this error go away it is not the root problem. The root problem is simply the missing database role membership.

    • Edited by DonMcB Thursday, April 21, 2016 3:52 AM
    Thursday, April 21, 2016 3:47 AM
  • Hi DonMcB, 

    Is there any official document telling Search account should have SPDataAccess  DB role?

    Friday, May 13, 2016 3:08 AM
  • I ´ve been having an error like this for a week!!! Your fix was the solution, thank you!


    Thursday, July 30, 2020 8:20 PM