Storytelling With Analytics

If this error comes up in the Search Service Application Administrative Status page

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.

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. ;)

Happy New Year All, I stumbled into an error "The search application for 'SharedServices' on server [SERVERNAME] is not provisioned. Confirm that the Windows SharePoint Services Timer service and Windows SharePoint Services Administration service are running on the server" when I tried to open search settings from my SSP site. After some little reasearch on the Internet, I came to find that most likely the config database cache was corrupt, and to resolve this, I had to clear the cache. So here is how I went about it: 1. Central Administration > Operations > Global Configuration > Timer job definitions > Application Server Administration Service Timer Job > Disable. 2. Then open windows administrative services (services.msc), stop Windows SharePoint Services Timer (aka OWSTIMER) 3. Navigate to C:\ProgramData\Microsoft\SharePoint\Config\GUID and delete only the XML files from the directory, then open the cache.ini and change the number in it to 1. 4. Sta...

Ok so I had to struggle with this error for like 48 hours, busy googling for a solution. This error came up at the same time on both our live and test environment after we were hit by the worm Microsoft reported a few days ago. So here is how I went about sorting it out: Using STSADMIN commands 1. I first ran stsadm -o osearch -action stop –f 2. Then stsadm -o osearch -action start -role indexquery 3. And stsadm -o execadmsvcjobs So now I tried to access the search site and it told me that I had to assign an index server, of which I did, then I again from the index server had to run stsadm -o execadmsvcjobs. At this point, I had to provide access to c:\windows\tasks, from the command line, on our index server for the local group WSS_WPG as follows 1. By running attrib -s c:\windows\tasks on the index server so as to be able to change the tasks system folder attributes. 2. Then I added the local group WSS_WPG with read and write access 3. And now take back the attributes of the tasks sy...