FIX: FT Wizard Fails with Windows NT Authentication and Not Sysadmin

View products that this article applies to.

This article was previously published under Q198163

BUG #: 52932 (SQLBUG_70)

Expand all | Collapse all

SYMPTOMS

If a user attempts to run the Full Text Indexing Wizard for a SQL Server database using Windows NT Authentication, without first selecting that database, and the user is not a member of the System Administrators (sysadmin) role, the Full Text Wizard will fail with the following error message:

[SQL-DMO] The name 'guest' was not found in the Logins collection. If
the name is a qualified name, use [] to separate various parts of the
name, and try again.

The user should be presented with a list of databases to select from to enable Full Text Indexing.

Back to the top

WORKAROUND

To work around this problem, a member of the db_owner role (DBO) of a database who is not a member of the sysadmin role should first select the database before launching the Full Text Indexing Wizard.

Back to the top

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:

232570 (http://support.microsoft.com/kb/232570/ ) INF: 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.

Back to the top

MORE INFORMATION

Only members of the sysadmin role or the database owner (DBO) have permissions to create a Full Text Catalog. If a user without these permissions attempts to create a Full Text Catalog, the Full Text Indexing Wizard will fail with the following error message dialog:

Only members of the sysadmin role or the database owner can execute this stored procedure.

This is expected behavior. Ensure that the user has the appropriate permissions before running the Full Text Indexing Wizard. You can confirm this in the SQL Server Enterprise Manager by doing the following:

Under the Security folder for the SQL Server, click Logins.
Right-click the user name and then click Properties on the shortcut menu.
Click the Server Roles or Database Access tabs and select the appropriate role or access to perform the task.

Back to the top