kamagra how much to take

Access To The Requested Resource(s) Is Denied – SharePoint 2013 – Map AD Attribute To Profile

I ran into this error today, which turned out to be an account problem in this particular instance. The error appears to occur when you are mapping an AD attribute to a profile property. The exact error text is:

Microsoft.ResourceManagement.Service: System.ServiceModel.FaultException: Access to the requested resource(s) is denied
at Microsoft.ResourceManagement.WebServices.ResourceManagementService.
GetCurrentUserFromSecurityIdentifier()
at Microsoft.ResourceManagement.WebServices.ResourceManagementService.GetCurrentUser()
at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Enumerate(Message request)

This can apparantly occur even if you are in a 2010 migration scenario whereby you are borrowing accounts that should technically have AD rights for this type of operation.

This error can also appear when you are deleting or managing a pre-exisiting attribute. Meaning, you may not run into the above error and you can successfully add a new mapping. However when try to delete or modify an exsiting attribute, you encounter the following:

LoadConnections failed trying to fill the connections list. Most likely during RetriveResources because of permissions — Microsoft.ResourceManagement.WebServices.Client.PermissionDeniedException: Access to the requested resource(s) is denied
at Microsoft.ResourceManagement.WebServices.Client.ResourceTemplate.EnumerateResources(SearchParameters parameters)
at Microsoft.ResourceManagement.WebServices.ResourceManager.RetrieveResources()
at Microsoft.Office.Server.UserProfiles.ConnectionManager.LoadConnections()
MgrProperty.DeleteProperty(): Microsoft.ResourceManagement.WebServices.Client.PermissionDeniedException: Access to the requested resource(s) is denied
at Microsoft.ResourceManagement.WebServices.Client.ResourceTemplate.EnumerateResources(SearchParameters parameters)
at Microsoft.ResourceManagement.WebServices.ResourceManager.RetrieveResources()
at Microsoft.Office.Server.UserProfiles.ConnectionManager.LoadConnections()
at Microsoft.Office.Server.UserProfiles.ConnectionManager.Initialize(UserProfileApplicationProxy userProfileApplicationProxy, Guid partitionID)
at Microsoft.Office.Server.UserProfiles.ConnectionManager..ctor(UserProfileApplicationProxy userProfileApplicationProxy, Guid partitionID)
at Microsoft.Office.Server.UserProfiles.PropertyBaseManager`1.get_ConnectionManager()
at Microsoft.Office.Server.UserProfiles.PropertyBaseManager`1.Remove(T property)
at Microsoft.Office.Server.UserProfiles.ProfileSubtypePropertyManager.Remove(String propertyURI, String propertyName, String sectionName)
at Microsoft.Office.Server.UserProfiles.PropertyBaseManager`1.RemovePropertyByName(String propertyName)
at Microsoft.Office.Server.UserProfiles.PropertyBaseManager`1.RemoveByName(String name, Boolean isSection)
at Microsoft.SharePoint.Portal.UserProfiles.AdminUI.MgrProperty.DeleteProperty(String strName, Boolean fIsSection).

As you can see in the text in the above, we can derive that these are permission based issues. Access to the requested resource(s) is denied appears within both of the reported errors. In order to implement the repair, simply add the correct account for user profiles which has elevated access to the user profile database and it should work fine!

 

Share

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>