Microsoft KB Archive/883783

= BUG: You may receive an error message when you try to initialize full-text indexing for a database on a computer that is running Windows XP SP2 =

Article ID: 883783

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft Windows XP Service Pack 2

-



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



SYMPTOMS
When you try to initialize full-text indexing for a database by using an application, such as SQL Server Enterprise Manager, and your instance of Microsoft SQL Server 2000 is running on a computer that is also running Microsoft Windows XP Service Pack 2 (SP2), you may receive an error message that is similar to the following:

Access is denied.

Additionally, if you use a stored procedure such as sp_fulltext_database to initialize full-text indexing for a database, a 7619 error may occur and you may receive an error message that is similar to the following:

Execution of a full-text operation failed. Access is denied.

This problem occurs only if all the following conditions are true:
 * You use a local user account or a domain user account on your computer to run the instance of SQL Server 2000.
 * You use an account that does not have administrative permissions to run the instance of SQL Server 2000.

Note The Microsoft Search service must always run under the local system account.



WORKAROUND
To work around this problem, use one of the following methods:  Change the SQL Server 2000 logon account information. To do this, start SQL Server 2000 by using any account that has administrative permissions. For more information about how to change the SQL Server services logon account information, visit the following MSDN Web site:

http://msdn2.microsoft.com/en-us/library/aa197921(SQL.80).aspx

 Bypass DCOM Activation security. To bypass DCOM Activation security for the Microsoft Search Gathering Manager application, follow these steps:  Click Start, click Run, type gpedit.msc in the Open box, and then click OK. In the left pane, expand Computer Configuration under Local Computer Policy, and then expand Administrative Templates. Expand System, expand Distributed COM, and then expand Application Compatibility Settings. In the right pane, double-click Allow local activation security check exemptions. Click Enabled, and then click OK.</li> In the right pane, double-click Define Activation Security Check exemptions.</li> Click Enabled, and then click Show.</li> Click Add.</li> In the Enter the name of the item to be added box, type {c7310557-ac80-11d1-8df3-00c04fb6ef4f} .</li> In the Enter the value of the item to be added box, type 1, and then click OK.</li> In the Show Contents dialog box, click OK.</li> In the Define Activation Security Check exemptions Properties dialog box, click OK.</li> Close Group Policy Editor.</li></ol>

You can also bypass DCOM Activation security for the Microsoft Search Gathering Manager application by using Registry Editor. To do this, follow these steps.

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. <ol> Click Start, click Run, type regedit in the Open box, and then click OK.</li> Locate the &quot;AllowLocalActivationSecurityCheckExemptionList&quot; value in the following registry subkey:

Note If you do not find the DCOM registry subkey in the registry, you must manually create the DCOM registry subkey and the corresponding registry subkeys and entries in the DCOM registry subkey.</li> Double-click AllowLocalActivationSecurityCheckExemptionList.</li> In the Value data box, type 1, and then click OK.</li> Locate the &quot;ListBox_Support_ActivationSecurityCheckExemptionList&quot; value in the following registry subkey:

</li> Double-click ListBox_Support_ActivationSecurityCheckExemptionList.</li> In the Value data box, type 1, and then click OK.</li> <li>Locate the following registry subkey:

</li> <li>On the Edit menu, point to New, and then click String Value.</li> <li>Set the following properties for the new registry key value: <ul> <li>Value name: {c7310557-ac80-11d1-8df3-00c04fb6ef4f}</li> <li>Value Data: 1</li></ul> </li> <li>Close Registry Editor.</li></ol>

This workaround overrides the security check for the Microsoft Search Gathering Manager COM object and resolves the problem.</li></ul>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Additional query words: fulltext access activate

Keywords: kbgpo kbsecurity kbenable kbdcom kberrmsg kbregistry kbtshoot kbbug KB883783

-

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

© Microsoft Corporation. All rights reserved.