Hi
we are using merge replication with anonymous subscription.
- Window 2000 and sql 2000 server (publisher and distributor)
- MSDE 2000 subscriber.
- using Active X-Control for subscription
-I have put subscriber never expire option in the property of
publisher.
Replication running without any problem in normal case but we received
some problem on the following scenario:
-I set up the subscriber call "TEST01" and synchronize it it run
without any problem. Because of some other reasons I need to change
the name of the computer, after that when I synchronize it does not
work, even if I change back the computer name to the original name it
stop working how can I fix this problem.
-If I want to delete the subscription total and generate the new one
how can I do this. I try to delete the subscription from the
publisher, distributor and delete the subscriber database for the
subscriber and create new database in subscriber, and click
synchronize, it still doesn't work- how can I solve this problem.
-What is different way of deleting the subscription if they are never
expiring in the publication property?
-Actually I try to do all of these above steps in our test
environment, it still give different error message.
-"The merge process could not able to drop the pull subscription form
"sesc-07" (which is server).
-"The remote server is not defined as a subscriber". I change and make
it as subscriber also but still same message.
- "The merge process could not update the last sent generation"
I will be greatful for the information.
Thanks in advance.
Indra.
can any subscriber pull the subscription from the publisher?
What server name did you change? the publisher or the subscriber?
Can you issue this query on the subscriber
select @.@.servername
master.dbo.xp_cmdshell 'hostname'
master.dbo.xp_cmdshell 'echo %computername%'
and post the results back here?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Indra" <itimilsina@.savannaenergy.com> wrote in message
news:e667cf1e.0409010742.1baee732@.posting.google.c om...
> Hi
> we are using merge replication with anonymous subscription.
> - Window 2000 and sql 2000 server (publisher and distributor)
> - MSDE 2000 subscriber.
> - using Active X-Control for subscription
> - I have put subscriber never expire option in the property of
> publisher.
> Replication running without any problem in normal case but we received
> some problem on the following scenario:
> - I set up the subscriber call "TEST01" and synchronize it - it run
> without any problem. Because of some other reasons I need to change
> the name of the computer, after that when I synchronize it does not
> work, even if I change back the computer name to the original name it
> stop working - how can I fix this problem.
> - If I want to delete the subscription total and generate the new one
> how can I do this. I try to delete the subscription from the
> publisher, distributor and delete the subscriber database for the
> subscriber and create new database in subscriber, and click
> synchronize, it still doesn't work- how can I solve this problem.
> - What is different way of deleting the subscription if they are never
> expiring in the publication property?
> - Actually I try to do all of these above steps in our test
> environment, it still give different error message.
> -"The merge process could not able to drop the pull subscription form
> "sesc-07" (which is server).
> -"The remote server is not defined as a subscriber". I change and make
> it as subscriber also but still same message.
> - "The merge process could not update the last sent generation"
> I will be greatful for the information.
> Thanks in advance.
> Indra.
|||Hi Hilary,
All the subscriber runing fine except those whoes computer name
(subscriber computer name) has been change.
we change the name of the subscriber not the publisher.
Our subscriber is runing on MSDE 2000, so how can i run that sql script
on MSDE?.
select @.@.servername
master.dbo.xp_cmdshell 'hostname'
master.dbo.xp_cmdshell 'echo %computername%'
CAN I RUN THIS ON PUBLISHER.
none of the subscriber are register on server becuase i am usign
anonymous subscribtion.
Thanks.
Indra.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Saturday, February 25, 2012
Looking for information
I'm looking for books or information on command line configuration of settings for things like activating Remote Connections under the Service Area Configuration and setting a port for that connection.
What books would be good to get or where can I download papers on this?
Any help would be appreciated.
I'd say the best place to start would be SQL Books Online, http://msdn2.microsoft.com, or you can download them from the Microsoft Download Center, http://www.microsoft.com/downloads.
You can run command line configuration through the SACUtility, check out the BOL topic at http://msdn2.microsoft.com/en-us/library/ms162800.aspx.
I don't have any personal recomendations for books you can read, but a quick search gave me Microsoft SQL Server 2005 Administrator's Pocket Consultant from MS Press (http://www.microsoft.com/MSPress/books/6794.asp). Probably a bunch of interesting things in there. It mentions having a section on Install, configure and tune SQL Server.
Hope this helps.
Mike Wachal
SQL Express team
Looking for Info on Full Text Catalogs with a 'Recovering' Status
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,
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" <robcam817@.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,
>
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,
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" <robcam817@.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,
>
Looking for Info on Full Text Catalogs with a 'Recovering' Status
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,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" <robcam817@.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,
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" <robcam817@.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" <robcam817@.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,
> > >
> >
> >
> >|||Rob, you have disk space issues. free up disk space on your system
drive and the drives where your catalogs are stored.
robcam817 wrote:
> 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" <robcam817@.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,
> > > >
> > >
> > >
> > >|||Rob, you have disk space issues. free up disk space on your system
drive and the drives where your catalogs are stored.
robcam817 wrote:
> 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" <robcam817@.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,
> > > >
> > >
> > >
> > >
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,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" <robcam817@.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,
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" <robcam817@.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" <robcam817@.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,
> > >
> >
> >
> >|||Rob, you have disk space issues. free up disk space on your system
drive and the drives where your catalogs are stored.
robcam817 wrote:
> 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" <robcam817@.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,
> > > >
> > >
> > >
> > >|||Rob, you have disk space issues. free up disk space on your system
drive and the drives where your catalogs are stored.
robcam817 wrote:
> 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" <robcam817@.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,
> > > >
> > >
> > >
> > >
Looking for Info on Full Text Catalogs with a 'Recovering' Status
I have not been able to find any information on Full Text Catalogs (FTC) wit
h
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,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" <robcam817@.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,
>
h
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,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" <robcam817@.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,
>
Looking for ideas...
I have a text file that I am importing in a data flow task. Not all of the rows are the same, there are "header" rows that contain a company code.
What I want to do is keep that company code and append that to the row of text that I am writing to a CSV file.
Since you cannot change variables until the post execute, what are my options?
Hope that's clear
Thanks!
BobP
Are you writing a custom script component to handle this? You talk of not being able to change variables until post execute, just handle the locking yourself and you can as illustrated here - http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=956181&SiteID=1|||From your description, I assume you're trying to denormalize a multi-formatted text file by moving data from header rows to detail rows.Since your rows are not all the same, set your text file source component to read each line of the source file as a single column. Then write a custom script transformation component to consume that column, parse the data by row type, and output the individual columns that will be consumed by your destination (including the header columns). When the transformation encounters one of these header rows, put the parsed data (Company Code) into global variable(s) in the transformation component, and discard or redirect the header row. For each detail row, create a new output row and populate the "detail" columns from the parsed input data and the "header" column(s) (i.e. Company Code) from the the local variable(s). This way your header data is remembered for each subsequent detail row until another header is encountered.
Hope that helps.
Looking for ideas
Hi everyone
We've got currenlty around 500 dts 2000 in production.
In order to know in what ETL processes we have Oracle connections, or FTP tasks or whatever, we did a VB6 app using dtspkg.dll which load all the properties for each DTS into Sql server tables. So that, then you could see from a specific DTS how many connections, Sql Tasks it had and so on..
How to accomplish the same with SSIS? I know, doing the same but using .Net, of course, but is there any else approximation? I am little bit concerned when we will have hundreds of them up.
Maybe 2005 is offering this feature automatically, I don't know.
Thanks in advance for your time/advices/ideas,
Try this -
Download details: SQL Server 2005 Business Intelligence Metadata Samples Toolkit
(http://www.microsoft.com/downloads/details.aspx?FamilyID=11daa4d1-196d-4f2a-b18f-891579c364f4&DisplayLang=en)
Even if the tools are visualisation is not what you want, it will have populated some tables with details of packages and objects that you can probably use. And if that is still not good enough the source code included will give you a start in writing your own tool.
Subscribe to:
Comments (Atom)