After configuring User Profile Synchronization, I found that SharePoint People Search could still not work as the the content source for the user profiles was being denied access.
Data and Advanced Analytics. Formerly SharePoint.
Posts
This one time I was trying to programmatically modify an SPListCollection, and I stabled into the error " Collection was modified; Enumeration operation may not execute ". This error came about during the code block that looped through the SPListCollection and attempting to update the collection.
This one time I was trying to figure out why every time I created a SharePoint lookup field, be it programmatically or via the UI in SharePoint 2010 and 2007, which looks up to another SharePoint list field, it would always have a value "none" in it when in use. So now I really wanted to eliminate that value...
Hello folks. Once upon a time, I was trying to create SharePoint Task list Alerts programmatically for each user that had been granted permissions to the specific site. The requirement was that these users would be assigned tasks and they needed to receive notifications summarising all the tasks that they had been assigned, on a daily basis.
So this one time I was creating a SharePoint view programmatically, whose items I wanted to be ordered as "Most recent item must be top". This meant ordering by the "Created" column in descending order. So I used the following query:
Normally, for Specialists that are installing their SharePoint 2010 Demo environments, so as to demonstrate custom solutions to clients, they usually do their installations onto their machines (Laptops) that in most cases are connected to their company domains. So what happens when the Specialist goes home or is at a client site is that, their SharePoint 2010 Search fails to return any results, and the wonder why this is so when not only are there no errors being registered but they also have full permissions on anything they can think of, after all, they did the installation themselves using an account with admin privileges. ;)
Recently, a lot of people have been faced with the Taxonomy error message that says "The Taxonomy feature (Feature ID “73EF14B1-13A9-416b-A9B5-ECECA2B0604C”) has not been activated" and they wonder why this is so when their installation is so clean, both on site collection features and site features, this Taxonomy feature is not listed, and the administrator ends up activating it via STSADM. Did you know that creating a BLANK SharePoint site collection does not activate the Taxonomy feature? well now you know :), so that you can now include this step in your deployment documentations.