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

SharePoint: How to create a custom action to open Word Documents using "Edit in Microsoft Word".

Imagine you have a SharePoint custom search webpart, and on your search results, you return word documents, you will obviously want to at times be able to open them in your MS Word client program for editing. So basically, depending on your office client installed on your local machine, there are 2 different approaches that can be made for Office 2003 and Office 2007/10, using the same function " editDocumentWithProgID2 ". For Office 2003: - If your document libraries versioning settings have got "Require Check out" ticked, then you will first want to check out the document using: onclick ="CheckoutviaXmlhttp(‘{SiteURL}’, ‘{DocumentDownloadURL}’)" - Then to open the document, you use: onclick =" return editDocumentWithProgID2(‘ {DocumentDownloadURL} ’, ”, ‘SharePoint.OpenDocuments’, ’1′,’ {SiteURL} ’, ’0′);" href ="#" - and now combining the above 2 actions into one clickable action: onclick ="CheckoutviaXmlhttp(‘ {SiteURL} ’, ‘ {...

Zambia's first K2 BlackPoint roll-out

Reporting to you live from Code|Influence... My colleague and I have been managing our organization's SharePoint infrastructure for some time now and we have just rolled out the first K2 BlackPoint in the country, intended mostly for SharePoint workflow developments.

How to Scope your SharePoint Projects

The "SharePoint project scope" is all of the things that must be produced to complete a SharePoint project. These 'things' are called deliverables and you need to describe them in depth as early in the SharePoint project as possible, so everyone knows what needs to be produced. Take these 5 Steps to scope your SharePoint projects: Step 1: Set the Direction Start off by setting the direction for the SharePoint project. Do you have an agreed SharePoint project Vision, Objectives and Timeframes? Are they specified in depth and has your customer agreed to them? Does everyone in the SharePoint project team truly understand them and why they are important? Only by fixing the SharePoint project direction can you truly fix the SharePoint project scope. Step 2: Scope Workshops The best way to get buy-in to your SharePoint project scope is to get all of the relevant stakeholders to help you define it. So get your SharePoint project sponsor, customer and other stakeholders in a ...