Why do I meet "Word breaking timed" out error

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Richard Li - 18 Apr 2008 07:37 GMT

Dear All,

I have just migrated from SQL Server 2005 to SQL Server 2008 Beta

I have a single table q_docversion with 1000 records

(
f_Doc_ID int PK
f_HeadLine nvarchar(510) [fulltext index column]
)

when I execute following statement

declare @word nvarchar(10)
set @word=N'CHINA'
select * from q_docversion where Contains (f_Headline,@word)
I met

Msg 30053, Level 16, State 102, Line 3
Word breaking timed out for the full-text query string. This can happen if
the wordbreaker took a long time to process the full-text query string, or if
a large number of queries are running on the server. Try running the query
again under a lighter load.

I am sure there is only one query

Reply to this Message

Hilary Cotter - 18 Apr 2008 16:56 GMT

What language are the docs you are indexing and which word breaker are you
using?

Are you indexing blobs?

> Dear All,
>
[quoted text clipped - 22 lines]
>
> I am sure there is only one query

Reply to this Message

Thermous - 15 May 2008 23:54 GMT

I discovered the following:

This can be caused if that FDHOST.exe is not running. To force it to start
again run this stored procedure:
exec sp_fulltext_service 'restart_all_fdhosts';

What I got when I ran that was the following error:
"Msg 30046, Level 16, State 1, Procedure sp_fulltext_service, Line 163
SQL Server encountered error 0x80070532 while communicating with full-text
filter daemon host (FDHost) process. Make sure that the FDHost process is
running. To re-start the FDHost process, run the sp_fulltext_service
'restart_all_fdhosts' command or restart the SQL Server instance."

0x80070532 I discovered is ERROR_PASSWORD_EXPIRED

Poking around some more I discovered that SQL Server had added a user
account (FDH$MSSQLSERVER) to my system which was marked that they had to
login to change the password. I trued turned that off and said password
should never expire, ran the stored procedure again and Lo! I now have
FDHOST.EXE running again and no longer get the word breaking error!

I think perhaps they need a better error code!

> Dear All,
>
[quoted text clipped - 21 lines]
>
> I am sure there is only one query

Reply to this Message

Thermous - 16 May 2008 00:25 GMT

Another thing I discovered is there is a stored proceure to set the user name
and password that the full text indexing host process will run under:
EXEC sp_fulltext_resetfdhostaccount @username = 'FDH$MSSQLSERVER',
@password = 'PassswordForFDH$MSSQLSERVER';
GO

Then I restarted SQLServer and all was good!

> I discovered the following:
>
[quoted text clipped - 44 lines]
> >
> > I am sure there is only one query

Reply to this Message