Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, March 12, 2015 5:50 PM
Hi,
We are using SP 2013 Standard SP1, just happened to get this error messages frequently in the Event Viewer, any insight on the same would be appreciated
Insufficient SQL database permissions for user 'Name: NT AUTHORITY\IUSR SID: S-1-5-17 ImpersonationLevel: Impersonation' in database 'WSS_Content' on SQL Server instance 'SQLServer\SPS2013'. Additional error information from SQL Server is included below. The UPDATE permission was denied on the object 'AllListsAux', database 'WSS_Content', schema 'dbo'.
All replies (8)
Friday, December 18, 2015 5:09 PM ✅Answered
This was something I finally got an answer too...
CAUSE: SQL access denied error occurs when stored procedure proc_OrphanRecurringEventExceptions updates AllListsAux.Modified column for the current SPList, at the end of the stored procedure. Despite the SQL access denied error, column AllListsAux.Modified is actually successfully updated, so there is no impact except the critical error generated in event viewer
RESOLUTION: This issue has been fixed and is scheduled to be released in the SharePoint 2013 November 2015 CU.
Friday, March 13, 2015 11:29 AM | 1 vote
Hi,
From your description, my understanding is that you get error message about UPDATE permission from Event Viewer.
It looks like the user doesn’t have the necessary permission on the database, you could check if the account is assigned the proper Server Role, and then grant permission for the user.
More information from below articles should help.
How to grant correct permission to the database access account:
https://technet.microsoft.com/en-us/library/ee513067(v=office.14).aspx
Here are some solutions about Execute permission and Select permission, you also could refer to them:
http://www.spstech.net/moss2007/event-5214-execute-permission-was-denied-on-object/
Best Regards,
Vincent Han
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Sunday, March 15, 2015 7:07 PM
Thanks for the links, the user does have the necessary permissions in SharePoint
Tuesday, March 17, 2015 5:54 AM
Hi,
As SharePoint need to connect to SQL Server database, user should have necessary permission on database, please check if the user has the correct permission on database, and grant correct permission for this user as my last replay.
Best Regards,
Vincent Han
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Tuesday, March 17, 2015 11:09 AM
The user does not directly connect to the database, it goes through the Service Accounts, in my 6+ years of experience with SharePoint from WSS 3.0 to 2013 I have never needed to grant a user permission on the SharePoint Database explicitly.
Tuesday, March 17, 2015 1:42 PM
Do you know what operation this error message is connected to? It smells like a timer job if it's happening at regular intervals, have you checked for any failing?
Do you know why the user ID is coming through as a SSID?
Wednesday, March 18, 2015 7:22 PM
Hope this helps, from the ULS and Event Viewer
Insufficient SQL database permissions for user 'Name: NT AUTHORITY\IUSR SID: S-1-5-17 ImpersonationLevel: Impersonation' in database 'WSS_Content' on SQL Server instance 'SQLServer\SPS2013'. Additional error information from SQL Server is included below. The UPDATE permission was denied on the object 'AllListsAux', database 'WSS_Content', schema 'dbo'.
Wednesday, March 18, 2015 10:29 PM
Not in the slightest, you already said that.
When does it fail?
Are there any failed timer jobs?
What other activities does that correlation ID match up to?
Edit: To explain why it's no use to us: We'd need to know every single process that might update the AllListsAux object in a content database. I'll assume you've already searched for that message so you're pretty much relying on someone wandering past having seen this unusual (since it's not bloged about) message and knowing the fix. That's possible but deeply unlikely. If you can find out some more information about which user is encountering the issue, or what process is related to it then we might be able to guide you to find a solution. As it is there's nothing more that can be done without more details.