Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Full-Text Search / November 2005

Tip: Looking for answers? Try searching our database.

2005 FT - Unable to re-populate catalogue

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Simon - 17 Nov 2005 10:50 GMT
Hi,

I have a clustered 2005 server (build 9.00.1399.06). On the server I have 3
FT catalogues.

When I created the first catalogue everything was fine. The catalogue built
fine and returns results correctly (sooo much quicker than 2000!). Then I
tried to do a full re-population.

The full text service appeared to hang and never re-populate the catalogue.
From various bits of testing I have found this:

Using sp_who and sp_lock I can see that the Gatherer spid is blocked by the
FT Monitor spid. The Gatherer has await resource of MD 24(7:0:0) which the
monitor has Sch-S lock on. Being a system process I cannot kill it. During
this time I cannot access the Full text screen in Man Studio (blocked again),
but I can query other catalogues.

When it appears to hang as above I tried stopping the FT service in cluster
admin. The process would not stop. I have to kill it using task manager.

After a restart of just the full text service I cannot access the FT
catalogue screen, though strangley I can't see any blocking. The catalogue
appears not to be rebuilt. I can query other catalogues fine. I cannot see
any blocking of gatherer (I can't see it in sp_who), or any other blocking
spids for that matter.

Last resort I restart the Full text service and SQL Service. Upon restarting
the catalogue starts repopulating straight away. I can access it in Man
Studio, it completes fine and everything is good. Until I try to start a full
population again. (BTW I've tried incremental and rebuilding - same as above
happens).

So in other words I have to restart the SQL service everytime I want to
re-populate my FT catalogue.

I'm hoping someone can help me. Any form of suggestion welcomed!

Thanks
Simon - 17 Nov 2005 11:30 GMT
I just found out that FT keeps a log. Here is part of todays output (it is
repeated several times):

2005-11-17 11:16:06.30 spid13s     Warning: Full-text population for table
or indexed view '[IMS].[dbo].[MyTable]' failed to send batch of data to
MSFTESQL service (table or indexed view ID '1253579504', catalog ID '5',
database ID '6'). Error: 0x8001010e(The application called an interface that
was marshalled for a different thread.).

2005-11-17 11:16:16.30 spid12s     The full-text catalog health monitor
reported a failure for full-text catalog "FTC_MYCatName" (5) in database
"IMS" (6). Reason code: 0. Error: 0x8001010e(The application called an
interface that was marshalled for a different thread.). The system will
restart any in-progress population from the previous checkpoint. If this
message occurs frequently, consult SQL Server Books Online for
troubleshooting assistance. This is an informational message only. No user
action is required.

2005-11-17 11:22:16.86 spid13s     Informational: Reinitialized full-text
Full population for table or indexed view '[IMS].[dbo].[MyTable]' (table or
indexed view ID '1253579504', database ID '6') after a temporary failure.
Prior to error, the number of documents processed: 60800, errors encountered:
0.

> Hi,
>
[quoted text clipped - 35 lines]
>
> Thanks
Hilary Cotter - 17 Nov 2005 14:54 GMT
Sounds like Monitor is locking with the population process. The population
does put locks on the rows and table it is indexing to preserve
transactional consistency.

It looks like you have to do a less invasive form of monitoring.

Signature

Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

>I just found out that FT keeps a log. Here is part of todays output (it is
> repeated several times):
[quoted text clipped - 76 lines]
>>
>> Thanks
Simon - 17 Nov 2005 15:13 GMT
Hilary,

Thanks for your reply. I agree with the cause. However the FT Monitor
process is a system process not something I have put in place!!

I don't what it is or what it does but I can't do anything to stop it. Do
you know what this process is?

Thanks

> Sounds like Monitor is locking with the population process. The population
> does put locks on the rows and table it is indexing to preserve
[quoted text clipped - 82 lines]
> >>
> >> Thanks
simondm@gmail.com - 22 Nov 2005 12:40 GMT
Is anyone able to help on this?

In short I'm trying to resolve this error:

2005-11-17 11:16:06.30 spid13s     Warning: Full-text population for
table
or indexed view '[IMS].[dbo].[MyTable]' failed to send batch of data to

MSFTESQL service (table or indexed view ID '1253579504', catalog ID
'5',
database ID '6'). Error: 0x8001010e(The application called an interface
that
was marshalled for a different thread.).

Which occurs when I populate my catalogue.

Thanks
Simon
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.