Help - An unknown full-text failure (80004005) while trying to create a new full-text catalog

Help - An unknown full-text failure (80004005) while trying to create a new full-text catalog

Post by andy_tre » Wed, 30 Jun 2004 07:07:18


Hi,

We just started getting this error when trying to create new catalogs
on databases that do not already have a Full-Text catalog. I can
create a new catalog on a database that has an existing catalog, but
cannot on one that does not.
I get the following error: "An unknown full-text failure (80004005)
occurred in function EnumCatalogs on full-text catalog" when I try to
create a new catalog through Enterprise Manager and this error when I
execute sp_FullText_Database:
"Server: Msg 7608, Level 17, State 1, Procedure sp_fulltext_database,
Line 46
An unknown full-text failure (80004005) occurred in function
EnumCatalogs on full-text catalog ''."

Line 46 in sp_fulltext_database looks to be:
DBCC CALLFULLTEXT ( 7, @dbid ) -- FTDropAllCatalogs ( "@dbid" )

I've seen plenty of postings of this error, but they are all for SQL
Server 7.0.
We're running SQL Server 2000:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003
16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

Any ideas?

Thanks in advance.
Andy
 
 
 

Help - An unknown full-text failure (80004005) while trying to create a new full-text catalog

Post by John Kan » Wed, 30 Jun 2004 14:52:00

Andrew,
You are correct *most* of the causes for the "unknown full-text failure
(80004005) while trying to create a new full-text catalog" in SQL Server
2000 were either eliminated or more specific error text messages were
defined. Still, you should check the obvious causes, for example, have you
recently changed the DCOM settings on this server? Have you or anyone else
changed the MSSQLServer startup account via Win2K's Component services? Does
the SQL logon account BUILTIN\Administrator exist with the default settings
of master database and have sysadmin privileges? Is this SQL Server
installed on a Domain Controller (DC) or backup DC (BDC)? Except for the
DCOM setting & installed on a DC/BDC, you should of gotten different error
text messages if any other changes were made. You should review the
following KB articles:

277549 (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K Component
Services]
http://www.yqcomputer.com/ ;EN-US;277549
317746 (Q317746) PRB: SQL Server Full-Text Search Does Not Populate Catalogs
http://www.yqcomputer.com/ ;en-us;317746

263712 (Q263712) INF: How to Impede Windows NT Administrators from
Administering a Clustered SQL Server
http://www.yqcomputer.com/ ;EN-US;263712

Depending upon your answers, it may be necessary to re-install the SQL FTS
components via the procedures doc'ed in the following KB article: 827449 How
to manually reinstall the Microsoft Search service for an instance of SQL
2000
http://www.yqcomputer.com/ ;EN-US;827449
Regards,
John

 
 
 

Help - An unknown full-text failure (80004005) while trying to create a new full-text catalog

Post by jt-kan » Fri, 02 Jul 2004 03:40:19

ndrew,
A follow-up to my reply below... There is now an updated KB article
"295772 (Q295772) How to debug full-text search when a 7608
(0x80004005) error message occurs in SQL Server" at
http://support.microsoft.com/?kbid=295772 that discuss in more detail
how to debug the unknown full-text failure (80004005) error you have
encountered. Let us know if you have resolved this error!

Thanks,
John




"John Kane" < XXXX@XXXXX.COM > wrote in message news:<# XXXX@XXXXX.COM >...
 
 
 

Help - An unknown full-text failure (80004005) while trying to create a new full-text catalog

Post by andy_tre » Fri, 02 Jul 2004 06:07:53

i John,

Thanks for your quick response. Unfortunately, it was nothing out of
the "obvious" catagory. I checked into the suggested articles with no
luck either.

Found a workaround since we do have another server where there is no
problem creating catalogs. We'll probably end up doing the manual
reinstall you recommended, but currently don't have the time to try
it. It's not mission critical since it's just a dev server.

Thanks again!
Andy

"John Kane" < XXXX@XXXXX.COM > wrote in message news:<# XXXX@XXXXX.COM >...