Sharepoint 2013 - Search service not working

We have set the search service application to crawl incrementally. The crawls are taking a long time. The content is not vast over the single farm but we do have a few sizable document libraries, lists and media assets. Suggestions as to what to check
again first? Screen shot of the search admin page.

Hi,
According to your post, my understanding is that Search service failed to work in SharePoint 2013.
The cause is that Accounts that are used by application pools or services are members of the Administrators group on the local computer.
I recommend to change the user account to a predefined account, or to a domain user account that is not a member of the Administrators group.
More information:
http://technet.microsoft.com/en-us/library/hh344224(v=office.15).aspx
http://alstechtips.blogspot.com/2013/12/health-analyzer-accounts-used-by.html
http://absolute-sharepoint.com/2013/01/sharepoint-2013-service-accounts-best-practices-explained.html
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Similar Messages

SharePoint foundation 2013 Search is not working

Hi, Search was working 3 days back, but today its not working. So
1. I Recreated Search Service Application
2. Created Content Source and set full crawl.
3. And service application is associated to the web application also.
4. All Application pool id are running.
5. Created Search Site collection, even though search is not working.
The error message i got was shown below. How to resolve this issue. An help/thoughts.

Try to use word Home in search
Do we see site getting crawl in crawl logs
Navigate to the site for which you want to control the Web Parts in search results.
Click Site Actions, and then click Site Settings.
Under Site Administration, click Search and offline availability.
In the Indexing ASPX Page Content section, under
This site does not contain fine-grained permissions. Specify the site’s ASPX page indexing behavior ,
Always index all Web Parts on this site
http://office.microsoft.com/en-in/sharepoint-server-help/enable-content-to-be-searchable-HA010379092.aspx

How to properly create and configure SharePoint 2013 Search service with PowerShell?

Hello Forum,
I have installed SharePoint 2013 across three tier servers:
WFE Server (Of course, SharePoint is installed here. Bsically this is just a Web server)
APP Server (Of course, SharePoint is installed here + Central Admin + Service Apps).
SQL Server
I now want to create and configure the Search service, obviously on the APP Server, But of course the search functionality should work correctly on the WFE server to.
I want to do this via a proper PowerShell script. I found Spence Harbar's script on: (http://www.harbar.net/articles/sp2013mt.aspx), But it has three problems, and they are as follows:
1) Spence Harbar himself literally stated on his article that this script is for: "deploying on a single server farm", But what if I have three tier servers? Could anyone please help me out in suggesting the required tweaks in the
script?
2) By default Search uses the SP_Farm account, So, How can I change the script to use other dedicated account for the search service e.g. SP_SearchAcc ?
3) How can I modify the script to specify a default Search center?
4) Apart from all the three aforementioned point - Is the script missing anything?
I would greatly appreciate your inputs - Thanks !

the only differences are where you place the components. if you are doing a small server farm with a 1-1-1, most likely you just need to change the script so that you set the index and query processing component on the front end, but the others on
the app server. just a 2 second update... just keep in mind this will work, but I am making several assumptions without any knowledge of your farm, users, capabilities.
generally, there would be more of a breakout on the topology than that, but im guessing for this farm that you wont have dedicated search servers. also, a lot depends on # users (rps really), # items in index, size of VMs (RAM for query processing,
Disk for index, etc, etc), and making sure the topology works for your particular environment and needs.
if you want more detailed topology help, which aligns as closely as possible to "best practices" (not that those exist in SharePoint, go ahead and provide the total # users, average/peak RPS for search, current index size, content source types,
VM specs RAM, CPU, #/Size of drives, HA concerns/priority (obviously isn't, since only 1-1-1)
Christopher Webb | MCM: SharePoint 2010 | MCSM: SharePoint Charter | MCT | http://christophermichaelwebb.com

SharePoint foundation search is not working in SP2010 Foundation version

Hi,
I am using SharePoint Search2010 foundation version.
CA->Application management->manageservices on server.
But I checked in CA->Manage web applications
How i need to configure search functionality for web application.
I tried to search in site collections the following message i am getting.
Your search cannot be completed because this site is not assigned to an indexer. Contact your administrator for more information.
Can you please any one help me on this issue.
Thanks in advance.
Ashok

Is this the default search service application that came with the original installation. In SP Foundation, you cannot create Search Service Applications. If you deleted the original, you'll have to reinstall from scratch to make it work...
Nikolas Charlebois-Laprade Microsoft Certified Professional & Software Engineer http://nikcharlebois.com

How to delete Content Source in Sharepoint 2013 Search Service

I want to delete Default Content Source in Search
Service in SharePoint 2013 but delete button is disable?Please see the below image. Content Source Type=SharePoint Sites
How to do it?
If In Content Source type=Files than delete button enables but
not for the Content Source type=Sharepoint sites
Vishal Goyal

Hi,
try to remove it using powershell
$searchapp = Get-SPEnterpriseSearchServiceApplication "NameofSearchAPp"
Remove-SPEnterpriseSearchCrawlContentSource -SearchApplication $searchapp -Identity "Name"\Regards
Whenever you see a reply and if you think is helpful,Vote As Helpful! And whenever you see a reply being an answer to the question of the thread, click Mark As Answer

Sharepoint 2013 Reporting services not fetching data via linked server

We have a functional SharePoint 2013 farm in production with WFE (Server 1 , windows server 2012) and WFE ( Server 2 , windows server 2012) and SharePoint databases including report server databases on (Server 3, which SQL Server 2012 on windows
server 2012)
Kerberos Authentication is enabled and Windows Authentication happens. Claims to Windows Service seems to work correctly too. No double hop issue. The SharePoint Reporting Services seem to be configured correctly and Reports get generated as expected
in the following cases.
1. If data is being pulled from Server A (SQL Server 2008 R2 Server on Windows Server 2008), Report gets generated no issues.
2. If data is being pulled from Server B (SQL Server 2008 R2 Server on Windows Server 2008), Report gets generated no issues.
The problem:-
We have a view on Server A, which is fetching data from Server B. This report does not get generated. Gives an NT/Authority logon failure. Server B is created as a linked Server on Server A. The setting to run under users security context is checked.
If I execute Query Builder from Report Builder 3.0, the query on the view gets the data and data is displayed in the report for next 10-15 min but after that the connections gets lost or if the user logs out and logs back in, the connection is lost
again.
Has some one experienced a issue like this? Can a report not work on a view getting data from linked server? Or I have missed some thing really important.
Any help is highly appreciated?
cheers!
Rachna
Rachna

Hi,
From your description, my understanding is that you got an error when you clicked System settings after configuring Reporting Services service application.
What size did you use for the memory? Please make sure the server has enough memory to run SharePoint and all services.
In addition, please open
http://localhost:xxxxx/SecurityTokenServiceApplication/securitytoken.svc to check if there is something about this issue.
Here is a similar post about this issue, please take a look at:
http://whitepages.unlimitedviz.com/2012/07/setting-up-reporting-services-2012-with-sharepoint-2013/
As this issue is about Reporting Services, I suggest you create a new thread on SSRS forum, more experts will assist you with SSRS.
SSRS forum:
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=sqlreportingservices
Best Regards,
Wendy
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

SharePoint 2013 "Help Menu" not working (Sorry, the page you're looking for can't be found)

The Built in SharePoint 2013 Help Menu (?) on our Enterprise Farm for both the sites and Central
Admin does not work.
On Central Admin help the error comes back as: "Sorry, the page you're looking for can't be found".
The site collections Help menu gets the error :
"Unfortunately, help seems to be broken...
There aren't any help collections in the current language for the site you're using."
We have installed on all servers in the farm:
December 9, 2014 Cumulative Update for SharePoint Server 2013 package (build 15.0.4675.1000)
as well as the latest SharePoint update KB2768001 1/15/2013.
I have checked:
Get-SPHelpCollection
Title
Name
SharePoint Help
WSSEndUser.1033.15
SharePoint Foundation 2010
WSSEndUser.1033.12
Central Administration Help
WSSCentralAdmin.1033.15
SharePoint Server 2010
OSSEndUser.1033.12
SharePoint Help
OSSEndUser.1033.15
SharePoint Foundation 2010 Central Administration
WSSCentralAdmin.1033.12
Teacher Help
EDUTEACHER.1033.15
Central Administration Help
OSSCentralAdmin.1033.15
Student Help
EDUSTUDENT.1033.15
SharePoint Server 2010 Central Administration
OSSCentralAdmin.1033.12
PerformancePoint Dashboard Designer 2010 Help and How-to
DashboardDesigner.1033.12
The URL for the site collections is https://servername...../_layouts/15/help.aspx?Lcid=1033&Key=HelpHome&ShowNav=true
We are only using Default English (US) language packs.
In the directory of
Directory of C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\HCCab\1033
there are cab files.
There are no pending upgrades on any SharePoint or SQL server, all other SharePoint components are working
normally.
Any ideas or suggestions?
Thanks.
John


I'm interested in getting the local help to work while this is offline, I saw the following in an article, did you do this and it still does not work for you?
"However the help won’t show up in
SharePoint 2013 sites. You need to change the Help Collection item property SharePoint
Version to15 to
make it work."

How can I force delete SharePoint 2013 search service?

I installed Search service using PowerShell. It failed. I tried to remove the service and only partially removed. Now when i try to remove it again it says I cannot login to the search database - the search database no longer exists. Is there
a way to force delete the service?

Get -SPServiceApplication
Grab the Search Service Application id – [for example] 30b15b57-6bec-46b5-990d-541d99bab53b
then use this
Stsadm -o deleteconfigurationobject -id 30b15b57-6bec-46b5-990d-541d99bab53b (Preferred over the next method of PowerShell)
this was working for me even the ps command failed (I had corrupted DB)
Martin

Can you refine people search results using a SharePoint 2013 search service application connected in SharePoint 2010?

We have an SP2010 farm which is now using some of the service applications from an SP2013 farm, including the search, managed metadata and user profile. This is part of an upgrade programme of work which will involve upgrading infrastructure and
then gradually the sites, and this is seen as one way to minimise the impact.
So, the SP2010 search results are being generated by the SP2013 which is indexing the SP2010 content. The initial results appear fine, however, the refiners in the people results for Job Title and Department are no longer working. We are receiving
a 404 page not found, even though the page is there as was working before.
If we compare the URL generated in SP2010 for refining results to an OOTB SP2013 search centre site, there is clearly a big difference to the format. Example below is where LastName is Smith and then refined where Department is HR.
SP2010 URL which now gives a 404 error:
http://intranet2010/search/pages/peopleresults.aspx?k=LastName%3Asmith&r=%22owstaxIdSPShDepartment%22%3D%23832e3479%2Dd168%2D4620%2Dac69%2D9b00a4c4205b%3A%22HR%22
OOTB SP2013 URL:
http://intranet2013/search/pages/peopleresults.aspx?k%3Asmith#Default=%7B%22k%22%3A%22smith%22%2C%22r%22%3A%5B%7B%22n%22%3A%22Department%22%2C%22t%22%3A%5B%22%5C%22%C7%82%C7%824335%5C%22%22%5D%2C%22o%22%3A%22and%22%2C%22m%22%3Anull%2C%22k%22%3Afalse%7D%5D%7D
I've looked at the URL decoded versions so can see how the query is built up.
Any ideas? Is this even possible?
Matt

All working now. Turns out there was an entry in the web.config which was causing issues.
<denyQueryStringSequences>
<add sequence="ID" />
</denyQueryStringSequences>
Seems IIS is denying something in the query string. We removed the whole section as was not needed.
http://www.iis.net/configreference/system.webserver/security/requestfiltering/denyquerystringsequences
Thanks to a colleague who spotted this; I would've never of thought to check the web.config for something like this.

SharePoint 2013 web service: Error while sending claim based authentication request (The corresponding SID in the domain is not part of the intended account type)

We are using .asmx services for SharePoint features such as comments, and rating.
Service
Feature used
http://<<hostname>>/_vti_bin/socialdataservice.asmx
Commenting, Rating
http://<<hostname>>/_vti_bin/UserProfileService.asmx
For out of box workflows
In SharePoint 2013,
SharePoint – 80 web application is on claims based mode and user is logging in with windows authentication. With logged-in client context used to call SharePoint's default web service, we are getting below error message from
web service (Social data and user profile services).
Server was unable to process request. ---> The corresponding SID in the domain is not part of the intended account type.
When the service is accessed using console application with Visual Studio credentials (logged in user), we are able to access the service. Below is the code snippet
using (SocialDataService
service = new
SocialDataService())
service.Credentials =
CredentialCache.DefaultCredentials;
SocialCommentDetail detail = service.AddComment("<<url>>",
"Test Comment",
null,
null);
Are SharePoint 2013 web services not supporting request coming with claim based authentication web application?
Thanks, Pratik Agrawal (MAQ Software)

While this applies to 2010, I believe the same is true with 2013:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/925e5f46-317f-46d3-bc55-c67f07eb2372/call-sharepoint-web-services-using-claimbased-authentication?forum=sharepointgeneralprevious
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint server 2013 Search Service App on Windows server 2012 R2 not working

Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM
was set up to access the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate
to search service app admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is
in a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem
with Search Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.
Thanks a lot.

Hi,
According to your post, my understanding is that SharePoint server 2013 Search Service App did not work on Windows server 2012 R2.
Please make sure you configure Search Service Application correctly. You can refer to:Create and configure a Search service application in SharePoint Server 2013
I recommend to created new Search Service Application, and made a full crawl. Then assigned the new SSA as the default SSA for webapplications. Finnlay checked the issue doesnt occur now,
If all search related components now are online, to keep the enviroonment clean, you can delete the old SSA.
Thank you for your understanding.
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Sharepoint 2013 search error - The search application 'Search Service Application 1' on server is not provisioned.Confirm that the Microsoft SharePoint Foundation Timer service and Central Administration service are running on the server.

Hi All,
I'm getting the below error in My SHarepoint 2013 search Administration page.
Crawler background activity - The search application 'Search Service Application 1' on server "" is not provisioned. Confirm that the Microsoft SharePoint Foundation Timer service and Central Administration service are running
on the server.
and when i click on Crawl Log and content source
it throws the below error
The search service is currently offline. Visit the Services on Server page in SharePoint Central Administration to verify whether
the service is enabled. This might also be because an indexer move is in progress
When i check the search status
Get-SPEnterpriseSearchServiceInstance, it shows all the components are online.
As of now search service application is online and search is working.But not sure why it throws the above error.
I have restarted timer service,search service in services.msc and cleared the sharepoint cache as well.
But no luck,This is happening in my prodcution environment.
Any help will be greatly appreciated.
There are the logs i have found
05/23/2014 13:03:22.71 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:http://dca-app-617:90/_admin/search/listcontentsources.aspx?appid=e830c1b3%2Dc3e4%2D4097%2D85fd%2Daa5248346d2e) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.71 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.73 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.79 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Search Administration djs2 High [Forced due to logging gap, cached @ 05/23/2014 13:03:22.76, Original Level: VerboseEx] {0} d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.79 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Database 8acb High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.80 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Search Administration djj1 High Unable to find application 'b9c8106c-c7ed-4eb3-96c9-ae1881ffb695' d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Search Administration djj1 High Unable to find application 'b9c8106c-c7ed-4eb3-96c9-ae1881ffb695' d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General 8nca Medium Application error when access /_admin/search/listcontentsources.aspx, Error=The search service is currently offline. Visit the Services
on Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress.   at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object
sender, EventArgs e)     at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e)     at System.Web.UI.Page.HandleError(Exception e)     at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Runtime tkau Unexpected Microsoft.SharePoint.SPException: The search service is currently offline. Visit the Services on Server page in SharePoint Central
Administration to verify whether the service is enabled. This might also be because an indexer move is in progress.    at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object sender, EventArgs e)
at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e)     at System.Web.UI.Page.HandleError(Exception e)     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General ajlz0 High Getting Error Message for Exception Microsoft.SharePoint.SPException: The search service is currently offline. Visit the Services on
Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress.     at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object
sender, EventArgs e)     at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e)     at System.Web.UI.Page.HandleError(Exception e)     at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General aat87 Monitorable  d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation DistributedCache ah24q Unexpected SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts are present in the farm. d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation DistributedCache ah24w Unexpected Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedViewStateCache'
- Exception 'System.InvalidOperationException: SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts present in the farm.     at Microsoft.SharePoint.DistributedCaching.SPDistributedCachePointerWrapper.InitializeDataCacheFactory()'. d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General ajb4s Monitorable ViewStateLog: Failed to write to the velocity cache:
http://dca-app-617:90/_admin/search/listcontentsources.aspx?appid=e830c1b3-c3e4-4097-85fd-aa5248346d2e d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:http://dca-app-617:90/_admin/search/listcontentsources.aspx?appid=e830c1b3%2Dc3e4%2D4097%2D85fd%2Daa5248346d2e)).
Execution Time=109.695855199474 d4c6939c-b10d-4000-6d95-14caeefe67df
Anil Loka

Please try below mentioned steps:
1. Central Administration > Monitoring > Review job definitions > Look for following timer job "Application Server Administration Service Timer Job" > Disable
2. Then open windows administrative services (services.msc), stop SharePoint Timer Service
3. Clear SharePoint Timer configuration cache by following steps mentioned in below blog:
http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx
4. Start SharePoint Timer Service and give it a few seconds so that the new XML files from the location you deleted then are re-populated.
5.Central Administration > Monitoring > Review job definitions > Look for following timer job "Application Server Administration Service" Timer Job > Enable
Please ensure that you mark a question as Answered once you receive a satisfactory response.

SharePoint 2010 Search Service is not working on replication of Servers.

Hi, I have a problem. I have a SharePoint Farm in which there are two servers with ip's 192.168.8.60 and 192.168.8.62. Both are replicas of each other. The search service is working on 192.168.8.60 and not working on 192.168.8.62. What can be the problem?
Also tell me how can I make the search service working on 192.168.8.62. What can be the issue?

Hi,
Could you provide more details about how the search service doesn’t work?
Are the search service unable to be started in CA -> Application Management -> Manage services on server? Or did you find it not working when you did searching? If that is the case, could you provide the error about
it?
It would be helpful to solve this issue if you provide more details about the issue.
Best Regards,
Dean Wang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Autocomplete is not working for Sharepoint 2013 search box.

I added the below code in cewp in sharepoint 2010 and autocomplete worked fine.
http://sharesilver.wordpress.com/2011/11/26/auto-suggestioncomplete-in-sharepoint-search-text-box-with-jquery-like-in-google-part-1/#comment-605
when i added this code in sharepoint 2013 by changing the searchbox class name in the code. it is not working. why ??
Sharepoint 2010 searchbox class name ="ms-sbplain"
what is Sharepoint 2013 searchbox class name ?? i added "ms-textLarge" as class name but it didn't work.
Thanks in advance.
M.M

Hi M.M,
The class for SharePoint 2013 Search box input element is as follow, please check if it is what you want.
class="ms-textLarge ms-srch-sbLarge-fullWidth ms-srch-sb-prompt ms-helperText"
The project code you are using is updated in codeplex, and the query suggestions (similar to this autocomplete) is an OOB feature in SharePoint 2013 enterprise verison, you can take a look.
http://spautosuggestion.codeplex.com/
http://technet.microsoft.com/en-us/library/jj721441.aspx
Thanks
Daniel Yang
TechNet Community Support

Search suggestion not working for anonymous user in sharepoint 2013

Hi ,
Please help on this search suggestion not working for anonymous user in sharepoint 2013
shaik

You can create a search center site, and set the search center site to
allow anonymous access.
Also see this link - http://blog.mastykarz.nl/search-query-suggestions-anonymous-users-sharepoint-2013-mavention-query-suggestions/
(As this is regarding a 3rd party tool, I suggest that you direct it to the provider support.)
Please 'propose as answer' if it helped you, also 'vote helpful' if you like this reply.

Sharepoint 2013 - Search service not working

Similar Messages

Maybe you are looking for