显示标签为“rebuild”的博文。显示所有博文
显示标签为“rebuild”的博文。显示所有博文

2012年3月19日星期一

Full text indexing not working!

Hi there,
I recently had to rebuild my database server and recreate databases from backups. All is well except full text indexing is not working although I did install it.
I get the following error from query analyser when trying to access full text indexing:
Server: Msg 7607, Level 17, State 1, Line 1
Search on full-text catalog 'FULL TEXT INDEX SEARCH' for database ID 184, table ID 1029578706 with search condition 'as' failed with unknown result (449ccdc).
In my event view I see error messages:
Unable to initialize project <SQLServer SQL0018400005>. Error: 80040154 - Class not registered .
Any advice appreciated.
Matt,
Can you pass us the exact sql query?Were you trying to search for 'as'? If
so, isnt that included in the ignored words list?Also, whats the SQLServer
version and service pack level?
I apologise for replying back with another set of questions but little more
detail would help !
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Matt" <matt@.community.nospam> wrote in message
news:3FF82A86-0B99-490C-AB5F-17E6A6A4E8F0@.microsoft.com...
> Hi there,
> I recently had to rebuild my database server and recreate databases from
backups. All is well except full text indexing is not working although I did
install it.
> I get the following error from query analyser when trying to access full
text indexing:
> Server: Msg 7607, Level 17, State 1, Line 1
> Search on full-text catalog 'FULL TEXT INDEX SEARCH' for database ID 184,
table ID 1029578706 with search condition 'as' failed with unknown result
(449ccdc).
> In my event view I see error messages:
> Unable to initialize project <SQLServer SQL0018400005>. Error: 80040154 -
Class not registered .
> Any advice appreciated.
|||Hi,
Are you using SQL 2000.
If yes, then install SP3 for SQL Server 2000. I had a identical problem
after database restore some time back and got resolved after applying SP3.
Note:
Even if you have SP3 , try to reinstall and check the FULLTEXT searrh.
Thanks
Hari
MCDBA
"Matt" <matt@.community.nospam> wrote in message
news:3FF82A86-0B99-490C-AB5F-17E6A6A4E8F0@.microsoft.com...
> Hi there,
> I recently had to rebuild my database server and recreate databases from
backups. All is well except full text indexing is not working although I did
install it.
> I get the following error from query analyser when trying to access full
text indexing:
> Server: Msg 7607, Level 17, State 1, Line 1
> Search on full-text catalog 'FULL TEXT INDEX SEARCH' for database ID 184,
table ID 1029578706 with search condition 'as' failed with unknown result
(449ccdc).
> In my event view I see error messages:
> Unable to initialize project <SQLServer SQL0018400005>. Error: 80040154 -
Class not registered .
> Any advice appreciated.
|||i think you'll need to recreate and repopulate the fulltext catalogs. a database backup does not contain the fulltext catalogs.
http://support.microsoft.com/default...b;en-us;240867
http://support.microsoft.com/default...b;en-us;236789
Matt wrote:

> Hi there,
> I recently had to rebuild my database server and recreate databases from backups. All is well except full text indexing is not working although I did install it.
> I get the following error from query analyser when trying to access full text indexing:
> Server: Msg 7607, Level 17, State 1, Line 1
> Search on full-text catalog 'FULL TEXT INDEX SEARCH' for database ID 184, table ID 1029578706 with search condition 'as' failed with unknown result (449ccdc).
> In my event view I see error messages:
> Unable to initialize project <SQLServer SQL0018400005>. Error: 80040154 - Class not registered .
> Any advice appreciated.
|||Hi and thanks for the replies;
It is SQL 7.0 with service pack 4. I am unsure whether I installed full text search AFTER applying the service pack 4 or not.
My example used an ignore word but other keywords fail as well (usually sql will tell you if it is an ignored word).
I have already rebuilt and repopulated the catelogues but still have the problem.
Should I reinstall full text search and if so how do I uninstall a Full text search and then reinstall? OR should I reinstall Service pack 4.
thanks again,
Matt

Full text indexing not working!

Hi there,
I recently had to rebuild my database server and recreate databases from bac
kups. All is well except full text indexing is not working although I did in
stall it.
I get the following error from query analyser when trying to access full tex
t indexing:
Server: Msg 7607, Level 17, State 1, Line 1
Search on full-text catalog 'FULL TEXT INDEX SEARCH' for database ID 184, ta
ble ID 1029578706 with search condition 'as' failed with unknown result (449
ccdc).
In my event view I see error messages:
Unable to initialize project <SQLServer SQL0018400005>. Error: 80040154 - Cl
XXX not registered .
Any advice appreciated.Matt,
Can you pass us the exact sql query?Were you trying to search for 'as'? If
so, isnt that included in the ignored words list?Also, whats the SQLServer
version and service pack level?
I apologise for replying back with another set of questions but little more
detail would help !
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Matt" <matt@.community.nospam> wrote in message
news:3FF82A86-0B99-490C-AB5F-17E6A6A4E8F0@.microsoft.com...
> Hi there,
> I recently had to rebuild my database server and recreate databases from
backups. All is well except full text indexing is not working although I did
install it.
> I get the following error from query analyser when trying to access full
text indexing:
> Server: Msg 7607, Level 17, State 1, Line 1
> Search on full-text catalog 'FULL TEXT INDEX SEARCH' for database ID 184,
table ID 1029578706 with search condition 'as' failed with unknown result
(449ccdc).
> In my event view I see error messages:
> Unable to initialize project <SQLServer SQL0018400005>. Error: 80040154 -
Class not registered .
> Any advice appreciated.|||Hi,
Are you using SQL 2000.
If yes, then install SP3 for SQL Server 2000. I had a identical problem
after database restore some time back and got resolved after applying SP3.
Note:
Even if you have SP3 , try to reinstall and check the FULLTEXT searrh.
Thanks
Hari
MCDBA
"Matt" <matt@.community.nospam> wrote in message
news:3FF82A86-0B99-490C-AB5F-17E6A6A4E8F0@.microsoft.com...
> Hi there,
> I recently had to rebuild my database server and recreate databases from
backups. All is well except full text indexing is not working although I did
install it.
> I get the following error from query analyser when trying to access full
text indexing:
> Server: Msg 7607, Level 17, State 1, Line 1
> Search on full-text catalog 'FULL TEXT INDEX SEARCH' for database ID 184,
table ID 1029578706 with search condition 'as' failed with unknown result
(449ccdc).
> In my event view I see error messages:
> Unable to initialize project <SQLServer SQL0018400005>. Error: 80040154 -
Class not registered .
> Any advice appreciated.|||i think you'll need to recreate and repopulate the fulltext catalogs. a dat
abase backup does not contain the fulltext catalogs.
http://support.microsoft.com/defaul...kb;en-us;240867
http://support.microsoft.com/defaul...kb;en-us;236789
Matt wrote:

> Hi there,
> I recently had to rebuild my database server and recreate databases from b
ackups. All is well except full text indexing is not working although I did
install it.
> I get the following error from query analyser when trying to access full t
ext indexing:
> Server: Msg 7607, Level 17, State 1, Line 1
> Search on full-text catalog 'FULL TEXT INDEX SEARCH' for database ID 184,
table ID 1029578706 with search condition 'as' failed with unknown result (4
49ccdc).
> In my event view I see error messages:
> Unable to initialize project <SQLServer SQL0018400005>. Error: 80040154 -
Class not registered .
> Any advice appreciated.

Full text indexing not working!

Hi there
I recently had to rebuild my database server and recreate databases from backups. All is well except full text indexing is not working although I did install it
I get the following error from query analyser when trying to access full text indexing
Server: Msg 7607, Level 17, State 1, Line
Search on full-text catalog 'FULL TEXT INDEX SEARCH' for database ID 184, table ID 1029578706 with search condition 'as' failed with unknown result (449ccdc)
In my event view I see error messages
Unable to initialize project <SQLServer SQL0018400005>. Error: 80040154 - Class not registered .
Any advice appreciated.Matt,
Can you pass us the exact sql query?Were you trying to search for 'as'? If
so, isnt that included in the ignored words list?Also, whats the SQLServer
version and service pack level?
I apologise for replying back with another set of questions but little more
detail would help !
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Matt" <matt@.community.nospam> wrote in message
news:3FF82A86-0B99-490C-AB5F-17E6A6A4E8F0@.microsoft.com...
> Hi there,
> I recently had to rebuild my database server and recreate databases from
backups. All is well except full text indexing is not working although I did
install it.
> I get the following error from query analyser when trying to access full
text indexing:
> Server: Msg 7607, Level 17, State 1, Line 1
> Search on full-text catalog 'FULL TEXT INDEX SEARCH' for database ID 184,
table ID 1029578706 with search condition 'as' failed with unknown result
(449ccdc).
> In my event view I see error messages:
> Unable to initialize project <SQLServer SQL0018400005>. Error: 80040154 -
Class not registered .
> Any advice appreciated.|||Hi,
Are you using SQL 2000.
If yes, then install SP3 for SQL Server 2000. I had a identical problem
after database restore some time back and got resolved after applying SP3.
Note:
Even if you have SP3 , try to reinstall and check the FULLTEXT searrh.
Thanks
Hari
MCDBA
"Matt" <matt@.community.nospam> wrote in message
news:3FF82A86-0B99-490C-AB5F-17E6A6A4E8F0@.microsoft.com...
> Hi there,
> I recently had to rebuild my database server and recreate databases from
backups. All is well except full text indexing is not working although I did
install it.
> I get the following error from query analyser when trying to access full
text indexing:
> Server: Msg 7607, Level 17, State 1, Line 1
> Search on full-text catalog 'FULL TEXT INDEX SEARCH' for database ID 184,
table ID 1029578706 with search condition 'as' failed with unknown result
(449ccdc).
> In my event view I see error messages:
> Unable to initialize project <SQLServer SQL0018400005>. Error: 80040154 -
Class not registered .
> Any advice appreciated.|||i think you'll need to recreate and repopulate the fulltext catalogs. a database backup does not contain the fulltext catalogs.
http://support.microsoft.com/default.aspx?scid=kb;en-us;240867
http://support.microsoft.com/default.aspx?scid=kb;en-us;236789
Matt wrote:
> Hi there,
> I recently had to rebuild my database server and recreate databases from backups. All is well except full text indexing is not working although I did install it.
> I get the following error from query analyser when trying to access full text indexing:
> Server: Msg 7607, Level 17, State 1, Line 1
> Search on full-text catalog 'FULL TEXT INDEX SEARCH' for database ID 184, table ID 1029578706 with search condition 'as' failed with unknown result (449ccdc).
> In my event view I see error messages:
> Unable to initialize project <SQLServer SQL0018400005>. Error: 80040154 - Class not registered .
> Any advice appreciated.|||Hi and thanks for the replies;
It is SQL 7.0 with service pack 4. I am unsure whether I installed full text search AFTER applying the service pack 4 or not.
My example used an ignore word but other keywords fail as well (usually sql will tell you if it is an ignored word).
I have already rebuilt and repopulated the catelogues but still have the problem.
Should I reinstall full text search and if so how do I uninstall a Full text search and then reinstall? OR should I reinstall Service pack 4.
thanks again,
Matt

2012年3月11日星期日

Full text index rebuild reboots server

I'm having a problem with the full text index rebuild process. Previously
when I did a full rebuild the process stopped, then the server rebooted and
the rebuild started over and completed. I had hoped this was just a fluke
but this last time I set up an indexing job to run at 2 am and the same
thing happened. About an hour into the rebuild the server reboots, then
restarts and the job restarts and takes about two hours to complete.
@.@.version:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
The server is a Compaq 5500 proliant with 1/2 gig of RAM, the main drive is
RAID 5 with the logs on a smaller RAID 0 drive.
In looking at the logs the only thing I found that I thought were relevant -
except the entries where the server comes online and looks for transactions
to rollback - were these:
Project <SQLServer$SERIALS_SQL SQL0000900005> has been shut down as
requested by user
and
Compaq System Information Agent: Compaq Health: The server is
operational again, the server has previously been shutdown by the Automatic
Server Recovery (ASR) featuer and has just become operational again. [SNMP
TRAP: 6025 in CPQHLTH.MIB]
The indexed tables are not extremely large, about 250,000 records each. One
of the indexed fields is 5,000 characters long, but I wouldn't think that
would be a problem.
Has anyone seen this before? I am going to pursue the compaq automatic
server recovery feature and see if that yeilds any clues, but I was hoping
someone else had run into this and had a hint or two to share.
Thanks in advance;
David Craig
ABC-CLIO
"DCraig" <dcraig@.nospam.com> wrote in message
news:OD1VNjsNEHA.3420@.TK2MSFTNGP11.phx.gbl...
> I'm having a problem with the full text index rebuild process. Previously
> when I did a full rebuild the process stopped, then the server rebooted
and
> the rebuild started over and completed. I had hoped this was just a fluke
> but this last time I set up an indexing job to run at 2 am and the same
> thing happened. About an hour into the rebuild the server reboots, then
> restarts and the job restarts and takes about two hours to complete.
> @.@.version:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> The server is a Compaq 5500 proliant with 1/2 gig of RAM, the main drive
is
> RAID 5 with the logs on a smaller RAID 0 drive.
Correction, the logs are on a mirrored (RAID 1) drive.
|||DCraig,
It is not a common occurrence that running a Full Population (full rebuild)
will cause a server reboot to occur.
Could you review your System Event log for any low free disk space available
on either your system disk (usually c:\ drive) or the drive array where you
have placed the FT Catalogs. Again this is not common, but one think to keep
in mind is that the MSSearch service requires that at least 15% of disk
space always be available on the disk drive where the FT Catalog resides as
well as enough disk space on the system drive to write tmp files when FT
Indexing MS Word document files.
Also, search your Application event log for any MssCi source events
(warnings & errors) and post them here.
Regards,
John
"DCraig" <dcraig@.nospam.com> wrote in message
news:OtGCZctNEHA.1908@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> "DCraig" <dcraig@.nospam.com> wrote in message
> news:OD1VNjsNEHA.3420@.TK2MSFTNGP11.phx.gbl...
Previously[vbcol=seagreen]
> and
fluke
> is
> Correction, the logs are on a mirrored (RAID 1) drive.
>
|||"John Kane" <jt-kane@.comcast.net> wrote in message
news:%23d9nsWwNEHA.2708@.TK2MSFTNGP11.phx.gbl...
> DCraig,
> It is not a common occurrence that running a Full Population (full
rebuild)
> will cause a server reboot to occur.
> Could you review your System Event log for any low free disk space
available
> on either your system disk (usually c:\ drive) or the drive array where
you
> have placed the FT Catalogs. Again this is not common, but one think to
keep
> in mind is that the MSSearch service requires that at least 15% of disk
> space always be available on the disk drive where the FT Catalog resides
as
> well as enough disk space on the system drive to write tmp files when FT
> Indexing MS Word document files.
>
John, thanks for your reply. The array with the full text index (also the
same as sql server and the data files) has 50 gigs free of 62.
Here are the system log entries, nothing before the server starts coming
back up:
5/9/2004 3:01:12 AM Server Agents Information Events 1090 N/A SERVER8
Compaq System Information Agent: Compaq Health: The server is operational
again. The server has previously been shutdown by the Automatic Server
Recovery (ASR) feature and has just become operational again.
[SNMP TRAP: 6025 in CPQHLTH.MIB]
5/9/2004 3:00:42 AM Foundation Agents Information Service 400 N/A SERVER8
The Compaq Foundation Agents service version 5.00 has started.
5/9/2004 3:00:39 AM SNMP Information None 1001 N/A SERVER8 The SNMP Service
has started successfully.
5/9/2004 3:00:38 AM Storage Agents Information Service 400 N/A SERVER8 The
Compaq Storage Agents service version 5.00 has started.
5/9/2004 3:00:37 AM Server Agents Information Service 400 N/A SERVER8 The
Compaq Server Agents service version 5.00 has started.
5/9/2004 3:00:36 AM NIC Agents Information Service 277 N/A SERVER8 The
Compaq NIC Management Agent version 5.00 has started.
5/9/2004 3:00:17 AM EventLog Information None 6005 N/A SERVER8 The Event log
service was started.
5/9/2004 3:00:17 AM EventLog Information None 6009 N/A SERVER8 Microsoft (R)
Windows 2000 (R) 5.0 2195 Service Pack 4 Multiprocessor Free.
5/9/2004 3:00:17 AM EventLog Error None 6008 N/A SERVER8 The previous system
shutdown at 2:42:16 AM on 5/9/2004 was unexpected.
So far I haven't been able to figure out if the automatic server recovery is
the cause or effect of the reboot.

> Also, search your Application event log for any MssCi source events
> (warnings & errors) and post them here.
Here are the application event log entries with MssCi in them:
5/9/2004 4:57:08 AM MssCi Information None 4103 N/A SERVER8 Master merge has
completed on
d:\mssql2000_data\mssql\data\mssql$serials_sql\ftd ata\sql0000900005\build\in
dexer\cifiles.
5/9/2004 3:04:24 AM MssCi Information None 4138 N/A SERVER8 Content index
corruption detected in component SmartBuffer1 in catalog
d:\mssql2000_data\mssql\data\mssql$serials_sql\ftd ata\sql0000900005\build\in
dexer\cifiles. Stack trace is 0x01165041
0x011DAD4B
0x011DADEE
0x011D8D45
0x011E8DED
0x011E57F0
0x011DF5F7
0x011DFD10
0x7C57438B
..
I noticed there were some virus definitions being downloaded about the same
time, could that have anything to do with it? I suppose I could turn off
live update while the index is being rebuilt but these days timely virus
protection is pretty important.
I'm assuming the corruption above is the result of the server rebooting
during indexing, as I said after that it went ahead and built the indexes
successfully. If I hadn't checked the logs I would have thought all was
well.
Thanks again for your help,
David Craig.
[vbcol=seagreen]
> Regards,
> John
>
> "DCraig" <dcraig@.nospam.com> wrote in message
> news:OtGCZctNEHA.1908@.TK2MSFTNGP12.phx.gbl...
> Previously
rebooted[vbcol=seagreen]
> fluke
same[vbcol=seagreen]
then[vbcol=seagreen]
14:22:05[vbcol=seagreen]
drive
>
|||DCraig,
The error "Content index corruption detected in component SmartBuffer1 in
catalog" could be the source of your re-boot, depending upon how you have
your Compaq Info Agents setup. The error by itself should not (and normally
does not) re-boot the server.. You should place a support call with
Microsoft PSS SQL Server support to identify the source of this error and
get it resolved first.
I doubt if the virus definitions being downloaded about the same time is a
cause, but if you can turn off the definition download (and not the virus
protection) briefly (for a day or two), and continue to run your Full
Population, this should determine if this is involved with the above error
as well.
Regards,
John
"DCraig" <dcraig@.nospam.com> wrote in message
news:#TTLvE4NEHA.1616@.TK2MSFTNGP12.phx.gbl...
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:%23d9nsWwNEHA.2708@.TK2MSFTNGP11.phx.gbl...
> rebuild)
> available
> you
> keep
> as
> John, thanks for your reply. The array with the full text index (also the
> same as sql server and the data files) has 50 gigs free of 62.
> Here are the system log entries, nothing before the server starts coming
> back up:
> 5/9/2004 3:01:12 AM Server Agents Information Events 1090 N/A SERVER8
> Compaq System Information Agent: Compaq Health: The server is operational
> again. The server has previously been shutdown by the Automatic Server
> Recovery (ASR) feature and has just become operational again.
> [SNMP TRAP: 6025 in CPQHLTH.MIB]
> 5/9/2004 3:00:42 AM Foundation Agents Information Service 400 N/A SERVER8
> The Compaq Foundation Agents service version 5.00 has started.
> 5/9/2004 3:00:39 AM SNMP Information None 1001 N/A SERVER8 The SNMP
Service
> has started successfully.
> 5/9/2004 3:00:38 AM Storage Agents Information Service 400 N/A SERVER8
The
> Compaq Storage Agents service version 5.00 has started.
> 5/9/2004 3:00:37 AM Server Agents Information Service 400 N/A SERVER8 The
> Compaq Server Agents service version 5.00 has started.
> 5/9/2004 3:00:36 AM NIC Agents Information Service 277 N/A SERVER8 The
> Compaq NIC Management Agent version 5.00 has started.
> 5/9/2004 3:00:17 AM EventLog Information None 6005 N/A SERVER8 The Event
log
> service was started.
> 5/9/2004 3:00:17 AM EventLog Information None 6009 N/A SERVER8 Microsoft
(R)
> Windows 2000 (R) 5.0 2195 Service Pack 4 Multiprocessor Free.
> 5/9/2004 3:00:17 AM EventLog Error None 6008 N/A SERVER8 The previous
system
> shutdown at 2:42:16 AM on 5/9/2004 was unexpected.
> So far I haven't been able to figure out if the automatic server recovery
is
> the cause or effect of the reboot.
>
> Here are the application event log entries with MssCi in them:
> 5/9/2004 4:57:08 AM MssCi Information None 4103 N/A SERVER8 Master merge
has
> completed on
>
d:\mssql2000_data\mssql\data\mssql$serials_sql\ftd ata\sql0000900005\build\in
> dexer\cifiles.
> 5/9/2004 3:04:24 AM MssCi Information None 4138 N/A SERVER8 Content index
> corruption detected in component SmartBuffer1 in catalog
>
d:\mssql2000_data\mssql\data\mssql$serials_sql\ftd ata\sql0000900005\build\in
> dexer\cifiles. Stack trace is 0x01165041
> 0x011DAD4B
> 0x011DADEE
> 0x011D8D45
> 0x011E8DED
> 0x011E57F0
> 0x011DF5F7
> 0x011DFD10
> 0x7C57438B
> .
> I noticed there were some virus definitions being downloaded about the
same
> time, could that have anything to do with it? I suppose I could turn off
> live update while the index is being rebuilt but these days timely virus
> protection is pretty important.
> I'm assuming the corruption above is the result of the server rebooting
> during indexing, as I said after that it went ahead and built the indexes
> successfully. If I hadn't checked the logs I would have thought all was
> well.
> Thanks again for your help,
> David Craig.
> rebooted
> same
> then
> 14:22:05
> drive
>
|||"John Kane" <jt-kane@.comcast.net> wrote in message
news:%23STaYl9NEHA.3816@.TK2MSFTNGP12.phx.gbl...
> DCraig,
> The error "Content index corruption detected in component SmartBuffer1 in
> catalog" could be the source of your re-boot, depending upon how you have
> your Compaq Info Agents setup. The error by itself should not (and
normally
> does not) re-boot the server.. You should place a support call with
> Microsoft PSS SQL Server support to identify the source of this error and
> get it resolved first.
>
I'll try that, thanks.

> I doubt if the virus definitions being downloaded about the same time is a
> cause, but if you can turn off the definition download (and not the virus
> protection) briefly (for a day or two), and continue to run your Full
> Population, this should determine if this is involved with the above error
> as well.
>
That is worth a try also, thanks for your time and effort.
David Craig.
[vbcol=seagreen]
> Regards,
> John
>
>
> "DCraig" <dcraig@.nospam.com> wrote in message
> news:#TTLvE4NEHA.1616@.TK2MSFTNGP12.phx.gbl...
where[vbcol=seagreen]
to[vbcol=seagreen]
disk[vbcol=seagreen]
resides[vbcol=seagreen]
FT[vbcol=seagreen]
the[vbcol=seagreen]
operational[vbcol=seagreen]
SERVER8[vbcol=seagreen]
> Service
> The
The[vbcol=seagreen]
> log
> (R)
> system
recovery
> is
> has
>
d:\mssql2000_data\mssql\data\mssql$serials_sql\ftd ata\sql0000900005\build\in[vbcol=seagreen]
index
>
d:\mssql2000_data\mssql\data\mssql$serials_sql\ftd ata\sql0000900005\build\in[vbcol=seagreen]
> same
off[vbcol=seagreen]
indexes[vbcol=seagreen]
a[vbcol=seagreen]
reboots,[vbcol=seagreen]
complete.
>
|||You have hopefully already found the answer, but if not, read this...
http://forums1.itrc.hp.com/service/f...hreadId=565419
It may be the same problem.
Stuart Bowen
Bandicoot Limited
Business and Internet Solutions
www.bandicoot.co.uk

2012年2月26日星期日

Full Population - completes but never ends

We rebuilt a catalog this weekend after upgrading to Adobe iFilter
version 6. Have attempted the rebuild twice, both times the result has
been that all rows are indexed, but the population never 'ends'. The
status remains at '1 - Full Population in Progress'. The item count
indicates 74,926 - which is one more than our (current) row count of
74,925. The mssearch and mssdmn processes continue to consume CPU
(~50%).
We're on Win2K, Sql2K, sp3A. There do not appear to be any error
messages in the event log.
The catalog contains one table, and it is configured with Change
Tracking. The table has one indexed column, an image column containing
primarily Word and PDF binaries.
Any help/suggestions appreciated!
Dave Hensler
dhensler@.prestongates.com
The item count reflects the numbers of rows being indexed and the numbers of
tables being full text indexed, so the number seems correct.
Can you use profiler to see if anything is being pulled? Look for events
coming with an Application Name of PKM.
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
"Dave Hensler" <dhensler@.prestongates.com> wrote in message
news:1118069691.983721.165480@.o13g2000cwo.googlegr oups.com...
> We rebuilt a catalog this weekend after upgrading to Adobe iFilter
> version 6. Have attempted the rebuild twice, both times the result has
> been that all rows are indexed, but the population never 'ends'. The
> status remains at '1 - Full Population in Progress'. The item count
> indicates 74,926 - which is one more than our (current) row count of
> 74,925. The mssearch and mssdmn processes continue to consume CPU
> (~50%).
> We're on Win2K, Sql2K, sp3A. There do not appear to be any error
> messages in the event log.
> The catalog contains one table, and it is configured with Change
> Tracking. The table has one indexed column, an image column containing
> primarily Word and PDF binaries.
> Any help/suggestions appreciated!
> Dave Hensler
> dhensler@.prestongates.com
>
|||Profiler shows lots of these under PKM:
exec sp_fulltext_getdata 29, 1835153583, 0x00002D31, 1
They are firing many times per second and seem to be originating in the
master database.
|||This is interesting - I have found 3 pdf files in the FTDATA directory
that are corrupt. They will not open successfully in Acrobat. It
looks like they have been there for about 29 hours.
Seems reasonable to try to remove these files from the database and see
if it frees up the search service. However, I need to identify the
rows containing these binaries. The file names have the form
'0000001f7d78a4e70000BF9D00000003.pdf'. Any idea how to locate these
in the table? Or is there another log that may identify the row where
these binaries came from?
Thanks for any advice.
|||This means that the population is still in progress.
go to
http://msdn.microsoft.com/library/de...tml/sp04f9.asp
Download the code sample and run it in VB 6. It will tell you where you are
in your population.
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
"Dave Hensler" <dhensler@.prestongates.com> wrote in message
news:1118078599.081054.208540@.g49g2000cwa.googlegr oups.com...
> Profiler shows lots of these under PKM:
> exec sp_fulltext_getdata 29, 1835153583, 0x00002D31, 1
> They are firing many times per second and seem to be originating in the
> master database.
>
|||Thanks for the tool, Hilary. Using it I can see that the population is
cycling within a small set of database rows. The rows are not
necessarily recent, in fact they are spread all over the table. I've
looked at the individual binaries and do not see any pattern - some are
newer versions of the pdf file format, some are older, etc.
Have you seen anything like this before? How about Adobe's latest
filter (ifilter 6.0) - any known issues?
Thanks - Dave
|||The problem seems to be solved. The indexer was repeatedly cycling
over 5 rows containing pdf binaries. Once the 5 rows were identified
and the binaries removed from the table, the indexer went into the Idle
state. When they are reinserted into the table, the indexer hangs up
again until they are removed. These pdf binaries do not appear to be
damaged or unusual when they are opened in Acrobat, however.