PRB: SQL Server Full-Text Search Does Not Populate Catalogs (317746)

SYMPTOMS

When you start a full or incremental population, you may receive the following events in the Microsoft Windows NT or Microsoft Windows 2000 Event Viewer application log and the population fails:

Event ID: 3036
Event Source: Microsoft Search
Description:
The start address <MSSQL75://SQLServer/7f60ed59> cannot be accessed.
Context: SQLServer Application, SQL0000XXXXXX
Catalog Details: Document filtering could not be completed because the document server did not respond within the specified timeout.
Try crawling the server later, or increase the timeout values. (0x80040d7b)

Event ID: 3036
Event Source: Microsoft Search
Description:
The crawl seed <MSSQL75://SQLServer/75d7831f> in project <SQLServer SQL0000XXXXXX> cannot be accessed.
Error: 800705b4 - This operation returned because the timeout period expired.

Event ID: 3036
Event Source: Microsoft Search
Description:
The crawl seed <MSSQL75://SQLServer/525a080f> in project <SQLServer SQL0001400005> cannot be accessed.
Error: 800700e9 - No process is on the other end of the pipe.

Event ID: 3024
Event Source: Microsoft Search
Description:
The crawl could not be started because the start addresses cannot be accessed.
Fix the errors and try the crawl again.
Context: SQLServer Application, SQL0000XXXXXX Catalog

Event ID: 3018
Event Source: Microsoft Search
Description:
The end of crawl has been detected. The Gatherer successfully processed 0 documents totaling 0K.
It failed to filter 1 documents. 0 URLs could not be reached or were denied access.
Context: SQLServer Application, SQL0000XXXXXX Catalog

Event ID: 7045
Event Source: Microsoft Search
Description:
The catalog was not propagated because no new files were detected. Context: SQLServer Application, SQL0000XXXXXX Catalog

WORKAROUND

In some environments, you may not want to allow Microsoft Windows NT or Windows 2000 system administrators to administer or access SQL Server.

If that is the case and you want a full-text search, follow these steps:

Grant the [NT Authority\System] user a logon to SQL Server. For example:
```
EXEC sp_grantlogin [NT Authority\System]
```

Add that account to the sysadmins role:

EXEC sp_addsrvrolemember @loginame = [NT Authority\System] 
, @rolename =  'sysadmin'

MORE INFORMATION

In most cases you do not have to add the BUILTIN\Administrators account. For more information, refer to the "References" section of this article.

As described in the "Workaround" section of this article, it is sufficient for the service account for SQL Server and SQL Server Agent to have login rights (and be sysadmins), and to add [NT Authority\System] as a sysadmin to represent the local system, which thereby enables full-text search to work properly.

REFERENCES

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

295034 FIX: Microsoft Search Service May Cause 100% CPU Usage if BUILTIN\Administrators Login Is Removed

263712 INF: How to Prevent Windows NT Administrators from Administering a Clustered SQL Server

If SQL Server is running in a clustered environment, you may want to review the following articles in the Microsoft Knowledge Base:

291255 BUG: IsAlive Check Does Not Run Under the Context of the BUILTIN\Administrators Account

243218 INF: Installation Order for SQL Server 2000 Enterprise Edition on Microsoft Cluster Server