Microsoft KB Archive/280872

= FIX: SQL Server 7.0 Microsoft Search Fails to Start With Error 1332 =

Article ID: 280872

Article Last Modified on 3/14/2006

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q280872



BUG #: 55180 (SQLBUG_70)



SYMPTOMS
If a SQL Server 7.0 server is moved to a different domain, the Microsoft Search (MSSEARCH) service may fail to start with the error message:

Unable to lookup account LookupAccountSid: Error 1332 - No mappings between account names and security IDs was done.

If you change the Startup account of the MSSQLServer Service from Control Panel instead of through Enterprise Manager this may also result in the above error message.



WORKAROUND
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

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.

 Open Regedt32.exe and delete the following registry keys:

 Open the Services applet and start Microsoft Search Service (MSSEARCH) with the Local System account. (The Microsoft Search Service should always use the Local System account.) Open SQL Server Enterprise Manager, navigate to SQL Server Properties, Security:  If you have the SQL Server Startup service account set to System account, stop and restart the SQL Server Service. If you have the SQL Server Startup service account set to This account, retype the password for the account and stop and restart the SQL Server Service. </li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider.

NOTE: The fix in the SQL Server 7.0 Service Pack prevents this problem if you apply the service pack before you move the computer to a different domain. Once you experience the problem, if you apply the service pack it will not resolve the issue. You must use the workaround described in this article.

<div class="moreinformation_section">

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

277549 PRB: Unable to Build Full-Text Catalog

282254 PRB: SQL Server Service Did Not Start Due to a Logon Failure

Additional query words: error 3023 3036 1332 full text ft mssearch

Keywords: kbbug kbpending KB280872

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.