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

Article translations Article translations
Article ID: 295034 - View products that this article applies to.
This article was previously published under Q295034
BUG #: 351866 (SHILOH_BUGS)
Expand all | Collapse all

SYMPTOMS

The Microsoft Search service (MSSearch) may fail to start, or may cause 100% CPU usage, if both of the following conditions are met:
  • The BUILTIN\Administrators account is removed from SQL Server 2000.
  • The Microsoft Search service is configured to start under an account other than the local system account.

CAUSE

Running the Microsoft Search service under an account other than local system is not supported.

RESOLUTION

To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

WORKAROUND

Change the startup account for the Microsoft Search service to the local system account.

STATUS

Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.

MORE INFORMATION

You do not need to add back the BUILTIN\Administrators account. It is fully 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 syadmin to represent the local system and thereby enable full-text search to work properly.

If you do wish to add the BUILTIN\Administrators account back into SQL Server, start SQL Enterprise Manager, go to the \ServerName\Security\Logins folder, and grant access to the BUILTIN\Administrators user.

If you wish to prevent Windows NT administrators from administering SQL Server, see the following article in the Microsoft Knowledge Base:
263712 INF: How To Prevent Windows NT Administrators From Administering a Clustered SQL Server

Properties

Article ID: 295034 - Last Review: October 31, 2003 - Revision: 3.2
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
  • MSN Search
Keywords: 
kbbug kbfix kbsqlserv2000sp1fix KB295034

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com