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.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

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.
8 comments
Read more

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 ...
7 comments
Read more

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...
2 comments
Read more