.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Can not start Office sharepoint server search (The search service instance on this server is not onl

Posted By:      Posted Date: October 06, 2010    Points: 0   Category :SharePoint


- Started WSS search -- OK

- Tried to start Osearch with Central Administration -- resulted in error

- Tried to start with stsadm command:

>stsadm.exe -o osearch -action start -role indexquery -farmcontactemail fname.ename@
mydomain.com -farmperformancelevel PartlyReduced

 -farmserviceaccount mydomain\pre_search -farmservicepassword phoapius

-defaultindexlocation D:\Sharepoint_index -propagationlocation D:\Sharepoint_index


Error message : The search service instance on this server is not online

And in the log:

OWSTIMER.EXE (0x2670)                    0x241C Office Server                  Setup and Upgrade              8u3j High     Registry key value {SearchThrottled} was not found under registry hive {Software\Microsoft\Office Server\12.0}. Assuming search sku is not throttled.  


View Complete Post

More Related Resource Links

How to stop Office SharePoint Server Search Service


Hi, anyone know how to force the Office SharePoint Server Search Service to stop? Its status is currently "stopping" and has been all morning. I'm trying to troubleshoot the same problem as the one in this thread: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=911552&SiteID=17


The crawling never stopped on my server, prohibiting backups, and other timed database jobs.


Any suggestions? Thanks!

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Adm

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (3ea4ace8-84f5-4d62-9c73-1325698a045a).

Reason: Logon failure: unknown user name or bad password

Techinal Support Details:
System.ComponentModel.Win32Exception: Logon failure: unknown user name or bad password
  at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.SynchronizeDefaultContentSource(IDictionary applications)
  at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
  at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

Above exception appears every minute in windows logs. Your help is appreciated.


Apriori algorithm [association rule]

Office Sharepoint Server Search not working but Windows Server Search is.

I am having an annoying Issue with the Sharepoint 2007 Enterprise search functionality. I cannot get the Search Centre to work, the out of the box webparts crash the page except the Searchbox when the others are closed. The event viewer shows up numerous Errors (Office Sharepoint Server - EventID 7080) returns with and the same when trying to add a search related web part (e.g. core.results, federated etc). EventID 6398 - Timer is a regular as is 7080. Details below.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified).

Remote connections are connected, I am not 100% on the Instance name, (how would I go about checking this?)

Also I cannot access the link to SharedServices1 - Open Shared Services Admin site (not clickable), guess it's permissions but I seem to have full site permissions, I think I need SSP-Admin to make more edits to the Search, maybe this is related :s

Both Search Servers are runnig, I have tried everything I can think of to fix this and allow the Search Centre to work.

I am running Sharepoint 2007 on SQL Server 2008.

Team Foundation Server and WSS 3.0 SharePoint Service Search not visible

I am having issues with setting up SharePoint Search service on the TFS 2008 server WSS 3.0. The Windows SharePoint Service Search service doesn't appear in Central Administration>Operations>Services on Server page. Only the Central Administration, Windows SharePoint Services Incoming E-Mail, and Windows SharePoint Services Web Application appear. I have Windows SharePoint Service Search running through Services in Windows and still it doesn't appear on the page to configure it. The service account that this service running under has db_reader role access to the WSS_Content database and is a db_owner for the WSS_AdminContent and WSS_Config database as well as for the WSS_Search database. I have executed iisreset and even rebooted the server to no avail. The installation/set up of TFS was done prior to me join the team. It was a default set up with dual servers. The Event Logs show nothing out of the ordinary to help me troubleshoot the issue. Does anyone have any other suggestions I should try or other things I should be looking for? Thank you in advance, WillWill Piedmont

SharePoint Portal Server 2001: Search and Access Disparate Data Repositories in Your Enterprise


The knowledge worker is greatly empowered if she is able to access information across the enterprise from a central access point. With the SharePoint Portal Server 2001 Search Service you can catalogue information stored in Exchange public folders, on the Web, in the file system, and even in Lotus Notes databases. This article discusses the use of ActiveX Data Objects and the Web-based Distributed Authoring and Versioning protocol for creating search solutions based on SharePoint Portal Server 2001.

Kayode Dada

MSDN Magazine April 2002

SharePoint Enterprise Search Migration Tool for SharePoint Server 2010

Use this tool when you upgrade to SharePoint Enterprise Search to migrate search-related data, such as best bets, search scopes, and site collection search settings.

FAST Search for SharePoint Server 2010 SDK

Learn how to develop and deploy search solutions in SharePoint Server 2010.

Search Customization and Development Options in SharePoint Server 2007

Examine the powerful platform of SharePoint Server 2007 search for the end user and developer. Learn about the built-in Web Parts for search and writing search queries for your applications.

Displaying the Server Ribbon and Site Actions Menu on Customized Search Pages Upgraded to SharePoint

Learn how to add the Site Actions menu and SharePoint Server ribbon to SharePoint Server 2007 search pages that you upgrade to SharePoint Server 2010 by using visual upgrade.

SharePoint Server 2010 Search - not returning results but crawling without errors

I have created a Search Service Application on a SharePoint Server 2010 (RTM) Farm and used the default Content Source. I started a Full Crawl and it suceeded with no errors etc. I ran it a few times and no issues. But if I go to the Intranet Portal Web Appliaction and do a search for a document that would have been crawled it does not show up in search results...nothing does. I am not getting any errors in Event Log or ULS Logs relevant to Search. How can I troubleshoot this problem further?SharePoint Solution Architect, Perth Australia - Microsoft Virtual Technology Specialist - MCTS WSS Dev, WSS Adm, MOSS Dev, MOSS Adm - http://wss.made4the.net/ - Founder of http://www.sharepointdevwiki.com/

Search Server Express 2010 - Access Denied when attempting to manage Search Service Application or P

I first noticed this error with the Search Service Application when I was no longer able to use the search portal, but have since noticed the issue with the PowerPoint Service Application.  When I navigate in Central Administration to either the "Farm Search Administration" or the "Manage service applications" pages and attempt to manage the "Search Service Application", I get this error: Error: Access Denied  Current User You are currently signed in as:  WHEELERS\MyUserName   Sign in as a different user    I have tried removing the service application and re-adding it, changing the application pool to running under an existing application pool as the farm administrator, as another application pool with the same identity as the primary web application, and as another application pool running under the SP-SearchService identity. The big recent change with SharePoint, aside from fixing the previous issue where I was incorrectly using CNAMEs with Kerberos, was to switch the main web application to claims authentication. That site correctly works with claims based authentication and Kerberos.

Crawl Component Resilience Requires Sharepoint Server Search Administration Component?

I have a single crawl database and two crawl components pointing to that crawl database. One of the crawl components also has the Sharepoint Server Search Administration component running. When I close down the server running the Sharepoint Server Search Administration component crawling stops. I removed the crawl component from the server running Sharepoint Server Search Administration component and reindexed and this worked. So the additional crawl component works fine. Checked that incremental crawl would run in 5 minutes. Downed the Sharepoint Server Search Administration component server and uploaded some new content. Crawling did not run. Can anyone confirm that this is expected behaviour? I am now trying to transfer the Sharepoint Server Search Administration component to the other server as part of Disaster Recovery preparation and this is failing as per another recently opened problem.  

SharePoint Search Server 2010 Express returns no search results for non-admin users

This is going to sound crazy, but anyway... bare with me... I have a SharePoint Search Server 2010 Express (RTM) installed with a crawl account (call it sharepoint_crawl) which has full read permission to an entire site collection of 100,000 documents. I have logged in with this account to make sure it has read access to everything, and it does. I run a full crawl of all documents and allow it to finish. If I try and search the content for an extremely common term (i.e. 50,000+ hits) I get no results. However, if I log in with a site collection admin I do get search results. There are no indexing errors or query errors in either log files or event log. Everything looks like it is working correctly - just no results for non-admins Anyone tripped on this? I have recreated the crawl account and perform a full re-index with the same results. What gets me is that the crawl account does have read permission to the content it is indexing, the content is indexed correctly, but the crawl account cannot get results back. It is as if security-trimming is removing everything. Any ideas?

SharePoint search server 2010 crawl rules

My client wants to create a number of scopes by crawling specific subsites of a CMS 2.0 site.  The CMS site is crawled as a website and security is ignored (e.g. results are not security trimmed). As an example, they want to create a scope called “Audit”.  This scope will use a content source which crawls all content starting at http://server/services/audit and http://server/wssservices/audit. The first is the CMS 2.0 site, the second is a WSS 3.0 site that contains documents for the CMS site. I setup the content source with start address of http://server/services/audit and http://server/wssservices/audit with the crawl settings set to ‘only crawl within the server of each start address’. Additionally, I have created rule with path http://server/services/audit* and set the configuration to “Include all items in this path”, with “Crawl SharePoint content as http pages” also selected.  I have created rule with path http://server/wssservices/audit* with the same configuration settings, except  “Crawl SharePoint content as http pages” is not selected . I have also performed a full crawl after creating the content source and crawl rules. What I would expect to happen is that only results from http://server/services/audit or documents linked from http://server/wssservices/audit would show i

Missing Assembly Reference for Microsoft.Office,.Server.Search

I am getting the following error while accessing the namespace: Microsoft.Office.Server.Search.Query  The type or namespace name 'Query' does not exist in the namespace 'Microsoft.Office.Server.Search' (are you missing an assembly reference?)   I have added references to 1) Microsoft.Sharepoint  2) Microsoft.Office.Server and  3) Microsoft.Office.Server.Search I am using VS 2010 and set the framework version to 3.5 and Sharepoint RTM Version  vinod kumar Bhasyam

Hide top menu search bar in Sharepoint server 2010

Hi I've tryed this guide to hide the top menu search bar with Sharepoint Designer in Sharepoint server 2010 ------------------------------ Open SharePoint Designer          Open the site in SharePoint Designer   On the left navigation pane, click on “All Files” (bottom item on menu)   Click on the folder “_catalogs”   Click on the folder “masterpage”   Click on the file “v4.master” An overview will open Make sure that you have selected “Split mode” viewing          Click on “Edit file” (I hope this is correct, because I have a Dutch version)          Select “Skewer click” on the ribbon          When you click on a item, you are presented with a submenu. Select in this case, the Help-button, “a#TopHelpLink” For the Search-field, you have to select “div#s4-searcharea.s4-search s4-rp”.          In the code properties screen, on the right side, select Style          And set visibility to “hidden”   Save your master file. ------------------------------ But it dosn't work, it puts a little red line under "hidden", Like if y

Search server 2010 setup - error creating search service application

I am running in a very similar siutation as this post:

I am configuring a new Search Server 2010 production environment.

I used the search setup account to run the setup and run the SharePoint Products Configuration Wizard.

During the first run of the SharePoint configuration wizard (where the farm account and service applications are setup), the process failed because the search service application could not be created.  

Errors were encountered during the configuration of the Search Service Application.
System.Data.SqlClient.SqlException: User does not have permissiont to perform this action.

I was under the assumption that the setup account had securityadmin and dbcreator SQL Server roles.  However, this was not the case and I had them added.  My original thought was the setup failed because of this.  After those roles were added, I tried to recreate the search service application and I still get a failure.

I am pretty sure I have followed the prerequisites as prescribed by Microsoft in terms of account setup (
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend