Send to me by Jeff Shannon, BellSouth. Thanks, Jeff, for this information.
Last week, it was brought to my attention that full-text indexing on SharePoint Services Sites was non-operational. Upon investigation of the problem, the following Event Log entries where discovered regarding SQL Server Full-Text searching:
Symptoms (Ref: KB 277549)
Event Source: Microsoft Search
Description: The crawl seed in project cannot be accessed. Error: 8007007f - The specified procedure could not be found.
-and-
Event Source: Microsoft Search
Description: The crawl for project could not be started, because no crawl seeds could be accessed. Fix the errors and try the crawl again.
When you run a full-text catalog population, the process runs fast and completes almost immediately. Even after the full-text catalog population, the Item Count of the full-text catalog may still be 1.
A search of Microsoft’s Knowledge Base articles returned information on the previously referenced article number 277549. The following explanation for the potential cause and workaround/fix is listed below:
Potential Cause 1 (Ref: KB 277549)
SQL Server adds itself as an Administrator to the Microsoft Search service (MSSearch). When the service logon account for the MSSQLServer service is changed through Control Panel, the service logon account no longer has administrative privileges over the MSSearch service, thus causing the error messages shown in the "Symptoms" section.
Workaround 1 (Ref: KB 277549)
Steps to Reproduce Behavior
1. Open the SQL Server Enterprise Manager. From the Action menu point to Properties, and then click Security.
2. Change the Startup service account to System Account.
3. Stop and then restart the MSSQLServer service.
4. Change the Startup service account back to the domain account you want. (Make sure that you perform this task through the SQL Server Enterprise Manager and not Control Panel.)
5. Stop and then restart both the MSSQLServer and MSSearch services. SQL Server should now have administrative control over the Microsoft Search service.
After implementing the workaround in KB 277549, the problem was not resolved. Upon further investigation, KB 817301 indicated that certain DLLs pertaining to full-text search may need to be re-registered. The following workaround was implemented:
Workaround 2 (Ref: KB 817301)
To work around this problem, re-register the following Microsoft Search (MSSearch) DLL files on all the nodes of the Failover cluster:
Query.dll
Tquery.dll
To re-register the DLLs, follow these steps:
1. Open a command prompt.
2. Run the following command: regsvr32 Full path of MSSearch DLL file
Note by default, the MSSearch DLL files exist in the C:\Program Files\Common Files\System\MSSearch\Bin folder.
After you re-register the DLL files, perform the full-text catalog population. If the full-text catalog is still not populated, you must re-register all the DLL files that are in the MSSearch DLL files folder.
This workaround was also unable to fix the problem. After exhausting the resources available via Microsoft’s Support and third party web sites, Ken Bullock our Microsoft TAM was contacted about opening a support case. Case SRX040830602639 was opened on August 30, 2004. Jason Howell of Microsoft’s PSS SQL Server group was assigned to the case. After discussing the problem and walking through what had already be done, Jason reviewed other Knowledge Base articles and non-published support cases to determine how the problem had been addressed and resolved with other Microsoft customers.
Other customers that experienced this problem were able to resolve the problem by re-installing the Full-Text portion of the SQL Server Service Pack 3a update. Looking at the SP 3a log created (undocumented) with Jason revealed there had been a problem installing SP 3a. The following excerpt from that log file is inserted below with a red circle indicating the error condition:
SQL Server 2000 Service Pack 3a Install Log
16:59:56 End: InstallPkgs (ID_INSTALLMDACQFE)
16:59:56 Begin: InstallPkgs (ID_INSTALLMSSEARCH)
16:59:56 InstallMSSearch instance: MSSQLSERVER
16:59:56 Software\Microsoft\Search\Install: Version: 9.107.5512
16:59:56 MSSearch 2.0 or greater version check returned -1
16:59:56 Setup is installing the Microsoft Full-Text Search Engine...
16:59:56 “F:\SQLSERVER2000SP3a\x86\FullText\MSSearch\Search\SearchStp.exe" /s /a:SQLServer
17:00:10 Process Exit Code: (2) The system cannot find the file specified.
17:00:10 MSSearch setup requires a reboot.
17:00:10 End: InstallPkgs (ID_INSTALLMSSEARCH)
Based on error, it was determined that we must re-install the Full-Text portion of SP 3a. In order to do the re-install correctly, the MSSQLServer service had to be stopped prior to the install. This was done after SharePoint customers had been notified of the needed down time to occur after normal business hours, 7:30 pm CT. Ray Ranson of Accenture and I used the following command string to re-install the indexing component:
Re-Installation of SQL Server Full-Text Indexing (Ref: KB 827449)
F:\ SQLSERVER2000SP3a\x86\FullText\MSSearch\Search\SearchStp.exe /s /a:SQLServer
After the re-install, we initiated a full population of the full-text index on the NetworkSites database. The population was successful indexing over 48,000 items. Subsequent full populations were run on the other databases on the production SQL Server, all successful. I ran a test on the morning of August 31, 2004 where I uploaded a file to a Windows SharePoint Services (Team) site and ran an incremental crawl. The properties of the full-text index were updated with the additional content.
It appears the problem has been resolved. More frequent monitoring of the full-text indexing will be performed until we are satisfied that the problem has been totally resolved.
SQL Server Full-Text Index Property Page for NetworkSites
Successful Index Crawl Event Log Entry