Our Client wanted to migrate its sharepoint plateform 2007 to SharePoint 2010. He encontred an issue when activating a feature wich creates a custom timer Job.
When i debugged the code, i found an access denied exception when the job.Delete() method is executed, wich was ubnormal because the activation using stsadm runs correctly.
After googling i found an interessant post Paul Kotlyar . He told that SharePoint added a security feature in the Classes inheriting from SPPersistedObject of the namespace Microsoft.SharePoint.Administration.
This feature dissallows modification of the above stated objects from content web applications.
To solve this issue, the SharePoint API property Microsoft.SharePoint.Administration.SPWebService.ContentService.RemoteAdministratorAccessDenied has to be set to false.
The file joined is the script that i used from to fix this issue without changing any thing in the feature code.
Don't forgot to unlock the ps1 file ;)
SetRemoteAdministratorAccessDenied-False
When i debugged the code, i found an access denied exception when the job.Delete() method is executed, wich was ubnormal because the activation using stsadm runs correctly.
After googling i found an interessant post Paul Kotlyar . He told that SharePoint added a security feature in the Classes inheriting from SPPersistedObject of the namespace Microsoft.SharePoint.Administration.
This feature dissallows modification of the above stated objects from content web applications.
To solve this issue, the SharePoint API property Microsoft.SharePoint.Administration.SPWebService.ContentService.RemoteAdministratorAccessDenied has to be set to false.
The file joined is the script that i used from to fix this issue without changing any thing in the feature code.
Don't forgot to unlock the ps1 file ;)
SetRemoteAdministratorAccessDenied-False
Comments
Post a Comment