Monday, April 23, 2007

Event ID : 6482 and 6398 errors for SharePoint 2003 Upgrade


I am currently conducting a SharePoint 2003 upgrade for MOSS 2007 in Load balanced medium server farm with SQL Cluster. I was getting following error message on my front end server.

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482

Date: 23/04/2007
Time: 3:05:36 PM
User: N/A
Computer: SERVERNAME
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance

(1cf3346b-cb9d-430e-ab11-4ca65c7a93a5).

Reason: Object 61f7f45f-d7ac-4948-91f6-b881dffea275 not found.

Techinal Support Details:
System.Collections.Generic.KeyNotFoundException:

Object 61f7f45f-d7ac-4948-91f6-b881dffea275 not found.
at Microsoft.Office.Server.Search.Administration.

SearchApi.get_App()
at Microsoft.Office.Server.Search.Administration.

SearchApi.SetUsersPermittedToQuery

(String[] userNames, Boolean force)
at Microsoft.Office.Server.Search.Administration.

SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.

ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Following error message in my index server.


Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398

Date: 23/04/2007
Time: 3:23:32 PM
User: N/A
Computer: SERVERNAME
Description:
The Execute method of job definition Microsoft.Office.Server.Search.Administration.

AddQueryServerJob (ID d39a43cb-8b90-4094-8f70-f51751700928)

threw an exception. More information is included below.

Index location '\\SERVERNAME\searchindexpropagation' not found on indexer 'SERVERNAME'. Aborting query server deployment for application EntrSharedServices.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


I did following steps to fix this problem,


  • Navigate to Check Services Enabled in this Farm (Central Administration > Application Management > Check Services Enabled in this Farm)

  • There was the error message
    Service: Office SharePoint Server Search
    Issue: The query server index file location on SERVERNAME is not shared. This location must be shared to allow for this server to receive propagation.
    Impact: Index propagation to SERVERNAME will fail.
    Action: Use the Office SharePoint Server Search Settings page to create the share.

  • I navigate to the page Office SharePoint Server Search Service Settings page(Central Administration > Operations > Services on Server > Office SharePoint Server Search Service Settings)

  • Set up the page.

    The above errors were cleared from my event log for good.

    I am a very happy man!!!!!!

13 Comments:

At 3:02 AM, Anonymous Anonymous said...

Its not working for me. I get "Failed to configure propagation share" error.

 
At 12:42 AM, Anonymous Anonymous said...

The "Failed to configure propagation share" is the same message I'm getting. It essentially means the share already exists. Yet, I still get the error message. Very Odd.

 
At 5:04 AM, Blogger Noel said...

Gayan,
are you using a seperate account for search .can you give some more details on how you resolved this problem.I am getting the same error when I use a seperate account for search service.

Noel

 
At 4:25 AM, Blogger Silentvale said...

Thank you very much. This worked perfectly for me.

 
At 12:31 AM, Blogger mtyson79 said...

I get the following error message and cannot find any solutions:

Message: Failed to connect to an IPC Port: The system cannot find the file specified.

 
At 3:18 PM, Anonymous Anonymous said...

I navigate to Central Administration > Application Management but I cannot see "Check Services Enabled in this Farm" anywhere.

 
At 12:21 AM, Anonymous Anonymous said...

We have the same 2 errors. When I navigate to the checkfarmservices.aspx page it finds no errors:

"The following issues were found in your farm. There are no items to show in this view."

 
At 6:42 PM, Anonymous Frederik Munster said...

Hi Guys,

We had the same problem on our Farm.

The problem was that File and Printer Sharing was not enabled on Servers that are serving search queries.

1. Open Network Connections
2. Open properties of the LAN Connection.
3. Enable the File and Printer Sharing.
4. Stop the Office Server Search Service in Central Administration (on the servers serving search queries).
5. Start the office Server Search Service in Central Administration.

 
At 9:03 PM, Blogger Gabriel Teodor said...

This comment has been removed by the author.

 
At 9:05 PM, Blogger Gabriel Teodor said...

Hi all,

For the following error I found the answer. Need to restart the Office Search Service from Services:

1) net stop osearch
2) net start osearch

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date: 9/24/2009
Time: 11:06:43 AM
User: N/A
Computer: SPIWA1SRV
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (e367eed0-d752-40a7-8c67-cea2ac7f494f).

Reason: Object f99f5ef2-0848-49eb-984c-bda0422450d0 not found.

Techinal Support Details:
System.Collections.Generic.KeyNotFoundException: Object f99f5ef2-0848-49eb-984c-bda0422450d0 not found.
at Microsoft.Office.Server.Search.Administration.SearchApi.get_App()
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at ...

http://www.it-share.ro

 
At 11:01 PM, Anonymous Victor Campuzano said...

In my case, we migrate to another server and has this problem.

After "un huevo" of days, I found the solution:

See if HKLM\Software\Microsoft\Office Server\12.0\Search\Applications

There are 1 or more [object-id] ??

If are more than one, see the diference between.

In my case, the folder [object-id-specified-in-events] was incomplete.

I copied the complete key and subkeys from the older server to the new server, restart the Office Search Service and ....

WOW!! Solved! :-)

Sorry for my english, jejeje, soy de Murcia. :-9

 
At 8:23 AM, Anonymous Anonymous said...

I had a similar issue which I fixed by uninstalling and reinstalling the Sharepoint Search Service:

Central Operations => Services on Server => Search Indexing => Stop => Uninstall => OK
Search Indexing => Start => Farm Search Service Account Password => Start
It may prompt you to reenter the search parameters at the top of the page and reprompt for a Farm Search Service Account Password => OK

 
At 6:27 AM, Anonymous digital signature software said...

Very informative post. I sometimes do presentations on SharePoint and was wondering if I could use your Print List example in my presentations.

 

Post a Comment

<< Home