none
Event ID: 6482 Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance

    Question

  • Event Type: Error
    Event Source: Office SharePoint Server
    Event Category: Office Server Shared Services
    Event ID: 6482
    Date: 4/14/2012
    Time: 1:02:32 PM
    User: N/A
    Computer: CORP-SUR-IDX02
    Description:
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (251114cc-e3a4-4752-ba6a-e9839194ebca).

    Reason: Could not find stored procedure 'dbo.proc_MSS_PropagationGetQueryServers'.

    Techinal Support Details:
    System.Data.SqlClient.SqlException: Could not find stored procedure 'dbo.proc_MSS_PropagationGetQueryServers'.
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.SynchronizeDefaultContentSource(IDictionary applications)
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

    MOSS2007 farm

    Wednesday, April 25, 2012 4:48 PM

All replies

  • Hi Sayuhail,

    From the error messages, it seems the stored procedure(SP) 'dbo.proc_MSS_PropagationGetQueryServers' is missing from the WSS_Search content database, or the Shared Service Provider(SSP)'s account does not have the sufficient privilege to access the SP. For the missing issue, it might be caused by incompleted upgrade.

    So, if this issue happens after an upgrade, please download and apply the latest hotfixes, and re-run the SharePoint Products Configration Wizard to fix the issue.
    If the actions above are done, we can reset the search index and do a full crawl to try to fix the issue. Or, please rebuild the SSP to fix it.

    For the information about the latest hotfixes, please see:
    http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb735839

    Thanks,
    Jinchun Chen


    Jinchun Chen
    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 tnmff AT microsoft.com(Please replace AT with @)

    Friday, April 27, 2012 3:02 AM
    Moderator
  • Recreate SSP.

    Change association amd make new SSP as default SSP

    Delete Old SSP


    Regards, Vishwas

    Tuesday, May 01, 2012 8:06 AM
  • Hi

    I will try and update.

    Thanks,

    Suhail

    Wednesday, May 02, 2012 4:36 PM
  • I cant apply this solution since its our production farm.
    Wednesday, May 02, 2012 4:36 PM
  • Hi Sayuhail,

    In case it is in production farm and we can't apply the solution I provided early, could you please help to check whether the SP 'dbo.proc_MSS_PropagationGetQueryServers'  is existing in the SQL Server(in Search Content database)?

    If it is not there, please try to create it manually:
    CREATE PROCEDURE dbo.proc_MSS_PropagationGetQueryServers
    AS
        DECLARE @Temp table(
            ServerID int,
            SearchServerName nvarchar(31),
            IndexDirectory nvarchar(260),
            MachineStatus int,
            LastPropagationTime datetime,
            PropagationStatus int
        )
        INSERT INTO
            @Temp
        SELECT
            SearchServerID,
            SearchServerName,
            IndexDirectory,
            MachineStatus,
            LastPropagationTime,
            1
        AS
            PropagationStatus
        FROM
            dbo.MSSPropagationSearchServerTable
        UPDATE
            @Temp
        SET
            PropagationStatus = 0
        WHERE
            NOT EXISTS (SELECT * FROM dbo.MSSPropagationSearchServerReady AS R WHERE ServerID = R.SearchServerID) AND
            (1 < DATEDIFF(m, LastPropagationTime, GETUTCDATE()) OR
            30 < DATEDIFF(s, LastPropagationTime, GETUTCDATE()))
        CREATE TABLE #UnresponsiveQueryServers (
            ServerID int )
        INSERT #UnresponsiveQueryServers   
        EXEC
            dbo.proc_MSS_PropagationGetUnresponsiveQueryServers
        UPDATE
            @Temp
        SET
            PropagationStatus = 3
        WHERE
            ServerID IN ( SELECT ServerID FROM #UnresponsiveQueryServers )
        UPDATE
            @Temp
        SET
            PropagationStatus = 2
        WHERE
            MachineStatus = 0 OR
            MachineStatus = 1 OR
            MachineStatus = 2
        SELECT
            SearchServerName,
            IndexDirectory,
            MachineStatus,
            PropagationStatus
        FROM
            @Temp

     


    Thanks,
    Jinchun Chen


    Jinchun Chen
    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 tnmff AT microsoft.com(Please replace AT with @)

    Thursday, May 03, 2012 11:04 AM
    Moderator
  • I'm not sure but creating a store procedure manually leads to database editing and would make your database unsupported by Microsoft. http://support.microsoft.com/kb/841057 ... Such errors might come up as a result of SQL server version. May be it's not patched with latest build. Recreating SSP would be less time consuming if you do not have crawl rules, BDC etc

    Regards, Vishwas

    Friday, May 04, 2012 11:28 AM
  • Thank you Vishwas for pointing me that out.

    Yes, recreating the SSP would be the better and easy way to fix the issue. But Sayuhail mentioned he can't do that as it is in a production environment.

    Trying to create the stored produce is just a step to narrow down the issue. Please do a backup of the database before performing the action.


    Jinchun Chen
    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 tnmff AT microsoft.com(Please replace AT with @)

    Tuesday, May 08, 2012 2:35 AM
    Moderator
  • Hi,

    Thank you all for your suggestion, however the issue is solved automatically.

    Tuesday, July 10, 2012 11:59 AM
  • i have search a blog which is 

    http://www.no-dumping.com/2011/03/23/sharepoint-error-event-id-6482/

    Thanks for his count..

    Affected software: Windows SharePoint Server 3.0

    Type : Error
    Date : 3/23/2011
    Time : 8:52:17 AM
    Event : 6482
    Source : Office SharePoint Server
    Category : Office Server Shared Services
    User : N/A
    Computer : xxxxxxxx
    Description:
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (94fda143-13d5-4bd2-bab1-d23b38f4ad95).
    Reason: The current operation timed-out after 3600 seconds
    Techinal Support Details:
    System.Net.WebException: The current operation timed-out after 3600 seconds
    at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.SynchronizeDefaultContentSource(IDictionary applications)
    at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
    at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

    Solution: This is caused by the Office Server Search Service having bad authentication information. First, go to Central Administration and click on the affected server. This should take you to the services on server view. Click on the Office SharePoint Server Search Service link and it will take you to the settings page. Enter the correct login information. On the machine itself, restart the Office SharePoint Server Search service in the Services management console. This should generate two new log entries Event IDs 10044 and 10045 indicating that changes to the configuration were successfully saved and imported. To re-enable search indexing on your site, restart IIS.


    Deepesh Yevle MCTS

    Monday, January 07, 2013 10:06 AM