After rebuilding the server and adding the new server back into the MOSS farm (See previous blog entry in this series), I have noticed that Crawling and Propagating Status was Retrieving on the Manage Search Service page from the Central Administration, Application tab.
Knowing “Retrieving” status means there must be something wrong with the index move, I tried to do some further research on the farm. Attempting to access Search Settings page from the SSP Administration Site threw an error – Authentication failed because the remote party has closed the transport stream. Additionally series of event ID: 6482 errors were generated in the application event log on the Index or Query Servers stating similar error description.
After goggling on the error – Authentication failed because the remote party has closed the transport stream, I came across the blog entry with similar problem.
According to the blog, these errors were generated because Office Server Web Services site on the Query Server and Index Server weren’t able to talk to each other through the default SSL port and most probably caused by the new server might be introduced in the MOSS farm with the Microsoft.NET 3.5 SP1.
Looking further, I have found out that new server indeed had Microsoft.NET 3.5 SP1 installed and existing servers didn’t have .NET 3.5 frameworks. While rebuilding the server, it is most important to verify that new server has exactly same Microsoft.NET versions installed as existing servers in the MOSS farm. If you update the MOSS farm with the new server with the Microsoft .NET Framework 3.5 Service Pack 1 (SP1), there are known issues causing the self-issued certificate used by the Office Server Web Services to become corrupted. This causes the Error event ID 6482 to be issued every minute on the server. It eventually causes the transport stream issues between the Query and Index Servers making them unable to reach each other required by Enterprise Search.
If you have similar problems, you might want to check out the following Microsoft KB article to see it can resolve the problem. http://support.microsoft.com/kb/962928
Here are excerpts from the KB article:
This issue occurs when the following conditions are true:
- The server that is running Office SharePoint Server 2007 has the query role in a server farm.
- The server farm was updated with Microsoft .NET Framework 3.5 Service Pack 1 (SP1).
- The roles of the query server and the index server are not on the same server in the server farm.
- This causes the self-issued certificate that is used by the Office Server Web Services to become corrupted. This causes the Error event ID 6482 to be issued every minute on the server.
To resolve this issue, follow these steps:
- Stop the Office SharePoint Search Services from the services snap-in or using command prompt – net stop osearch and Press Enter.
- Download and install the IIS 6.0 Resource Kit Tools. To obtain the IIS 6.0 Resource Kit Tools, visit the following Microsoft Web site: http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en
- On both the Query and Index servers in the farm, at the command prompt, type selfssl /s:951338967 /v:1000 and Press ENTER. Please note that 951338967 is the default ID of the Office Server Web Services certificate and 1000 is the number of days that the certification will be valid.
- Start the Office SharePoint Search Services from the services snap-in or using command prompt – net stop osearch and Press Enter.
- Either uninstall the .NET Framework 3.5 SP1 from the MOSS farm or if you really want to keep the .NET Framework 3.5 SP1, Download and install the following update to the .NET Framework 3.5 SP1 – http://support.microsoft.com/kb/959209/
- After performing above steps, Office Server Web Services web site should be updated with the SelfSSL certificate, Search Settings Page should be accessible, and communication between Query and Index Server should work.