When you run your code with Elevated Privileges, the code runs under the identity of the hosting application pool. SharePoint\System account exists ONLY within content of SharePoint runtime(not recognised by Windows Security subsystem) and map internally to the account under which application pool is running.
If you are running application pool under DOMAIN\SSUSER account, the code is still audited as running under SharePoint\System account. So, if you get access error on SharePoint site stating that SharePoint\System account don’t have access to the resource, this is because the application pool identity account don’t have access to the resource. Don’t spend time looking for SharePoint\System account :-)
2 comments:
Absolutely with you it agree. In it something is also to me it seems it is excellent idea. I agree with you.
Can you assist this guy? His document is checked out by SHAREPOINT\SYSTEM account.
http://social.technet.microsoft.com/Forums/en-US/sharepoint2010general/thread/0c0d1296-2a0e-451a-a80d-dc224762a738
Post a Comment