search service and document search

We kept search service unchecked while running Services configuration wizard after sharepoint was first setup so currentky Sharepoint search  is in disabled state.

However  we now  would like to use only search document feature in libraries. which is not working .

is these 2 are related what will be best way to now enable serach aned config=ure so as it doesnt create more load /resource usage or  shaould we add new server in farm and run search service there?

December 19th, 2013 1:22pm

Hello,

What version of sharepoint you are using?

If you have not created service service yet then please create it otherwise you won't be able to search documents.

http://technet.microsoft.com/en-us/library/gg502597%28v=office.14%29.aspx

Correct me if i misunderstood you

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2013 1:44pm

You will need to set search up in full to get any search facilities. Your farm is, from memory, a 2013 farm rather than 2010 so this is probably in the wrong forum.

Depending on the size, load and use of your SharePoint farm you may need to scale this out onto another server but we don't have the information to advise on that at the moment.

December 19th, 2013 1:49pm

 thanks

so this means even if the search document ( not text/strings) we shall need search service enabled.

We are using Sharepoint 2013.

Free Windows Admin Tool Kit Click here and download it now
December 19th, 2013 1:52pm

looks like I posted in wrong forum
December 19th, 2013 1:52pm

Yes, as Alex already mentioned, you will need to configure SharePoint 2013 search for any search functionalit
Free Windows Admin Tool Kit Click here and download it now
December 19th, 2013 2:00pm

thanks again

Since service is in disbaled state so dio i need to enable it manually or go through steps as per Some MS Article.

December 19th, 2013 2:07pm

Yes, and here is that article: http://technet.microsoft.com/en-us/library/gg502597.aspx
Free Windows Admin Tool Kit Click here and download it now
December 19th, 2013 2:10pm

we added search srevice application today after RAM upgrade

though Central admin showed search service application added succcessfully and we founda db also created at  DB server , however we are finding following errors whcih is worrying ... Specially tokenservice and claimsauthentication warnings

we enabled serach host controller servoice. selected service account. The in Manage service application created new search service application and selected new apppool setting.

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          2/25/2014 6:00:01 AM
Event ID:      2138
Task Category: Health
Level:         Warning
Keywords:      
User:        spfarmacc

Description:
The SharePoint Health Analyzer detected a condition requiring your attention.  The Security Token Service is not available.
The Security Token Service is not issuing tokens. The service could be malfunctioning or in a bad state.
Administrator should try to restart the Security Token Service on the boxes where it is not issuing tokens. If problem persists, further troubleshooting may be available in the KB article. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=160531".

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
    <EventID>2138</EventID>
    <Version>15</Version>
    <Level>3</Level>
    <Task>8</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-25T12:00:01.092530500Z" />
    <EventRecordID>131912</EventRecordID>
    <Correlation ActivityID="{75B1779C-6E20-60CD-507E-9FFD4DAEDB0A}" />
    <Execution ProcessID="892" ThreadID="3400" />
    <Channel>Application</Channel>

    <Security UserID="S-1-5-21-521425033-3276028114-1354584634-1108" />
  </System>
  <EventData>
    <Data Name="string0">The Security Token Service is not available.
The Security Token Service is not issuing tokens. The service could be malfunctioning or in a bad state.
Administrator should try to restart the Security Token Service on the boxes where it is not issuing tokens. If problem persists, further troubleshooting may be available in the KB article. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=160531".
</Data>
  </EventData>
</Event>

--

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Server
Date:          2/25/2014 5:56:25 AM
Event ID:      2159
Task Category: Unified Logging Service
Level:         Error
Keywords:      
User:       \spservices
Computer:
Description:
Event 2548 (SharePoint Server Search) of severity 'Error' occurred 847 more time(s) and was suppressed in the event log

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          2/25/2014 5:51:14 AM
Event ID:      5586
Task Category: Database
Level:         Error
Keywords:      
User:       spfarmacc
Computer: 
Description:
Unknown SQL Exception 2812 occurred. Additional error information from SQL Server is included below.

Could not find stored procedure 'dbo.Search_GetRecentStats'.
Event Xml:

---

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          2/25/2014 5:53:55 AM
Event ID:      8306
Task Category: Claims Authentication
Level:         Error
Keywords:      
User:       spfarmacc
Computer:
Description:
An exception occurred when trying to issue security token: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs..
Event Xml:

February 25th, 2014 7:08am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics