FIX: Changing SQL Server Account to Non-Admin for Full-Text Search Makes Existing Catalogs Unusable (295051)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q295051 BUG #: 235408 (SHILOH_BUGS) SYMPTOMS For a full-text search catalog, changing the SQL Server
account to a non-administrator makes existing catalogs unusable. For
example, if SQL Server is running with the administrator account, the following
script successfully creates and queries a catalog:
use pubs
go
exec sp_fulltext_table 'authors', 'drop'
exec sp_fulltext_catalog 'mycatalog','drop'
exec sp_fulltext_database 'enable'
exec sp_fulltext_catalog 'mycatalog','create'
exec sp_fulltext_table 'authors','create','mycatalog','UPKCL_auidind'
exec sp_fulltext_column 'authors','address','add'
exec sp_fulltext_table 'authors','activate'
exec sp_fulltext_catalog 'mycatalog','start_full'
go
waitfor delay '00:00:10'
go
select * from authors where contains(address, 'bigge')
go
However, if you change the SQL Server account to a non-administrator
account, you may receive the following error: Server:
Msg 7619, Level 16, State 1, Line 1 Execution of a full-text operation failed.
The catalog does not exist or is currently unavailable. Please retry the action
again later and if this symptom persists, contact the system administrator.
RESOLUTIONTo 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
IMPORTANT: When you apply the latest SQL Server 2000 service pack to
correct the problem, you must apply the service pack to both the server and the
client. WORKAROUND To access existing full-text search catalogs, rebuild and
repopulate them. The existing catalogs can also be accessed by switching back
to an administrator account. STATUSMicrosoft has confirmed that this is a
problem in SQL Server 2000.
This problem was first corrected in SQL Server 2000
Service Pack 1.
Modification Type: | Major | Last Reviewed: | 11/6/2003 |
---|
Keywords: | kbBug kbfix kbSQLServ2000sp1fix KB295051 |
---|
|