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...
Data and Advanced Analytics. Formerly SharePoint.