Working of search service
Hi All,
i want to know how does the search exactly works in backgroung in plumtree/alui/oracle webcenter portal search. can some one provide any link or doc regarding this. I am using Plumtree v6.0 and search server 6.0. please let me know if any other information is required.
Hi,
Search is very differnt in ALUI/ Plumtree from WebCenter.
ALUI/ Plumtree comes with its own search service. This service can be configured through the configuration manager for ALUI. They provide nice extension mechanisms. For example you can write you own Web Crawler and index content. This will be part of your search results.
WebCenter uses SES which is an Oracle product. That works as a standard Web Crawler on WebCenter based portal or Spaces. For UCM there is a SES component which has to be installed on UCM. This component exports data from UCM in SES format which SES picks up for its DB.
Hope this helps get you started.
Venkat
Similar Messages
-
Set up Search Service App For SharePoint server 2013 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. This seems also to be a SP set up issue.
Thanks a lot.Using new Search Service App wizard to create SSA is always a success. I could delete existing SSA and recreate it and no problem. It says successful but when I open Search Admin page from CA, it gives me errors as mentioned.
Now I used the following PS script for creating SSA from Max Mercher, but it stays at the last setps in following script:
Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
$IndexLocation = "C:\Search" #Location must be empty, will be deleted during the process!
$SearchAppPoolName = "SSAPool"
$SearchAppPoolAccountName = "mydomain\admin"
$SearchServiceName = "SSA"
$SearchServiceProxyName = "SSA Proxy"
$DatabaseServer = "W12R2DC1"
$DatabaseName = "SSA"
$spAppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
if (!$spAppPool)
$spAppPool = New-SPServiceApplicationPool -Name $SearchAppPoolName -Account $SearchAppPoolAccountName -Verbose
$ServiceApplication = Get-SPEnterpriseSearchServiceApplication -Identity $SearchServiceName -ErrorAction SilentlyContinue
if (!$ServiceApplication)
# process stays at the following step forever, already one hour now.
$ServiceApplication = New-SPEnterpriseSearchServiceApplication -Name $SearchServiceName -ApplicationPool $spAppPool.Name -DatabaseServer $DatabaseServer -DatabaseName $DatabaseName
Account mydomain\admin is an farm managed account, domain admin account, in WG_ADMIN role, It is in all SQL server roles and is DBO. I see search DBs are already on SQL server. From Event viewer, I got following errors in sequence:
(1) Crawler:Content Plugin under source Crawler:Content Plugin
Content Plugin can not be initialized - list of CSS addresses is not set.
(2) Warning for 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)
(3) Error for 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 'cbc5a055-996b-44a7-9cbc-404322f9cfdf'
(4) Error for 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.
(5) Error Shared Services for SharePoint Server Search
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
Above errors keep being generated. Last step for SSA creation stay there forever. Any clue what is really going on? Thanks. -
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 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] -
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 -
Search Service stopped crawling content after previously working
The search service stopped crawling contennt. This was working previously. I tried to stop full crawl and restart. The ULS logs reveals this error repeatedly. when filter on search errors.
Microsoft.Ceres.ContentEngine.SubmitterComponent.ContentSubmissionDecorator : CreateSession() failed with unexpected exception System.ServiceModel.FaultException`1[System.String]: The creator of this fault did not specify a Reason. (Fault Detail is equal
to Specified flow: Microsoft.CrawlerFlow could not be started. Unable to start a flow instance on any of the available nodes.).
Before we dropped the index and or rebuilding the Search Service application has anyone else worked on a similar issue?
Thank you.Hi PSCoan,
From the error message, it seems that the service account running the SharePoint Search Host Controller and the SharePoint search server 15 is missing the following four local policies:
SeAssignPrimaryTokenPrivilege (Replace a process-level token )
SeImpersonatePrivilege (Impersonate a client after authentication)
SeServiceLogonRight (Log on as a service)
SeIncreaseQuotaPrivilege (Adjust memory quotas for a process)
Please go to the Local Group Policy Editor to assign the policies to the service account.
Click Start , type gpedit.msc in the
Start Search box, and then press ENTER .
Expand Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment.
Right click “Replace a process-level token” -> Properties -> Add User or Group.
Right click “Impersonate a client after authentication” -> Properties -> Add User or Group.
Right click “Log on as a service” -> Properties -> Add User or Group.
Right click “Adjust memory quotas for a process” -> Properties -> Add User or Group.
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support -
Another post with a well-known title. Believe me, I know. Here's my setup;
- 1 Server 2012 WFE, SharePoint Server 2013, totally up-to-date, including the september 2014 hotfix
- 1 Server 2012 DB, SQL Server 2012
Installed SP 2013 using PowerShell, with the AutoSPinstaller. Worked like a charm. Got everything up and running, with some tweaking here and there to customize it to fit my situation. Now, I can't get the Search Service Application to work. Must have created,
deleted and recreated it at least 30 times. Used both PowerShell scripts, PowerShell line-by-line, Central Admin, heck, I even went so far as to use the configuration wizzard... No luck. I keep on getting the message that search cannot connect to the machine
that hosts the 'administration component'.
In order to avoid answers that suggest all the things I've already tried, here's a summary of the various scenarios I followed:
Tried both a dedicated application pool as well as the SharePoint Web Services Default
Timer job job-application-server-admin-service is running and not showing errors
IIS 8.0 is installed, so is .NET 4.5 (not the known perp of IIS 7.5 and .NET 4.0)
the get-SPEnterpriseSearchServiceInstance -local returns a healthy, online state
the SPEnterpriseSearchQueryAndSiteSettingsServiceInstance is also running
FireWall is disabled; registry has the BackConnectionHostNames modified with the necessary FQDNs
Accounts used to install and / or run the serviceapp all have sufficient rights - tried a dedicated managed account, SP_2013_SearchSvc, the SP admin account, and even the original Farm account; all to no avail, I keep on getting the error message.
Even tried stsadm to start the server search running - NOTHING WORKS!!!
As you might understand, this is driving me nuts. About to miss my second deadline, and no amount of IISresetting is making this go away. Been stuck on this issue for far too long, now (my searching is measured in days and weeks instead of hours, by now).
Whoever helps me solve this - you will have my eternal gratitude, and a nice bottle of Prosecco. Or whatever's your poison. You need to come get it, though. I´m situated in the Netherlands. Hey, you always meant to visit Amsterdam and see for yourself, right?
Thanks, community, for coming to my rescue!Thanks again - Alas, I've been there. Deleted Search a dozen times, at least, and tried installing it, initially using a PowerShell script (tried several scripts actually, from full-blown total Search Applications with extensive topologies to the most basic
of basics 'please just start without showing me errors'), PowerShell line-by-line to see where things went South, next tried installing through Central Admin (hoping that it was my own stupidity in overlooking things and hoping The System would get it right
for me), and eventually even tried using the config wizzard as a total and utter last resort - Nothing worked.
At first, I found out that removing a Service App needs a *little* bit more work than simply removing it through Central Admin, but by now I can truthfully state that if there's one thing I've become supergood at, it's removing Search Service Applications.Totally.
I will check out the article, though - I realized early on in my SharePoint experience that regardless of what you think you know, there's so much more to find out. I know, that's almost philosophical. That is, my friends, indeed the point I've reached... -
Sharepoint foundation 2013 Search Service Application.
Hi all,
I want to configure search application for sharepoint foundation 2013. I have followed some of the web links.
But did not get success. Can you please provide me the working example of how to configure search application and run the crawl. And make sure the search is working correctly.
Thanks in advance for help.Hi Vishwajeet,
According to your description, my understanding is that you want to configure SharePoint Foundation 2013 Search service application.
In SharePoint Foundation 2013, we cannot add the Search Service to SharePoint Foundation 2013 from the Central Administration GUI after selecting a manual configuration method. It seems that the ONLY way you can add the Search Service to SharePoint Foundation
2013 is by using the SharePoint Configuration Wizard.
More information, please refer to the link:
http://blog.ciaops.com/2012/12/search-service-on-foundation-2013.html
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support -
SharePoint Foundation 2013 search service crawl error
Hi all,
When I try to view the Crawl log of Search Service Application I am getting error something like below:-
I tried to figure out why this is happening but could not find the error details related to above Correlation ID.
Can you please help me & guide me in right direction. I am clueless how to fix this issue. Yesterday it was working fine but somehow it stopped working today and it even does not display the Crawl log. So it has become tough at least for me to
fix it.
Thanks for help.Did you try a using the
Merge-SPLogFile cmdlet to retrieve the events that use this correlation ID?
Merge-SPLogFile -Path ".\example.log" -Correlation "0467d49c-c872-509e-ca23-16445ea822d4"
You can also check out my blog post, An even better way to get the real SharePoint error from the ULS logs which describes the
process for using Merge-SPLogFile
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights -
Sharepoint 2010 search service from C# web service and Powershell - passing credentials to search
Good morning everyone,
I really need your expert help about the following issue. I ve developed a web service in C#. Its core code has a Powershell script inside which makes a call to SharePoint 2010 search service to make some search queries, and returns some URL of some files.
In Powershell code I make connection to SharePoint search service using the Farm Admin account. This system works, but given results are not filetered by the user using the web service (I remember you I m using the Farm admin account in PS code)
How can I use user account to make some queries ? How can I filter search results by user ? In Powershell code I put username and password of Farm Admin account and I know them because I m the farm administrator, but
what about if I want to pass Powershell code some other user credentials ? Of course I cannot know his credential .. Can I do it , in which way ?
Any help is really appreciated !
GaeHi Gae, if you are using web services, you shouldn't need to add a SharePoint DLL to your project. I would advise against using C# -> PS -> Web Service Call -> PS -> C# if you could go straight C# -> Web Service -> C#.
Anyways, back to the matter at hand. Do you know what type of authentication your SharePoint server is running? Is it direct NTLM, NTLM over Kerberos, Claims, or something different?
The following article provides the various types of impersonation available in SharePoint:
http://extreme-sharepoint.com/2012/05/30/impersonation-elevation-of-privileges/
Dimitri Ayrapetov (MCSE: SharePoint) -
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 LokaPlease 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. -
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 -
Your search cannot be completed because no search service is available- SP2013
Hi,
We have an application page, in which we need to retrieve the search results in SP2013. However, the query always returns the error "your search cannot be completed because no search service is available". Please find the code below.
using (SPSite site = new SPSite("http://server"))
using (SPWeb web = site.OpenWeb())
Microsoft.SharePoint.Search.Query.FullTextSqlQuery kq = new FullTextSqlQuery(site);
// KeywordQuery kq = new KeywordQuery(site);
//KeywordQuery kq = new KeywordQuery(site);
kq.SourceId = new Guid(SourceID_Value);
kq.QueryText = keyword;
kq.RowLimit = 100;
kq.AuthenticationType = QueryAuthenticationType.NtAuthenticatedQuery;
ResultTableCollection resultTables = new SearchExecutor().ExecuteQuery(kq);
ResultTable resultTableFinal = new ResultTable();
resultTableFinal = resultTables[ResultType.RelevantResults];
However, the same code works in a console application executed on the same server. Please let know if you have faced this issue and the solution.
Sreeharsha Alagani | MCTS Sharepoint 2010 |
Linkedin | BlogNot sure if it's typo with your post or the code, the url in the first line doesn't contain a close quote.
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights -
Hi all. I have been searching for days for a solution to a problem I am having with SP2013 Enterprise edition.
We recently upgraded from SP2013 Foundation to SP2013 Enterprise. After the upgrade, the search services are no longer working and we are receiving many application log entries indicating the following:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ea2019ef-bb9e-4efe-85ee-5d2307406f31).
Reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Technical Support Details:
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
as well as:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ea2019ef-bb9e-4efe-85ee-5d2307406f31).
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)
I have tried to remove the search service application and recreate it, and even though the SharePoint Central Administration states that it was created successfully, I am still getting the same errors in the log. If I go to the Search Service Application
Search Administration page, the "System Status" shows the following message:
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '0359af35-0982-4ede-8838-b1d390e915bf' in search application 'Search Service Application' is in a good state and
try again
Additionally, under the "Search Application Topology" section, it states "Unable to retrieve topology component health states. This may be because the admin component is not up and running" which I assume is normal if the admin is not
running.
Does anyone know how I can resolve this problem?
Thanks!Hi Joaquin,
According to your description, the error occurred when you re-created the Search Service Application.
Based on the error message, I recommend to verify the things below:
1. Check if the association between the Search Service Application proxy and the web application is configured.
Please go to Central Administration > Application Management > Configured service application associations > Click Default to see if the Search Service application is checked.
2. Change the app pool for the Search Service Application to SharePoint Web Services Default in the properties of the Search Service Application.
Please go to Central Administration > Application Management > Manage service applications > Highlight the Search Service Application > Click Properties in the ribbon > Change
the two app pool to SharePoint Web Services Default: App Pool For Search Admin Web Service and Application Pool for Search Query and Site Settings Web Service.
3. Run PS command to check if the search admin timer job is enabled: Get-SPTimerJob
job-application-server-admin-service | fl. If it is not enabled, use PS command to enabled it and then reset Internet Information Services: Enable-SPTimerJob job-application-server-admin-service.
Best regards.
Thanks
Victoria Xia
TechNet Community Support -
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
Maybe you are looking for
-
The other day my iMesasges stopped working so I plugged my phone into my laptop (windows) to update through iTunes. I tried to update it, but when the update was almost done an error message popped up. Now the phone will only turn on with the plug in
-
Mac Pro 4,1 kernel panic - restarts on its own
I have a Mac Pro 4,1 that will not finish the start up process It kernel panics at the end of the process. It will then do a restart on its own and kernel panics again. What's the best way to figure out what's wrong with it? HDs? Processor ? Or th
-
Exporting slideshows successful but no audio
I exported a slideshows from iPhoto 09, but the resulting file has no audio in it. The problem started to occur after I downloaded and run the latest iPhoto update (version 8.0.4). The slideshows itself can play well (with audio) during "preview" and
-
Problem with PDF forms not having language property--not passing accessibility tests.
Why doesn't LiveCycle Designer pass the language region to the PDF language property? Anyone know how to fix this problem?
-
Is it possible to lock individual folders in snow leopard?
can we lock each folder and set different passwords to them in snow leopard? - i have been searching the system and still cant seem to get it to work - there is an option for "lock" in the get info section, but when i hit the action preference on the