Skip to main content

The search application for 'SharedServices' on server [SERVERNAME] is not provisioned.

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. Start the OWSTIMER and give it a few seconds so that the new XML files from the location you deleted then are re-populated.

5. Central Administration > Operations > Global Configuration > Timer job definitions > Application Server Administration Service Timer Job > Enable.

and your search settings should now be accessible.

Thanks to Joe Rodgers for pointing me in the right direction.

Comments

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