I’ve noticed that this issue came up few times in different environments where Team foundation server 2010 configured with out of the box SharePoint (WSS) installation. I thought of writing this post that might help someone having the same issue.
The Problem: SharePoint search was not working in the current production environment and when you search you get a error message saying
‘Your search cannot be completed because this site is not assigned to an indexer. Contact your administrator for more information’.
You also notice that the SharePoint search service is running as a windows service in the service console but not visible under farm services in the Central Administration.
The cause: Search services not properly configured registered in the SharePoint farm level.
The resolution steps:
1. Go to Central Admin as login as the farm Administrator
2. Go to Application Management tab
3. Select SharePoint Web Application Management heading | Content databases
4. Ensure your web application is the one selected
5. Select your content database name
6. Under Search Server – select your server (if your search server drop down is disabled please follow the additional steps below)
7. Go to 12 hive folder and open stsadm.exe utility
8. Run the following command psconfig.exe -cmd services -install
9. Then run stsadm -o spsearch -action start (specify the farm account if required)
This process will register the search services within the SharePoint (WSS) farm and search service will now appear under central administration. Now you can click the service service and create a indexing schedule. After indexing job is completed for the given web application you will notice that search results appear as expected.
Windows Identity Foundation (WIF) is the platform on which SharePoint 2010 claims authentication is based. WIF, which is fully supported in SharePoint 2010, ADFS 2.0, ASP.NET, Windows Communication Foundation (WCF), and any other .NET application you care to develop, provides the infrastructure necessary to generate, transmit, and process claims-based identity in a simple and straightforward manner. It removes the roadblocks imposed by legacy authentication schemes like NTLM and Kerberos and puts control directly into the hands of developers, users, and IT security professionals. long story short, it’s a framework written to help solve identity issues common in the of cloud computing and service-oriented architecture.
The idea of claims based identity is one that many people are willing to try. Getting accurate information out there to the public though does take time.
The important point is this is based on industry standards. Many different entities are on board along with Microsoft in this matter. The digital world continues to give us new opportunities and those involved believe that this will help all of us to get the most out of it. There is a strong foundation in place to continue building upon. The use of AD FS v2, CardSpace, and Windows Identity Foundation are all important pieces of this puzzle.
As a demonstration of these capabilities, I’ll show how SharePoint 2010, WCF,and WIF can be put together to solve the identity delegation problem. In this demo session part 1 I start establishing the trust relationship between ADFS 2.0 and SharePoint with PowerShell and demonstrate how the claims get into SharePoint.Then we build and deploy a claims viewer Webpart with WIF programming model. In part 2 We start with a web service that is front-ending line-of-business information stored in a SQL database. Then, we’ll configure it to use WIF to request the calling user’s claims from SharePoint and process the token so that authorization decisions can be made. we’ll surface this information in SharePoint 2010 as an External Content Type using Business Connectivity Services (BCS).
Click here to view a recorded screencast of this session.
The slide deck of this session is shared here