Unable to delete search service application

We accidentally deleted the three databases related to Sharepoint Search.  Luckily, this was done on the test server.  So now I have the search service application but no related databases.  I want to delete this search service application
and recreate it but it won't let me do it because during deletion it's looking for these databases and I get an error message that it can't find them.  Is there any way to either recreate these databases or force deletion of this Search Service application?
thanks,

Hi,
If you have the backups for these databases related to SharePoint Search, you can try to restore them.
If you donot, you need to use STSADM.EXE command as below to delete the corrupted search service application:
Stsadm -o deleteconfigurationobject -id %GUID%
Reference:
http://blog.greenbrain.de/2013/11/removing-corrupted-search-service-from.html
http://blog.isaacblum.com/2011/08/08/force-delete-search-any-service-application-sharepoint-2010/
Best Regards,
Eric
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]

Similar Messages

  • Unable to create Search Service Application

    Hi All,
    When I tried to create Search Service Application in Central Admin, I'm getting Error on creation. The below is the detail error.
    Errors were encountered during the configuration of the Search Service Application.
    Microsoft.SharePoint.SPException: The timer job completed, but failed on one or more machines in the farm. at Microsoft.SharePoint.Administration.SPTimerJobAsyncResult.End()
    at Microsoft.SharePoint.Administration.SPServiceApplication.ProvisionInstances() at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Provision() at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Provision() at Microsoft.Office.Server.Search.Administration.SearchConfigWizard.b__22()
    at Microsoft.Office.Server.Search.Administration.SearchAdminUtils.UpdateIgnoreSPUpdatedConcurrencyException(String description, SearchAdminUtilsUpdateDelegate updateDelegate, SearchAdminUtilsRefreshObjectDelegate refreshObjectDelegate) at Microsoft.Office.Server.Search.Administration.SearchConfigWizard.CreateSearchApp()
    at Microsoft.Office.Server.Search.Administration.SearchConfigWizard.ProvisionSearchServiceApplication() at Microsoft.Office.Server.Search.Administration.SearchConfigurationJobDefinition.ExecuteTimerJob()
    5/2/2011 11:49:08 AM
    Could any body guide, where I'm missing?.
    Thanks
    When I looked in EventViewer for more error details, the below is the error message.
    Access to 'Global\Microsoft.SharePoint.SPIisProvisioningLock' is denied
    any ideas?.

    It doesnt work.
    I Stopped the search service and then try to receate the Search sercie application with the gui. In the log I get the same error.
    SearchConfigWizardFinish page failed with exception. System.InvalidCastException: Unable to cast COM object of type 'Microsoft.Office.Server.Search.Administration.MSSITLB.CGatheringManagerClass' to interface type 'Microsoft.Office.Server.Search.Administration.MSSITLB.IGatherManagerAdmin3'.
    This operation failed because the QueryInterface call on the COM component for the interface with IID '{0FF1CE14-013A-0000-0000-000000000000}' failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)).   
    Server stack trace:      at Microsoft.Office.Server.Search.Administration.Gatherer.get_AdminObject()     at Microsoft.Office.Server.Search.Administration.Gatherer.ProvisionGlobalProperties()    
    at Microsoft.Office.Server.Search.Administration.Gatherer.Provision()     at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Provision()     at Microsoft.Office.Server.Search.Administration.SearchAdminUtils.DeployLocalServiceInstance[T](T
    localSearchServiceInstance)     at Microsoft.Office.Server.Search.Administration.SearchConfigurationJobDefinition.Create(AbstractSearchConfigWizard wizardOM)     at Microsoft.Office.Server.Search.Internal.UI.SearchConfigWizardFinish.ExecuteConfigurationTimerJob(SPLongOperationState
    longOperationState, String& strRedirectPage)     at Microsoft.SharePoint.SPStatefulLongOperation.SetThreadCultureAndRun(RunStatefulOperation runOperation, SPLongOperationState state, CultureInfo culture, CultureInfo uICulture)    
    at Microsoft.SharePoint.SPStatefulLongOperation.<>c__DisplayClass6.<Run>b__0(Object state)     at Microsoft.SharePoint.Utilities.SPThreadPool.WaitCallbackWrapper(Object state)     at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr
    md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)     at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)    Exception
    rethrown at [0]:      at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)     at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData&
    msgData)     at System.Threading.WaitCallback.EndInvoke(IAsyncResult result)     at Microsoft.SharePoint.Utilities.SPThreadPool.RunAsyncWorkItem(ImpersonatedCallbackParam param, TimerCallback timerCallback, Object timerState,
    Int32 timerPeriod)     at Microsoft.SharePoint.Utilities.SPThreadPool.RunAsyncWorkItemWithImpersonation(WaitCallback workItemCallback, Object workItemState, TimerCallback timerCallback, Object timerState, Int32 timerPeriod)    
    at Microsoft.SharePoint.SPStatefulLongOperation.Run(RunStatefulOperation runOperation)     at Microsoft.Office.Server.Search.Internal.UI.SearchConfigWizardFinish.<>c__DisplayClass2.<Commit>b__0(SPStatefulLongOperation longOperation)

  • Unable to remove search service application - SP2010

    I have a SSA that unfortunately lost its crawl database.  It's not a critical DB so I then tried to remove it via Central Admin.  The remove dialog appeared and I checked "remove data".  The dialog sat for at least half an hour and at that
    point I just killed it.  I then tried to remove using the Powershell cmdlet Remove-SPEnterpriseSearchServiceApplication, which basically behaves the same way.  I say "Yes", but the command never returns.  
    Is there another way to forcibly remove an application?

    Solution:
    “id retrieved from search application link” (if you hoover over it you'll see it)
    So you have to fill in the quotes the GUID from the search application. If it's 97s2fgd9-453k-3423-f334-8r78jd3bv2t6 you have to give:
    Reference to this post:
    http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/88f7998f-4a88-4928-ba59-e76d7f6afcdc 
    Alpesh Nakar's Blog
    Alpesh
    Just SharePoint
    Just SharePoint Updates
    SharePoint Conference Southeast Asia
    Oct 26-27 2010 Contributing Author
    SharePoint 2010 Unleashed
    MCTS: SharePoint 2010 Configuration
    MCITP: SharePoint 2010 Administrator

  • Showing search service application status error in SharePoint 2013

    Hi All,
    I'm unable to configure search service application in SharePoint 2013.When I go to CA > manage services , it is showing below issue.
    On the place of started or stopped it shows 'error'. I'm using admin credentials here.
    Then, when click on search service application, it shows details screen as follows
    Thank you

    HI,I would recommend to re-create the service application.please check the below links that gives you the solution of the issue.
    http://expertsharepoint.blogspot.de/2014/07/the-search-service-is-not-able-to_19.html
    http://expertsharepoint.blogspot.de/2014/07/the-search-service-is-not-able-to.html
    Anil Avula[Partner,MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

  • Error "Unable to load word breaker for locale 0. Error code 8007007e." with search service application.

    I recreate the Search service application and the default Content source stayning in the 'Recovering' status.
    The log give multiple error 'Unable to load word breaker for locale 0. Error code 8007007e.'
    The default language is English and the reference in registry for word breaker dll is naturallanguage1.dll but I found only the naturallanguage6.dll.

    Hi,
    For your issue, check your current language settings and ensure that search supports the current language.
    On the SharePoint Server open Registry Editor (Start -> type “Regedit” and hit enter). 
    Point to : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeServer\14.0\Search\Setup\ContentIndexCommon\LanguageResources\Default\English
    Under the registry key for each of the languages there is a value called StemmerDLLPath and WBDLLPathOverride
    Updated the registry entry with NATURA~1.dll to NATURA~2.dll
    Point to Start -> Administrative Tools -> Services, right click on SharePoint Server Search 14 and click on Restart.
    Performed a Full Crawl and wait for the Full Crawl to complete and try searching again.
    For more detailed information, refer to the following blogs:
    http://blog.ithinksharepoint.com/2008/04/20/a-word-breaker-was-not-found-for-the-given-language-error-when-crawling-content/
    http://www.sharepoint2013.me/Blog/Post/175/Word-breakers-in-SharePoint-2013
    Best Regards,
    Lisa Chen
    Lisa Chen
    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.

  • The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component 'GUID′ in search application 'Search Service Application' is in a good state and try again.

    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 Search Service Application Restore Is Failing

    Issue:
    When performing a Search Service restore with the CA UI, the restore is failing. The backup was generated from a Full level backup that is run nightly from the cmdlet Backup-SPFarm.  The Farm is running SharePoint 2013 SP1, Windows Server 2012 And SQL
    Server 11.0.3128. Both Production and the test environment have the same topology.
    The sprestore.log file shows the following error message:
    [12/17/2014 12:37:51 PM] Verbose: [Search Service Application] The default endpoint id for this application is 'b8b92dc6-38b3-49bf-90bc-d9ea64dcf928'.
    [12/17/2014 12:37:51 PM] Verbose: [Search Service Application] Re-parented endpoint 'b8b92dc6-38b3-49bf-90bc-d9ea64dcf928' to this application.
    [12/17/2014 12:37:51 PM] Verbose: [Search Service Application] The default endpoint has been found and set.  NOTE: The id of the default endpoint will be different than specified in the logs if
    the restore mode is not 'overwrite'.
    [12/17/2014 12:37:51 PM] Verbose: [Search Service Application] Re-parented endpoint 'bb456994-47ac-4bad-9197-9a4d5b39bf5c' to this application.
    [12/17/2014 12:37:55 PM] FatalError: Object Search Service Application failed in event OnPostRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
            SqlException: The database principal owns a database role and cannot be dropped.
    User does not have permission to perform this action.
    [12/17/2014 12:37:55 PM] Debug:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj,
    Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean
    asyncWrite, SqlDataReader ds)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout,
    Task& task, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)
       at Microsoft.Office.Server.Data.SqlDatabaseManager.GrantAccess(String user)
       at Microsoft.Office.Server.Search.Administration.SearchDatabase.GrantAccess(String username, String role)
       at Microsoft.Office.Server.Search.Administration.SearchDatabase.SynchronizeAccessRules(SearchServiceApplication searchApp)
       at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.SynchronizeDatabases()
       at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Provision()
       at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Microsoft.SharePoint.Administration.Backup.IBackupRestore.OnPostRestore(Object sender, SPRestoreInformation info)
    A SQL Profile was run beginning at 12/18/2014 11:11.
    A SQL exception can be found at 11:20:03 with the error:
                   The database principal owns a database role and cannot be dropped.
    The issue has to do with the SQL statement just prior to the exception:
    declare @p4 int
    set @p4=NULL
    declare @p5 int
    set @p5=NULL
    exec sp_executesql N'declare @db_user_name sysname
    select @db_user_name = name from dbo.sysusers where sid = SUSER_SID(@user_name) and hasdbaccess = 1
    if (@db_user_name is null)
    begin
    if exists(select * from dbo.sysusers where name = @user_name)
    exec @revoke_result = sp_revokedbaccess @user_name
    exec @grant_result = sp_grantdbaccess @user_name, @db_user_name output
    end',N'@user_name nvarchar(128),@revoke_result int output,@grant_result int output',@user_name=N'----\sp2013uatfarmacct',@revoke_result=@p4 output,@grant_result=@p5 output
    select @p4, @p5
    I highlighted the row in red causing the issue. For some reason SharePoint during the Search Restore process try’s to delete the user “------\sp2013uatfarmacct” from the database Search_Service_Application_DB_60bb9889222841aa94f59aed71349a6b
    And re-add them again.  But the reason for the failure is because the user “------\sp2013uatfarmacct” is the owner of the database role “SPSearchDBAdmin”, so it cant.
    I checked all other Service databases that contain the role SPSearchDBAdmin and they all correctly have the owner as dbo
    NOT ------\sp2013uatfarmacct.
    Further checking the SQL trace log a SQL batch is executed at 12/18/2014 11:19:59.790 that states the following:
    -- Drop existing role members
    IF  EXISTS (SELECT * FROM sys.database_principals WHERE name = N'SPSearchDBAdmin' AND type = 'R')
    Begin
        DECLARE @RoleMemberName sysname
        DECLARE Member_Cursor CURSOR FOR
        SELECT [name]
        FROM sys.database_principals
        WHERE
            principal_id IN
                SELECT member_principal_id
                from sys.database_role_members
                where role_principal_id in (
                select principal_id
                FROM sys.database_principals where [name] = N'SPSearchDBAdmin'  AND type = 'R' ))
        OPEN Member_Cursor;
        FETCH NEXT FROM Member_Cursor
        into @RoleMemberName
        WHILE @@FETCH_STATUS = 0
        BEGIN
            exec sp_droprolemember @rolename=N'SPSearchDBAdmin', @membername= @RoleMemberName
            FETCH NEXT FROM Member_Cursor
            into @RoleMemberName
        END;
        CLOSE Member_Cursor;
        DEALLOCATE Member_Cursor;
    End
    -- Drop/Create role
    IF  EXISTS (SELECT * FROM sys.database_principals WHERE name = N'SPSearchDBAdmin' AND type = 'R')
    DROP ROLE [SPSearchDBAdmin]
    CREATE ROLE [SPSearchDBAdmin]
    I highlighted the statement in red that is eventually causing the SP restore to fail. For some unknown reason to me when this statement is executed the new ROLE SPSearchDBAdmin owner is -----\sp2013uatfarmacct
    instead of dbo.
    As a test I executed via SQL Management Studio “CREATE ROLE [SPSearchDBAdmin]” and it correctly created the owner as dbo.
    So the problem and my question is why when the SP Search Service is restored is the ROLE SPSearchDBAdmin owner being set to “-----\ sp2013uatfarmacct”, which in turn seems to be causing the restore failure?

    Hi!
    I believe it is trying to delete a user who owns the schema of the database. You can try changing the schema owner to some other user like "dbo", and then drop the first user.
    Below are a few links that can help you with much more details.
    http://blogs.technet.com/b/mdegre/archive/2010/12/19/the-database-principal-owns-a-schema-in-the-database-and-cannot-be-dropped.aspx
    http://littletalk.wordpress.com/2009/11/09/fix-for-the-database-principal-owns-a-schema-in-the-database-and-cannot-be-dropped-error-in-sql-server-2005/
    http://dotnetgun.blogspot.com/2011/02/database-principal-owns-schema-in.html
    Thanks,
    Owens
    Owens G. Jesse

  • Search Service Application problems after upgrading from Foundation to Enterprise edition of SharePoint 2013

    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

  • Problem rename sharepoint 2010 search service application admin database

    Hi all,
    i have a problem that hopefully someone has an answer to.  i am not too familiar with sharepoint so please excuse my ignorance.
    we have sharepoint 2010 on a windows 2008r2 server.  everything seems to work fine.  but as you know, the default database names are horrendous.  i have managed to rename all of them, except for the "search service application" admin
    database.
    the default is: Search_Service_Application_DB_<guid>
    the other 2 databases (crawl and property) were renamed without a problem.
    we are following the article from technet on how to rename the search service admin db (http://technet.microsoft.com/en-nz/library/ff851878%28en-us%29.aspx).  it says to enter the following command:
    $searchapp | Set-SPEnterpriseSearchServiceApplication -DatabaseName "new database name" -DatabaseServer "dbserver"
    however, i get an error about identity being null.  no big deal, i add the -Identity switch and the name of my search service application.  but the real problem comes the error it throws:
    Set-SPEnterpriseSearchServiceApplication : The requested database move was aborted as the associated search application is not paused.
    At line:1 char:54
    + $searchapp | Set-SPEnterpriseSearchServiceApplication <<<<  -Identity "Search Service Application" -DatabaseName "SharePoint2010_Search_Service_Application_DB" -DatabaseServer "dbserver"
        + CategoryInfo          : InvalidData: (Microsoft.Offic...viceApplication:
       SetSearchServiceApplication) [Set-SPEnterpriseSearchServiceApplication], I
      nvalidOperationException
        + FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.SetSearchS
       erviceApplication
    when i look at the crawling content sources, i see "Local SharePoint Sites" and it's status is Idle.  i even looked at this article on how to pause the search to no avail.  (http://technet.microsoft.com/en-us/library/ee808864.aspx)
    does someone know how i can rename my Search Service Applcation Admin database properly?  or at least "pause" that service so i can rename it?
    thank you all in advanced

    If you want to have no guids for your search admin db, i recommend you check out this script :)
    just delete your search service application (assuming you have just started)
    Alpesh Nakar's Blog
    Alpesh
    Just SharePoint Just SharePoint Updates
    SharePoint Conference Southeast Asia
    Oct 26-27 2010 Contributing Author
    SharePoint 2010 Unleashed
    MCTS: SharePoint 2010 Configuration
    MCITP: SharePoint 2010 Administrator

  • Unable to open search service content sources from SharePoint

    HI
    unable to open search service content sources from SharePoint , I got this error in search server event viewer .
    A database error occurred. Source: Microsoft SQL Server Native Client 10.0 Code: 1205 occurred 1 time(s) Description: Transaction (Process ID 66) was deadlocked
    on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
    Context: Application 'SP_SearchApp'
    adil

    Hi,
    Based on the error message, I recommend to stop all the crawl process in SharePoint search service application by using PowerShell and then check the results:
    http://blogs.technet.com/b/heyscriptingguy/archive/2010/09/28/how-to-use-sharepoint-2010-windows-powershell-cmdlets-to-manage-search-crawls.aspx
    The deadlock error will occurs when there are too many overlapping crawls, so I recommend to schedule the crawl to not overlap in SharePoint and add more crawl components if needed.
    http://blogs.msdn.com/b/sharepoint_strategery/archive/2014/02/10/sharepoint-search-and-deadlocks-in-sql-server.aspx
    If above cannot work, please also check the ULS log and SQL server for detailed error messages.
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • Getting error while editing content source of search service application

    Hi,
    when i edit the content source of SharePoint Search Service Application and click on OK Button then i get the following error.
    Error it gives : An item with the same key has already been added.
    and when i check it in ULS log it gives this.
    Application error when access /_admin/search/editcontentsource.aspx, Error=An
    item with the same key has already been added.  Server stack trace:    
     at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version,
    FaultConverter faultConverter)   
     at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)   
     at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs,
    TimeSpan timeout)   
     at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)   
     at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown
    at [0]:    
     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)
    System.ServiceModel.FaultException`1[[System.ServiceModel.ExceptionDetail, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]:
    An item with the same key has already been added.   Server stack trace:    
     at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version,
    FaultConverter faultConverter)   
     at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)   
     at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs,
    TimeSpan timeout)   
     at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)   
     at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown
    at [0]:    
     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)
    Getting Error Message for Exception System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: An
    item with the same key has already been added. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.ArgumentException: An
    item with the same key has already been added.  
     at Microsoft.Office.Server.Search.Administration.SearchApi.WriteAndReturnVersion(CodeToRun`1 remoteCode, VoidCodeToRun localCode, Int32 versionIn)   
     at SyncInvokeEditContentSource(Object , Object[] , Object[] )   
     at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)   
     at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)   
     at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)   
     at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc&
    rpc)   
     at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).
    Can anyone please help me, how can i resolved this issue.i am stuck :(
    Thanks in advance
    Muhammad Luqman

    Also tried with this code, but no succeed.
    Add-PSSnapin "Microsoft.SharePoint.PowerShell"
    $searchapp = Get-SPEnterpriseSearchServiceApplication "Search Service Application"
    $StartAddresses = "http://insite"
    $cs = Get-SPEnterpriseSearchCrawlContentSource -SearchApplication $searchapp -identity "Local SharePoint sites"
    $cs | Set-SPEnterpriseSearchCrawlContentSource –StartAddresses $StartAddresses
    I have now only single content source and all others are removed now but still getting same error.
    Muhammad Luqman

  • 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 Search Service Application isn't crawling.

    Hi all,
    I am new to Sharepoint 2013 and I do not know how to troubleshoot the issue of sharepoint search service.
    My issue is that the sharepoint search service application is not crawling. How can I know the reason of this error and how to fix this.
    Please help me.
    Thanks.

    Hi Vishwajeet,
    if you facing any problem in search you can Use the crawl log and crawl-health reports to diagnose problems
    which is best recommended practices  from Microsoft.
    http://technet.microsoft.com/en-us/library/dn535606%28v=office.15%29.aspx
    for View Search diagnostic   and also check all the search related service whether its running or not
    http://technet.microsoft.com/en-us/library/jj219611%28v=office.15%29.aspx
    Please Mark as Answer and Vote me if it help to resolve your issue

  • Create SharePoint 2010 Search Service Application Using Powershell

    Hi Team,
    Could you please assist me in completing the search service application for
    two server using powershell. Both the servers will be running all the component
    Version SharePoint 2010
    # 1.Setting up some initial variables.
    write-host 1.Setting up some initial variables.
    $SSAName = "Search Service Application"
    $SVCAcct = "Domain\ServiceAccount"
    $SearchAppPoolName ="DefaultAppPool"
    $SSI = get-spenterprisesearchserviceinstance -local
    $err = $null
    $SSADBName="Search_AdminDB"
    $SSADBServer="DBServer"
    $host1="Server1"
    $host2="Server2"
    # Start Services search services for SSI
    write-host Start Services search services for SSI
    Start-SPEnterpriseSearchServiceInstance -Identity $SSI
    # 2.Create an Application Pool.
    write-host 2.Create an Application Pool.
    #$AppPool = new-SPServiceApplicationPool -name $SSAName"-AppPool" -account $SVCAcct
    $AppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
    # 3.Create the SearchApplication and set it to a variable
    write-host 3.Create the SearchApplication and set it to a variable
    $SearchApp = New-SPEnterpriseSearchServiceApplication -DatabaseServer $SSADBServer -Name $SSAName -applicationpool $AppPool -databasename $SSADBName
    #4 Create search service application proxy
    write-host 4 Create search service application proxy
    $SSAProxy = new-spenterprisesearchserviceapplicationproxy -name $SSAName"ApplicationProxy" -Uri $SearchApp.Uri.AbsoluteURI
    # 5.Provision Search Admin Component.
    write-host 5.Provision Search Admin Component.
    set-SPenterprisesearchadministrationcomponent -searchapplication $SearchApp -searchserviceinstance $SSI
    # 6.Create a new Crawl Topology.
    write-host 6.Create a new Crawl Topology.
    $CrawlTopo = $SearchApp | New-SPEnterpriseSearchCrawlTopology
    New-SPEnterpriseSearchCrawlComponent -SearchTopology $newTopology -SearchServiceInstance $hostA
    Source:blog.MSDN Author- Russ Maxwell
    Thanks Basva

    Could you please assist me in completing the search service application for
    two server using powershell. Both the servers will be running all the component 
    Hi Basva,
    Do you want to provision two search service applications in single farm?
    Commonly, only one search service application is needed in a farm for Search function.
    Here are articles for detail information about how to provision search service application using powershell:
    http://blogs.msdn.com/b/jjameson/archive/2011/02/28/powershell-script-to-configure-search-in-sharepoint-server-2010.aspx
    http://blogs.msdn.com/b/russmax/archive/2009/10/20/sharepoint-2010-configuring-search-service-application-using-powershell.aspx
    Regards,
    Rebecca Tu
    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]

Maybe you are looking for