.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

How to rebuild my search server?

Posted By:      Posted Date: September 01, 2010    Points: 0   Category :SharePoint
I have a broken search server where almost all services are stopped and stopping as shown on this picture   I tried to use the wizard to do a repair on that server but at stage 4 it stops and gives me a whole logfile. I can't figure it out what it needs so I maybe can disconnect this server from the actual farm, uninstall sharepoint on that server, reinstall and reattach it. Is that something doable?

View Complete Post

More Related Resource Links

MS SQL Server: Search All Tables, Columns & Rows For Data or Keyword Query

If you need to search your entire database for specific data, this query will come in handy.

So when a client needs a custom report or some sort of custom development using Great Plains, most of the time I will have to track down the data in the system by running this query and find the table(s) it is in.

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

Search Server Gatherer - Custom hierarchical protocol handler ISearchProtocol for MOSS 2010



Search server gatherer calls CloseAccessor() and shutdown() on ISearchProtocol after GetChunk() even if the FILTER_E_END_OF_CHUNKS is not returned. After calling shutdown() it stops calling the createaccessor() with new URL. I want to create a hierarchical indexing but I am not gatherer is not suporting this. The same piece of code is working fine in MOSS 2007, I am facing this issue in MOSS 2010 only. Is there anything changed in MOSS 2010 which is creating this issue?



Pass the server variable to search core result web part


I'd like to custom the search core result web part to filter results based on the log on user name.

It can easily be done in Dataview web part.

However the search core web part doesn't accept "<parameterbining>" to pass in the server variable [logon_user]. I can't figure out how to use <xsl:param> to get this server variable either.


Any ideas? Thanks a lot!

If you get confused, listen to the music play...

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.

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.

Solution deployment requires executing execadmsvcjobs command on search server to complete deploymen

We have multiple Sharepoint 2007 farms and deploy custom code weekly to the farms. On one o the farms it is required to run stsadm -o execadmsvcjobs on the Search server in the farm in order for solution deployments to complete deploying. These are solution recycles that we are running. This is the only farm this happens on and all farms are identical. In central admin it shows the solution state as deploying. Farm Config Sharepoint 2007 SP2 w Dec Cumulative updates 1 WFE 1 Search server 1 SQL server

Cannot connect to FAST Search server

From the ULS: Failed to connect to myfastserver.mydomain.com:13391 sp. Error=Failed to initialize session with document engine: Unable to resolve Contentdistributor  [documentsubmitterworkerthread.cpp:132]  d:\office\source\search\native\gather\plugins\contentpi\documentsubmitterworkerthread.cpp Docpush -c sp myfile.txt works fine. And I can do a search from FAST search center and find the new file. Q1: How do I determine if SSL is working correctly between my SP Server and my FAST Search Server? Q2: The FAST Search server has port 13391 open. Does this port also need to be opened on the SP Server or are all communications (crawling etc) made over port 443? Q3: Why does the error refer to d:\office... when this the DVD drive (place FAST was installed from)

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/

Fast Search Server 2010 on Windows 7

Is it possible i can install Fast Search Server 2010 for  sharepoint  on windows 7 ?   Thanks in advancehttp://mykbdump.blogspot.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.  

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