New answers tagged

0

If AD properties are already mapped with user profile properties, then you can get them using REST API. http://siteurl/_api/SP.UserProfiles.PeopleManager/GetMyProperties Just make GET request to the above end-point, it will return you current user's properties. Get all properties of Specific User SP Online http://siteurl/_api/SP.UserProfiles....


0

I had the same issue with my account. It happens when you log-in with Service Account to server and then use your account to browse your profile or do some activity. You need to log-in with service account on the server and then check credential manager it might be saved their which needs to be deleted.


0

I personally had a few problems with AD Groups not long ago. I ended up finding a blog post about Security Token Caching. Long story short, changes make in AD Groups weren't applied to the SharePoint site, at least not immediately, due to these token expiration delays. Alternatively, an IISReset appeared to push all the changes immediately. Not sure if ...


1

Solution: there've been wrong data in ActiveDirectoryCustomQuery of the picker settings: ActiveDirectoryCustomQuery = "(&(objectCategory=person)(objectClass=user))" => set to null by ActiveDirectoryCustomQuery = $null resolved the problem


0

Since the issue is intermittent, I believe this is something related to object cache. In SharePoint Server 2013, querying for items is linked with the user account that makes the query. Various parts of the publishing feature make queries for which the results are cached in the object cache. The object cache makes its queries as one of two out-of-box user ...


1

Make sure that you are running your code from the server as an administrator. Also replace Localhost with the actual Web Application URL.


0

At least a complete recreation of the farm from the config database up is required. If you installed AD on this specific server, then your local accounts that you used to configure SharePoint are now completely gone. There are no local computer accounts on a DC (unlike a member server). Thus a complete recreation is required for the farm. You 'could' ...


0

Run SharePoint configuration wizard > disconnect this server from your farm if you didn't select standalone installation at the beginning of the current installation > after SharePoint configuration wizard has been finished try to run it again and configure new farm with the new domain users account.


0

@hello B, Waqas Sarwar MCSE is right. If you installed Active Directory AFTER installing SharePoint Farm, you mess up all the permissions and database access, because AD users are not the same as the users you had before. I am guessing it is a dev environment (since u installed DC on SP machine), so the easiest way would be to start from scratch: ...


0

Go to Services > Search For SharePoint Timer Service > Make sure that it's started and try to restart it. then reset IIS Again, find all related Project server services and make sure it was started. If the issue did not solve try to check the correlation ID using ULS Viewer and come back with its details.


0

create another user like AppDeveloper in active directory and provide site collection administrator permissions in site


0

You can query AD membership using this workaround: var clientContext = new SP.ClientContext(); var groupId = 5; // the group membership ID for the group you want to check var group = clientContext.get_web().get_siteGroups().getById(groupId); clientContext.load(group,"CanCurrentUserViewMembership"); clientContext.load(group,"OnlyAllowMembersViewMembership"); ...



Top 50 recent answers are included