0
Answered

"Attempted to perform an unauthorized operation" Error on Export

Matthew Woolnough 2 years ago in UNIFYBroker/Microsoft SharePoint • updated by anonymous 1 year ago 8

Permissions like error upon export to Sharepoint.  I have reviewed the Pre-reqs and it appears as though the service account has the appropriate rights (screenshots below).

Are there additional rights required?

Matthew


System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Attempted to perform an unauthorized operation. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.
   at Microsoft.Office.Server.UserProfiles.OrganizationProfileValueCollection.CheckUpdatePermissions()
   at Microsoft.Office.Server.UserProfiles.ProfileValueCollectionBase.set_Value(Object value)
   at Microsoft.Office.Server.UserProfiles.OrganizationProfile.set_DisplayName(String value)
   at Unify.Connectors.SharePoint.SharePoint2010WCFService.UNIFYIdentityBrokerService.SharePoint2010OrganizationProfileService.PopulateProfile(OrganizationProfileData organizationProfile, OrganizationProfile profile, IEnumerable`1 schemaValueNames)
   at Unify.Connectors.SharePoint.SharePoint2010WCFService.UNIFYIdentityBrokerService.SharePoint2010OrganizationProfileService.UpdateOrganizationProfile(OrganizationProfileData organizationProfile, String[] schemaValueNames)
   at SyncInvokeUpdateOrganizationProfile(Object , Object[] , Object[] )
   ...).

 




Affected Versions:
Fixed by Version:

Answer

Answer
Answered

In all three cases, the stack traces show the error is raised inside the Microsoft library (Microsoft.Office.Server.UserProfiles) and we are reporting them as-is.

Under review

Yes, it appears to be a SharePoint permission error. What have you attempted to fix it?

Just a review of the permissions outlined in the doco. These look OK to me.



The account is also a farm admin. Is there anything I need to do to get this operational?








Hi Matt,

Is this the first export to SharePoint, or have there been successful exports before this? If so, is there anything different about this export, perhaps a particular field that's being updated that hasn't been updated before?

It's the first export.

The old solution is using the same service account & is also reporting errors on bot user and org exports, but they are different:

Orgs

System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Object reference not set to an instance of an object. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.Office.Server.UserProfiles.OrganizationProfile.set_Parent(ProfileBase value)
   at Microsoft.Office.Server.UserProfiles.OrganizationProfileManager.CreateOrganizationProfile(ProfileSubtype subtype, ProfileBase parentProfile)
   at Unify.Connectors.SharePoint.SharePoint2010WCFService.UNIFYIdentityBrokerService.SharePoint2010OrganizationProfileService.AddOrganizationProfile(OrganizationProfileData organizationProfile, String[] schemaValueNames)
   at SyncInvokeAddOrganizationProfile(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at...).

Users

System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Invalid Property Value: Could not find SID corresponding to input account name. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
Microsoft.Office.Server.UserProfiles.PropertyInvalidValueException: Invalid Property Value: Could not find SID corresponding to input account name.
   at Microsoft.Office.Server.UserProfiles.UserProfileGlobal.ValidatedPerson(Object value, UserFormat userFormat, UserProfileApplicationProxy userProfileApplicationProxy, Guid partitionID)
   at Microsoft.Office.Server.UserProfiles.UserProfileGlobal.ValidatedSingleValue(Object value, ProfileSubtypeProperty prop, PropertyDataType propDataType, UserFormat userFormat, UserProfileApplicationProxy userProfileApplicationProxy, Guid partitionID, SiteContext si)
   at Microsoft.Office.Server.UserProfiles.UserProfileGlobal.ValidatedValue(Object value, ProfileSubtypeProperty prop, PropertyDataType propDataType, UserFormat userFormat, UserProfileApplicationProxy userProfileApplicationProxy, Guid partitionID, SiteContext si)
   at Microsoft.Office.Server.UserProfiles.ProfileValueC...).



Is there anything I need to do to get this operational?

The prerequisites from the documentation you linked have been sufficient for all previous deployments.

The old solution is using the same service account & is also reporting errors on bot user and org exports, but they are different:

How long has this been failing? I couldn't say whether these are related, I suggest taking all of these errors to a SharePoint administrator.

OK. 

Over a year in dev.

Is the error I have listed exactly what the API is returning?



Answer
Answered

In all three cases, the stack traces show the error is raised inside the Microsoft library (Microsoft.Office.Server.UserProfiles) and we are reporting them as-is.