Skip to main content

Error "403 Forbidden" on Sharepoint Search Settings Page

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 system folder to the way they were by running attrib +s c:\windows\tasks
4. Then restart the search service on the index server
5. And perform a full crawl

Depending on how big your databases are, will determine how long the crawling and computing ranking will take, ours took about 5 hours and after which, the search site for the live environment came up.

Am still struggling with the test environment search site as the tasks folder keeps on denying access when I try to ran attrib -s c:\windows\tasks

Later mates….will tell you more soon.

Comments

Christoph said…
Hello Christopher,
I am getting the same error accessing the Search Administration Page in the Shared Service Provider Settings Page --> 403.

I have 5 Servers in our farm, 3 Web Front Ends, 1 Application Server and 1 Indexing Server. On wich server do I have to execute the stsadm command to fix this problem?

My guess is the Indexing Server. Right?

Thanks,
Chris
Christopher said…
Hi Christoph,

Yes please run the stsadm commands on your indexing server (in my case, it was the server that was running central admin).

Regards,
Chris.
Anonymous said…
This is great. wishing you all the best in all your daily applications development and hope to learn more from you as I read your site.May the Lord Himself continue to give you the knowledge and strength that you need to accomplish your vision. Mwila (ATS IT)
Tripwire said…
Which worm exactly?

Popular posts from this blog

Zambia's first Helpdesk System on SharePoint

For my 25th birthday today 3rd March, 2009, allow me to present to you another first of its kind in Zambia. Yes we have done it again, having been Project manager, I present to you Zambia's first Helpdesk System which Masialeti and I have developed on Microsoft Office SharePoint Server 2007. The system also implements SharePoint designer workflows, Infopath forms, SharePoint document library and sends email notifications to the relevant personnel. When a user logs in a call, the user automatically receives a mail from the system, telling them that their call has been received and is being attended to, IT section will also receive a notification and the helpdesk manager will assign the call to the right IT guy who will also automatically receive a mail notification from the system. When the call is resolved, the user again automatically gets notified by the system with a mail giving them description of the problem they logged and also how it has been resolved. The user also has an

How to implement a SharePoint "Change Management Process"

Not so much from the technical point of view, SharePoint Change Management is the process of monitoring and controlling changes within a SharePoint project. By managing the implementation of change, you can: • Reduce the impact of changes to the SharePoint project • Identify new issues and risks as a result of changes raised • Ensure that changes do not affect the SharePoint project's ability to achieve its desired objectives • Control the cost of change within the SharePoint project Change Management is comprised of the following processes: Step 1: Identify Change: The first step in the change process is to identify the need for change. Any team member can suggest a change to the SharePoint project, if he or she believes it is needed to keep the SharePoint project producing deliverables to the customer's specified requirements. After identifying a need for change, the team member records relevant information on a Change Request Form (commonly called a CRF), describing the chan