"robcam817" <robcam***@discussions.microsoft.com> wrote in message
news:7F3703C9-E9E4-4AB0-9D84-F29A74DBED9E@microsoft.com...
>I have not been able to find any information on Full Text Catalogs (FTC)
>with
> a status of 'Recovering'.  If anyone can help me by responding to my
> questions, I would greatly appreciate it.
>
> 1. How does a FTC get a status of 'Recovering'?
> 2. What implication does this status have on the FTC?
> 3. What is happening to the catalog while it is being recovered?
>
> Pretty much I'm looking for any information I can find, so any
> comments/links that would help me understand what is occurring are
> welcomed.
>
> Thanks,
>

"Hilary Cotter" wrote:

> Like a database the full-text catalogs are transactional in nature. It can
> be in the recovering state after an abrupt power off which will force a
> consistency check when it is launched. Check the event log to see if there
> are any messages from MSSCI or MSSearch which are relevant to this error.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> 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
>
>
>
> "robcam817" <robcam***@discussions.microsoft.com> wrote in message
> news:7F3703C9-E9E4-4AB0-9D84-F29A74DBED9E@microsoft.com...
> >I have not been able to find any information on Full Text Catalogs (FTC)
> >with
> > a status of 'Recovering'.  If anyone can help me by responding to my
> > questions, I would greatly appreciate it.
> >
> > 1. How does a FTC get a status of 'Recovering'?
> > 2. What implication does this status have on the FTC?
> > 3. What is happening to the catalog while it is being recovered?
> >
> > Pretty much I'm looking for any information I can find, so any
> > comments/links that would help me understand what is occurring are
> > welcomed.
> >
> > Thanks,
> >
>
>
>

"robcam817" wrote:

> Hilary,
>
> Thank you very much for responding to my post.  I had an issue the other day
> where the drive containing the FTData folder ran out of space which caused
> the mssearch service to lock up.  I stopped the service and freed up some
> space on the drive and started the service again.  When I restarted the
> catalog went into a 'recovering' status.  Here are some log entries from this
> issue:
>
> Event Type:    Error
> Event Source:    Microsoft Search
> Event Category:    Indexer
> Event ID:    7010
> Date:        10/17/2006
> Time:        3:08:20 PM
> User:        N/A
> Computer:    [server]
> Description:
> The project <SQLServer SQL0008700005> cannot be initialized. Error: 80041828
> - The disk has reached its configured space limit.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Event Type:    Error
> Event Source:    Microsoft Search
> Event Category:    Gatherer
> Event ID:    3010
> Date:        10/17/2006
> Time:        12:52:31 AM
> User:        N/A
> Computer:    ANNRS100UT06
> Description:
> The transaction cannot be appended to the project <SQLServer SQL0008700006>
> queue. File: e:\MSSQL\FTData\SQL0008700006\SQL0008700006.Ntfy1.gthr. Error:
> 80070070 - There is not enough space on the disk.  .
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> Event Type:    Failure Audit
> Event Source:    MssCi
> Event Category:    None
> Event ID:    4133
> Date:        10/17/2006
> Time:        12:50:35 AM
> User:        N/A
> Computer:    [server]
> Description:
> Very low disk space was detected on drive
> e:\mssql\ftdata\sql0008700005\build\indexer\cifiles. Please free up at least
> 24MB of space for content index to continue.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> Here are some additional errors from the Application Log that I saw today
> after I stopped and startded the MSSEARSH process for some testing: (i have
> also included some gatherer logs entries below)
>
> Event Type:    Error
> Event Source:    Microsoft Search
> Event Category:    Gatherer
> Event ID:    3013
> Date:        10/17/2006
> Time:        6:20:34 PM
> User:        N/A
> Computer:    [server]
> Description:
> The entry <MSSQL75://SQLSERVER/778AC167/006CFFA6> in the hash map on project
> <SQLServer SQL0008700005> cannot be updated. Error: 8007054e - Unable to
> complete the requested operation because of either a catastrophic media
> failure or a data structure corruption on the disk.  .
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> Event Type:    Warning
> Event Source:    Microsoft Search
> Event Category:    Gatherer
> Event ID:    3035
> Date:        10/17/2006
> Time:        6:20:34 PM
> User:        N/A
> Computer:    [server]
> Description:
> One or more warnings or errors for Gatherer project <SQLServer
> SQL0008700006> were logged to file <C:\Program Files\Microsoft SQL
> Server\MSSQL\FTData\SQLServer\GatherLogs\SQL0008700006.2.gthr>. If you are
> interested in these messages, please, look at the file using the gatherer log
> query object (gthrlog.vbs, log viewer web page).
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Event Type:    Error
> Event Source:    Application Error
> Event Category:    (100)
> Event ID:    1000
> Date:        10/17/2006
> Time:        6:20:20 PM
> User:        N/A
> Computer:    ANNRS100UT06
> Description:
> Faulting application mssearch.exe, version 9.107.8320.9, faulting module
> unknown, version 0.0.0.0, fault address 0x00000003.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 41 70 70 6c 69 63 61 74   Applicat
> 0008: 69 6f 6e 20 46 61 69 6c   ion Fail
> 0010: 75 72 65 20 20 6d 73 73   ure  mss
> 0018: 65 61 72 63 68 2e 65 78   earch.ex
> 0020: 65 20 39 2e 31 30 37 2e   e 9.107.
> 0028: 38 33 32 30 2e 39 20 69   8320.9 i
> 0030: 6e 20 75 6e 6b 6e 6f 77   n unknow
> 0038: 6e 20 30 2e 30 2e 30 2e   n 0.0.0.
> 0040: 30 20 61 74 20 6f 66 66   0 at off
> 0048: 73 65 74 20 30 30 30 30   set 0000
> 0050: 30 30 30 33               0003   
>
> My main objective for the post was to find out what is happening to the
> index when it is recovering.  I have a general idea of what causes the
> catalog to need to be recovered, but I wanted to know how ling it takes for
> the recovery too.  I am rebuilding some catalogs on a remote server and then
> moving them back and I wanted to know if they will go thorugh the recovery
> process an how long I can expect it to take or at least how I can estimate
> how long it will take. 
>
> Additionally, here is the @@versino for the server:
> Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)   May  3 2005 23:18:38  
> Copyright (c) 1988-2003 Microsoft Corporation  Developer Edition on Windows
> NT 5.2 (Build 3790: Service Pack 1)
>
> Thank you for your help...
> Dan
>
> "Hilary Cotter" wrote:
>
> > Like a database the full-text catalogs are transactional in nature. It can
> > be in the recovering state after an abrupt power off which will force a
> > consistency check when it is launched. Check the event log to see if there
> > are any messages from MSSCI or MSSearch which are relevant to this error.
> >
> > --
> > Hilary Cotter
> > Director of Text Mining and Database Strategy
> > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> >
> > This posting is my own and doesn't necessarily represent RelevantNoise's
> > positions, strategies or opinions.
> >
> > 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
> >
> >
> >
> > "robcam817" <robcam***@discussions.microsoft.com> wrote in message
> > news:7F3703C9-E9E4-4AB0-9D84-F29A74DBED9E@microsoft.com...
> > >I have not been able to find any information on Full Text Catalogs (FTC)
> > >with
> > > a status of 'Recovering'.  If anyone can help me by responding to my
> > > questions, I would greatly appreciate it.
> > >
> > > 1. How does a FTC get a status of 'Recovering'?
> > > 2. What implication does this status have on the FTC?
> > > 3. What is happening to the catalog while it is being recovered?
> > >
> > > Pretty much I'm looking for any information I can find, so any
> > > comments/links that would help me understand what is occurring are
> > > welcomed.
> > >
> > > Thanks,
> > >
> >
> >
> >

> Here is the Gatherer log info:
>
> SQL0008700005.3.gthr:
> Microsoft (R) Windows Script Host Version 5.6
> Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
>
> 10/18/2006 11:18:16 AM        Add    The gatherer has started
> 10/18/2006 11:43:26 AM        Add    The recovery has completed
> 10/18/2006 3:16:10 PM        Add    The gatherer has started
> 10/18/2006 3:36:34 PM        Add    The recovery has completed
>
> SQL0008700006.3.gthr:
> Microsoft (R) Windows Script Host Version 5.6
> Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
>
> 10/18/2006 11:18:16 AM        Add    The gatherer has started
> 10/18/2006 1:14:08 PM        Add    The recovery has completed
> 10/18/2006 3:16:10 PM        Add    The gatherer has started
>
> SQL0008700006.2.gthr: (the end of another gatherer log)
> 10/17/2006 6:20:36 PM    MSSQL75://SQLServer/47dbae45/0005EF0D    Add    Error
> fetching URL, (80041812 - Content Index has been shutdown.  )
> 10/17/2006 6:20:36 PM    MSSQL75://SQLServer/151b244e/000DF6BD    Add    Error
> fetching URL, (80041812 - Content Index has been shutdown.  )
>
> Thanks,
>
> "robcam817" wrote:
>
> > Hilary,
> >
> > Thank you very much for responding to my post.  I had an issue the other day
> > where the drive containing the FTData folder ran out of space which caused
> > the mssearch service to lock up.  I stopped the service and freed up some
> > space on the drive and started the service again.  When I restarted the
> > catalog went into a 'recovering' status.  Here are some log entries from this
> > issue:
> >
> > Event Type:    Error
> > Event Source:    Microsoft Search
> > Event Category:    Indexer
> > Event ID:    7010
> > Date:        10/17/2006
> > Time:        3:08:20 PM
> > User:        N/A
> > Computer:    [server]
> > Description:
> > The project <SQLServer SQL0008700005> cannot be initialized. Error: 80041828
> > - The disk has reached its configured space limit.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> > Event Type:    Error
> > Event Source:    Microsoft Search
> > Event Category:    Gatherer
> > Event ID:    3010
> > Date:        10/17/2006
> > Time:        12:52:31 AM
> > User:        N/A
> > Computer:    ANNRS100UT06
> > Description:
> > The transaction cannot be appended to the project <SQLServer SQL0008700006>
> > queue. File: e:\MSSQL\FTData\SQL0008700006\SQL0008700006.Ntfy1.gthr. Error:
> > 80070070 - There is not enough space on the disk.  .
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > Event Type:    Failure Audit
> > Event Source:    MssCi
> > Event Category:    None
> > Event ID:    4133
> > Date:        10/17/2006
> > Time:        12:50:35 AM
> > User:        N/A
> > Computer:    [server]
> > Description:
> > Very low disk space was detected on drive
> > e:\mssql\ftdata\sql0008700005\build\indexer\cifiles. Please free up at least
> > 24MB of space for content index to continue.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > Here are some additional errors from the Application Log that I saw today
> > after I stopped and startded the MSSEARSH process for some testing: (i have
> > also included some gatherer logs entries below)
> >
> > Event Type:    Error
> > Event Source:    Microsoft Search
> > Event Category:    Gatherer
> > Event ID:    3013
> > Date:        10/17/2006
> > Time:        6:20:34 PM
> > User:        N/A
> > Computer:    [server]
> > Description:
> > The entry <MSSQL75://SQLSERVER/778AC167/006CFFA6> in the hash map on project
> > <SQLServer SQL0008700005> cannot be updated. Error: 8007054e - Unable to
> > complete the requested operation because of either a catastrophic media
> > failure or a data structure corruption on the disk.  .
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > Event Type:    Warning
> > Event Source:    Microsoft Search
> > Event Category:    Gatherer
> > Event ID:    3035
> > Date:        10/17/2006
> > Time:        6:20:34 PM
> > User:        N/A
> > Computer:    [server]
> > Description:
> > One or more warnings or errors for Gatherer project <SQLServer
> > SQL0008700006> were logged to file <C:\Program Files\Microsoft SQL
> > Server\MSSQL\FTData\SQLServer\GatherLogs\SQL0008700006.2.gthr>. If you are
> > interested in these messages, please, look at the file using the gatherer log
> > query object (gthrlog.vbs, log viewer web page).
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> > Event Type:    Error
> > Event Source:    Application Error
> > Event Category:    (100)
> > Event ID:    1000
> > Date:        10/17/2006
> > Time:        6:20:20 PM
> > User:        N/A
> > Computer:    ANNRS100UT06
> > Description:
> > Faulting application mssearch.exe, version 9.107.8320.9, faulting module
> > unknown, version 0.0.0.0, fault address 0x00000003.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 41 70 70 6c 69 63 61 74   Applicat
> > 0008: 69 6f 6e 20 46 61 69 6c   ion Fail
> > 0010: 75 72 65 20 20 6d 73 73   ure  mss
> > 0018: 65 61 72 63 68 2e 65 78   earch.ex
> > 0020: 65 20 39 2e 31 30 37 2e   e 9.107.
> > 0028: 38 33 32 30 2e 39 20 69   8320.9 i
> > 0030: 6e 20 75 6e 6b 6e 6f 77   n unknow
> > 0038: 6e 20 30 2e 30 2e 30 2e   n 0.0.0.
> > 0040: 30 20 61 74 20 6f 66 66   0 at off
> > 0048: 73 65 74 20 30 30 30 30   set 0000
> > 0050: 30 30 30 33               0003
> >
> > My main objective for the post was to find out what is happening to the
> > index when it is recovering.  I have a general idea of what causes the
> > catalog to need to be recovered, but I wanted to know how ling it takes for
> > the recovery too.  I am rebuilding some catalogs on a remote server and then
> > moving them back and I wanted to know if they will go thorugh the recovery
> > process an how long I can expect it to take or at least how I can estimate
> > how long it will take.
> >
> > Additionally, here is the @@versino for the server:
> > Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)   May  3 2005 23:18:38
> > Copyright (c) 1988-2003 Microsoft Corporation  Developer Edition on Windows
> > NT 5.2 (Build 3790: Service Pack 1)
> >
> > Thank you for your help...
> > Dan
> >
> > "Hilary Cotter" wrote:
> >
> > > Like a database the full-text catalogs are transactional in nature. It can
> > > be in the recovering state after an abrupt power off which will force a
> > > consistency check when it is launched. Check the event log to see if there
> > > are any messages from MSSCI or MSSearch which are relevant to this error.
> > >
> > > --
> > > Hilary Cotter
> > > Director of Text Mining and Database Strategy
> > > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> > >
> > > This posting is my own and doesn't necessarily represent RelevantNoise's
> > > positions, strategies or opinions.
> > >
> > > 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
> > >
> > >
> > >
> > > "robcam817" <robcam***@discussions.microsoft.com> wrote in message
> > > news:7F3703C9-E9E4-4AB0-9D84-F29A74DBED9E@microsoft.com...
> > > >I have not been able to find any information on Full Text Catalogs (FTC)
> > > >with
> > > > a status of 'Recovering'.  If anyone can help me by responding to my
> > > > questions, I would greatly appreciate it.
> > > >
> > > > 1. How does a FTC get a status of 'Recovering'?
> > > > 2. What implication does this status have on the FTC?
> > > > 3. What is happening to the catalog while it is being recovered?
> > > >
> > > > Pretty much I'm looking for any information I can find, so any
> > > > comments/links that would help me understand what is occurring are
> > > > welcomed.
> > > >
> > > > Thanks,
> > > >
> > >
> > >
> > >

> Here is the Gatherer log info:
>
> SQL0008700005.3.gthr:
> Microsoft (R) Windows Script Host Version 5.6
> Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
>
> 10/18/2006 11:18:16 AM        Add    The gatherer has started
> 10/18/2006 11:43:26 AM        Add    The recovery has completed
> 10/18/2006 3:16:10 PM        Add    The gatherer has started
> 10/18/2006 3:36:34 PM        Add    The recovery has completed
>
> SQL0008700006.3.gthr:
> Microsoft (R) Windows Script Host Version 5.6
> Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
>
> 10/18/2006 11:18:16 AM        Add    The gatherer has started
> 10/18/2006 1:14:08 PM        Add    The recovery has completed
> 10/18/2006 3:16:10 PM        Add    The gatherer has started
>
> SQL0008700006.2.gthr: (the end of another gatherer log)
> 10/17/2006 6:20:36 PM    MSSQL75://SQLServer/47dbae45/0005EF0D    Add    Error
> fetching URL, (80041812 - Content Index has been shutdown.  )
> 10/17/2006 6:20:36 PM    MSSQL75://SQLServer/151b244e/000DF6BD    Add    Error
> fetching URL, (80041812 - Content Index has been shutdown.  )
>
> Thanks,
>
> "robcam817" wrote:
>
> > Hilary,
> >
> > Thank you very much for responding to my post.  I had an issue the other day
> > where the drive containing the FTData folder ran out of space which caused
> > the mssearch service to lock up.  I stopped the service and freed up some
> > space on the drive and started the service again.  When I restarted the
> > catalog went into a 'recovering' status.  Here are some log entries from this
> > issue:
> >
> > Event Type:    Error
> > Event Source:    Microsoft Search
> > Event Category:    Indexer
> > Event ID:    7010
> > Date:        10/17/2006
> > Time:        3:08:20 PM
> > User:        N/A
> > Computer:    [server]
> > Description:
> > The project <SQLServer SQL0008700005> cannot be initialized. Error: 80041828
> > - The disk has reached its configured space limit.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> > Event Type:    Error
> > Event Source:    Microsoft Search
> > Event Category:    Gatherer
> > Event ID:    3010
> > Date:        10/17/2006
> > Time:        12:52:31 AM
> > User:        N/A
> > Computer:    ANNRS100UT06
> > Description:
> > The transaction cannot be appended to the project <SQLServer SQL0008700006>
> > queue. File: e:\MSSQL\FTData\SQL0008700006\SQL0008700006.Ntfy1.gthr. Error:
> > 80070070 - There is not enough space on the disk.  .
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > Event Type:    Failure Audit
> > Event Source:    MssCi
> > Event Category:    None
> > Event ID:    4133
> > Date:        10/17/2006
> > Time:        12:50:35 AM
> > User:        N/A
> > Computer:    [server]
> > Description:
> > Very low disk space was detected on drive
> > e:\mssql\ftdata\sql0008700005\build\indexer\cifiles. Please free up at least
> > 24MB of space for content index to continue.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > Here are some additional errors from the Application Log that I saw today
> > after I stopped and startded the MSSEARSH process for some testing: (i have
> > also included some gatherer logs entries below)
> >
> > Event Type:    Error
> > Event Source:    Microsoft Search
> > Event Category:    Gatherer
> > Event ID:    3013
> > Date:        10/17/2006
> > Time:        6:20:34 PM
> > User:        N/A
> > Computer:    [server]
> > Description:
> > The entry <MSSQL75://SQLSERVER/778AC167/006CFFA6> in the hash map on project
> > <SQLServer SQL0008700005> cannot be updated. Error: 8007054e - Unable to
> > complete the requested operation because of either a catastrophic media
> > failure or a data structure corruption on the disk.  .
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> > Event Type:    Warning
> > Event Source:    Microsoft Search
> > Event Category:    Gatherer
> > Event ID:    3035
> > Date:        10/17/2006
> > Time:        6:20:34 PM
> > User:        N/A
> > Computer:    [server]
> > Description:
> > One or more warnings or errors for Gatherer project <SQLServer
> > SQL0008700006> were logged to file <C:\Program Files\Microsoft SQL
> > Server\MSSQL\FTData\SQLServer\GatherLogs\SQL0008700006.2.gthr>. If you are
> > interested in these messages, please, look at the file using the gatherer log
> > query object (gthrlog.vbs, log viewer web page).
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> > Event Type:    Error
> > Event Source:    Application Error
> > Event Category:    (100)
> > Event ID:    1000
> > Date:        10/17/2006
> > Time:        6:20:20 PM
> > User:        N/A
> > Computer:    ANNRS100UT06
> > Description:
> > Faulting application mssearch.exe, version 9.107.8320.9, faulting module
> > unknown, version 0.0.0.0, fault address 0x00000003.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 41 70 70 6c 69 63 61 74   Applicat
> > 0008: 69 6f 6e 20 46 61 69 6c   ion Fail
> > 0010: 75 72 65 20 20 6d 73 73   ure  mss
> > 0018: 65 61 72 63 68 2e 65 78   earch.ex
> > 0020: 65 20 39 2e 31 30 37 2e   e 9.107.
> > 0028: 38 33 32 30 2e 39 20 69   8320.9 i
> > 0030: 6e 20 75 6e 6b 6e 6f 77   n unknow
> > 0038: 6e 20 30 2e 30 2e 30 2e   n 0.0.0.
> > 0040: 30 20 61 74 20 6f 66 66   0 at off
> > 0048: 73 65 74 20 30 30 30 30   set 0000
> > 0050: 30 30 30 33               0003
> >
> > My main objective for the post was to find out what is happening to the
> > index when it is recovering.  I have a general idea of what causes the
> > catalog to need to be recovered, but I wanted to know how ling it takes for
> > the recovery too.  I am rebuilding some catalogs on a remote server and then
> > moving them back and I wanted to know if they will go thorugh the recovery
> > process an how long I can expect it to take or at least how I can estimate
> > how long it will take.
> >
> > Additionally, here is the @@versino for the server:
> > Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)   May  3 2005 23:18:38
> > Copyright (c) 1988-2003 Microsoft Corporation  Developer Edition on Windows
> > NT 5.2 (Build 3790: Service Pack 1)
> >
> > Thank you for your help...
> > Dan
> >
> > "Hilary Cotter" wrote:
> >
> > > Like a database the full-text catalogs are transactional in nature. It can
> > > be in the recovering state after an abrupt power off which will force a
> > > consistency check when it is launched. Check the event log to see if there
> > > are any messages from MSSCI or MSSearch which are relevant to this error.
> > >
> > > --
> > > Hilary Cotter
> > > Director of Text Mining and Database Strategy
> > > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> > >
> > > This posting is my own and doesn't necessarily represent RelevantNoise's
> > > positions, strategies or opinions.
> > >
> > > 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
> > >
> > >
> > >
> > > "robcam817" <robcam***@discussions.microsoft.com> wrote in message
> > > news:7F3703C9-E9E4-4AB0-9D84-F29A74DBED9E@microsoft.com...
> > > >I have not been able to find any information on Full Text Catalogs (FTC)
> > > >with
> > > > a status of 'Recovering'.  If anyone can help me by responding to my
> > > > questions, I would greatly appreciate it.
> > > >
> > > > 1. How does a FTC get a status of 'Recovering'?
> > > > 2. What implication does this status have on the FTC?
> > > > 3. What is happening to the catalog while it is being recovered?
> > > >
> > > > Pretty much I'm looking for any information I can find, so any
> > > > comments/links that would help me understand what is occurring are
> > > > welcomed.
> > > >
> > > > Thanks,
> > > >
> > >
> > >
> > >