Re: Error Msg 30053 - Word breaking timed out for the full-text query string

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Andrew how much data are in these rows and how many rows?

How many changes do you make to your data?

Is there anything funky about your html?

Do you have this problem if you index the documents as html?

I'd like to look at your data if you want to send it to me offline.
"Andrew Urquhart" <andrew.urquhart@xxxxxxxxx> wrote in message
news:491d7ca0-d184-4ea7-8780-d58321df1f5f@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi all

Here's a SQL Server 2008 fulltext indexing problem that 3 days of head-
scratching hasn't alleviated. There are four known symptoms:

Symptom 1. All fulltext queries timeout after 10s with the message:
"Msg 30053, Level 16, State 102, Line 1
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."

Symptom 2. The SQL Server ERRORLOG log file largely consists of the
following block of error messages repeated thousands of times, usually
at a frequency of 1 block per second:
"2009-02-09 11:13:27.78 spid28s A new instance of the full-text
filter daemon host process has been successfully started.
2009-02-09 11:13:27.90 spid26s Error: 30089, Severity: 17, State:
1.
2009-02-09 11:13:27.90 spid26s The fulltext filter daemon host
(FDHost) process has stopped abnormally. This can occur if an
incorrectly configured or malfunctioning linguistic component, such as
a wordbreaker, stemmer or filter has caused an irrecoverable error
during full-text indexing or query processing. The process will be
restarted automatically.
2009-02-09 11:13:28.01 spid26s A new instance of the full-text
filter daemon host process has been successfully started.
2009-02-09 11:13:28.22 spid23s The full-text filter daemon host
process has stopped normally. The process will be automatically
restarted if necessary."

Symptom 3. The FDLAUNCHERRORLOG log file consists of the following
block of error messages repeated thousands of times, usually at a
frequency of 4 blocks per second:
"2009-02-09 11:17:03.788 MSSQLFDLauncher$SQL_SITE service received
control message.
2009-02-09 11:17:03.890 MSSQLFDLauncher$SQL_SITE service
successfully launched FDHost.exe Process(process id = 912)."

Symptom 4. The SQLFT* log files consist of lines of following the form
(the embedded PK GUID changes for each line) repeated thousands of
times, usually at a frequency of 2 lines per second:
"2009-02-09 11:21:01.98 spid22s Error '0x80004005' occurred during
full-text index population for table or indexed view '[ai_site].[dbo].
[ArticleContent]' (table or indexed view ID '421576540', database ID
'5'), full-text key value '72F52428-C8B5-4BDE-80ED-01D2995740A7'.
Attempt will be made to reindex it."



Platform notes:
==============
The problem is seen when using SQL Server 2008 Standard on Windows
Server 2008. The problem is not seen on SQL Server 2005 Express with
Advanced Services on Windows Server 2003. The problem appeared on the
production server around 1 month after the initiaL SQL install, the
problem immediately appeared on an identical development platform upon
restoring the affected database from the production environment.



Table structure
===============
The table being indexed ('ArticleContent') has 61583 rows with the
following structure (ignoring foreign keys and constraints):

CREATE TABLE [dbo].[ArticleContent](
[articleContentId] [uniqueidentifier] ROWGUIDCOL NOT NULL,
[articleId] [uniqueidentifier] NOT NULL,
[languageId] [tinyint] NOT NULL,
[status] [tinyint] NOT NULL,
[spellState] [tinyint] NOT NULL,
[title] [nvarchar](100) NOT NULL,
[dateCreated] [bigint] NOT NULL,
[dateModified] [bigint] NOT NULL,
[content] [ntext] NOT NULL,
CONSTRAINT [PK_ArticleContent] PRIMARY KEY NONCLUSTERED
([articleContentId] ASC) WITH (PAD_INDEX = OFF,
STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS
= ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]


The [content] field holds well-formed and validating HTML 4.01 Strict
markup with the note that the HTML, HEAD (and all its children) and
BODY elements are not present, only the children of the BODY element
are present.
The table does not appear to have any locking issues as during
fulltext population as I can perform updates on the data. The database
collation is Latin1_General_CI_AS.



Fulltext index
==============
I have a fulltext index created as follows:

CREATE FULLTEXT CATALOG FTCatalog
AS DEFAULT
GO

CREATE FULLTEXT INDEX ON ArticleContent
([content] LANGUAGE 'British English'
,[title] LANGUAGE 'British English')
KEY INDEX PK_ArticleContent
ON FTCatalog
WITH CHANGE_TRACKING AUTO
GO


In addition to the manual scripting of index creation, I've also tried
creating/editing this via the various Management Studio GUIs. I've
also tried different languages, different fields, different tables.
All rows are eventually 'processed' during a rebuild, but the above
mentioned log files contain one error per tuple and the indexed item
count is always zero.


SQL Services
============
The SQL services run as follows:

Name State Start Mode
Log On As
SQL Server Integration Services 10.0 Stopped Manual
NT AUTHORITY\NetworkService
SQL Server (SQL_SITE) Running Automatic
NT AUTHORITY\NetworkService
SQL Server (SQL_SITE_IO) Running Automatic
NT AUTHORITY\NetworkService
SQL Full-text Filter Daemon Launcher (SQL_SITE) Running Manual
NT AUTHORITY\LOCAL SERVICE
SQL Server Agent (SQL_SITE) Running Automatic
NT AUTHORITY\NetworkService
SQL Server Agent (SQL_SITE_IO) Running Automatic
NT AUTHORITY\NetworkService
SQL Server Browser Stopped Manual
NT AUTHORITY\LOCAL SERVICE

I've played around with various Windows users including a Local admin,
a Domain user, Local Service, Local System and Network System to no
avail.
I've played around with granting and resetting child permissions for
the local admin and all SQL* users/user-groups full control to data
folders, binn folders, you name it.
I've granted these users, via the local security policy, the Log-on
Locally right, to no avail. My sys-admin has checked for group policy
issues and he couldn't find any.



Additional notes
================
I've played around with the following during various stages of index
creation to no avail:
sp_fulltext_service 'restart_all_fdhosts'
sp_fulltext_service 'verify_signature' {, [0|1};
sp_fulltext_service 'load_os_resources' {, [0|1};



So, I'd be ecstatic if anyone has any ideas on what I can try next to
troubleshoot this!
--
Best,

Andrew Urquhart


.

Relevant Pages

  • Error Msg 30053 - Word breaking timed out for the full-text query string
    ... Here's a SQL Server 2008 fulltext indexing problem that 3 days of head- ... Symptom 1. ... I have a fulltext index created as follows: ...
    (microsoft.public.sqlserver.fulltext)
  • How to program a really fast product search catalogue
    ... am currently using the SQL Server 2000 fulltext engine for this task ... In SQL Server I am using the clause CONTAINSTABLE(products, name, ... expressions and use a 1:n relation between the expressions and the ... The search for "juicy mac" would then get a lock ...
    (microsoft.public.dotnet.languages.csharp)
  • How to program a really fast product search catalogue
    ... am currently using the SQL Server 2000 fulltext engine for this task ... In SQL Server I am using the clause CONTAINSTABLE(products, name, ... expressions and use a 1:n relation between the expressions and the ... The search for "juicy mac" would then get a lock ...
    (microsoft.public.sqlserver.programming)
  • Re: Slow performance after restarting
    ... Columnist, SQL Server Professional ... Launch additional instances of Query Analyzer and verify the connection ... Detach/Rename/Re-attach gets me a much smaller transaction ... >> log file is this size or what you do for backups. ...
    (microsoft.public.sqlserver.programming)
  • Re: Transaction Log Failure
    ... A maintenance plan can not create a log file, ... then bring up sql server. ... > maintenance plan that would create a transaction log file every hour. ... > 2004-12-14 21:00:43.51 backup BACKUP failed to complete the command ...
    (microsoft.public.sqlserver.server)