FIX: Full-Text Failures Occur Because of SQL Server Account Change (308787)


The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)
This article was previously published under Q308787
BUG #: 353483 (Shiloh_bugs)

SYMPTOMS

In Enterprise Manager, if you change the account that SQL Server 2000 runs under, the following error message may occur:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Error 22035: No mapping between account names and security IDs was done.
After you change the account, if you try to create a full-text catalog, the following error message may occur:
Server: Msg 7619, Level 16, State 1, Procedure sp_fulltext_catalog, Line 64
Execution of a full-text operation failed. No mapping between account names and security IDs was done.
Alternately, the preceding error message may also occur with different text:
Server: Msg 7619, Level 16, State 1, Procedure sp_fulltext_catalog, Line 64
Execution of a full-text operation failed. The process cannot access the file because it is being used by another process.

CAUSE

This problem occurs if you delete a user account at the operating system level under which SQL Server runs.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft 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

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this problem, use these steps:
  1. Delete the following keys under HKLM\Software\Microsoft\Search\1.0:
    • ...\Applications\SQLServer\AccessControl
    • ...\Gathering Manager\AccessControl
    • ...\Gathering Manager\Applications\SQLServer\AccessControl
    • ...\SearchService\AccessControl


  2. Start the MS Search service under the Local System Account. The preceding keys are populated to their default values.
  3. In Enterprise Manager, change the account that SQL Server runs under to the Local System Account.
  4. Change back to the account you want for SQL Server from Enterprise Manager.

STATUS

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

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a Microsoft Windows user account. In Enterprise Manager make the new Windows user the account under which SQL Server runs.
  2. Delete the Windows user account you created in step 1.
  3. In Enterprise Manager, change the account under which SQL Server runs.
Modification Type:MajorLast Reviewed:10/17/2003
Keywords:kbbug kbfix KB308787
©2003 Microsoft Corporation. All rights reserved.