Error in Site Data WebService

Just recently I was trying to track down an indexer issue on MOSS 2007 in the Shared Services Provider (SSP). The error was "Error in the Site Data Web Service" in the location of http://<ssp web host>/ssp/admin/Content.

After digging around in the logs I found an error to the call: GetWebDefaultPage. After pointing SharePoint Designer at this Content sub site (which hosts the BDC entity display template pages) in the SSP host, I found out that there is no default page (default.aspx).

You can do 4 things to solve this problem.

1. Ignore it


2. Create a crawl rule to skip this site completely


3. Create an empty Default.aspx in the site


4. Remove the SSP host from the Local SharePoint Sites Content source.

I am not convinced Option 2 is a good idea as it could lead to strange searhc behaviour especially with BDC applications.

In our environment, we decided on Option 4 as we had no need to index the SSP at the moment.

I hope this helps.

Nate

SharePoint 2007 and Event Id: 6482 and 6398

I recently ran into 2 strange errors when deploying a SharePoint server. It so happens that this error occurred just after deploying the Adobe x64 iFilter pack.

Event ID: 6482 - Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (GUID).

Reason: Exception from HRESULT: 0x80040D1B

And

Event ID: 6398

The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (GUID) threw an exception. More information is included below.

Exception from HRESULT: 0x80040D1B

As a result, I was unable to navigate to the Search Settings in the default SSP.

It turns out that I had 2 duplicate entries in the registry for the Adobe PDF file type.

Check out the registry key:

HKLM\Software\Microsoft\Office Server\12.0\Search\Applications\GUID\Gather\Portal_Content\Extensions\ExtensionList

I removed one of them and we were off again.

This will happen when you add the file type by hand in the registry and then add it as a File Type in the SSP Host web application.

I hope it helps.