I was getting access denied error while updating list items, I already tried to put my code into SPSecurity.RunWithElevatedPrivileges delegate, still I was getting error. Below was my actual code.
CODE:
//code line for updating list columns
Listitem.update()
List.Update()
After doing debugging and removing line by line from actual code I have figured out actual problem – the user who has contributor rights(normal user) was getting access denied error, admin users can able to update list without any problem, it’s because of LIST.UPDATE() statement, because contributor rights users don’t have permission to change anything into List settings, they can add/delete list items but they can’t able to change anything into list, after removing LIST.UPDATE() statement from my actual code, all users were able to successfully update the list items.
Enjoy!
Showing posts with label Access denied. Show all posts
Showing posts with label Access denied. Show all posts
Tuesday, January 26, 2010
Getting access denied error while updating list items
Labels:
Access denied,
access denied in list item,
Getting access denied error while updating list items,
List Settings,
List.Update(),
Listitem.update(),
MOSS 2007,
Personal Experience,
SharePoint,
SharePoint List,
SharePoint Object Model,
SPSecurity.Runwithelevatedprivileges,
SPSecurity.RunWithElevatedPrivileges delegate,
updating list items
Tuesday, October 14, 2008
Access denied error while installing feature
I was getting “Access denied” in command prompt when I tried to execute below command
Stsadm –o installfeature –name “featurename” –force
Solution:
1. Log in user was not added into Central Admin Database security group into SQL Server.
2. Log in user has to be in farm administrator/site collection users group in SharePoint site.
By adding my current Log in users into above two parts, I was able to successfully install feature.
Stsadm –o installfeature –name “featurename” –force
Solution:
1. Log in user was not added into Central Admin Database security group into SQL Server.
2. Log in user has to be in farm administrator/site collection users group in SharePoint site.
By adding my current Log in users into above two parts, I was able to successfully install feature.
Subscribe to:
Posts (Atom)