Monday, March 26, 2012

I can't seem to access my fulltext data

I am running on Sql Server 2000.
This was set up a couple of weeks ago and ran fine. I came in today and was
looking at some of my asp.net pages and started to get the error:
Execution of a full-text operation failed. The catalog does not exist or is
currently unavailable
I tried just a simple query:
select * from position where Contains(jobDescription,'sales')
and got the same error.
What causes the problem? When I right-click on the table and go the
fulltext menu and wizard, it says it is already set up for FullText
indexing.
Thanks,
Tom
Can you check for any messages in the event log from MSSearch or MSSCI?
You might also want to use the gthrlog.vbs to examine your gatherer logs for
this catalog.
Go to c:\program files\Common files\system\mssearch\bin copy the gthrlog.vbs
to c:\winnt\system32 directory or add the above path to your
path (control panel - system - Environment - user and in the path variable
append the above path in the path value (separate it from the entry before
with a ;).
Click on set, apply and OK. Run path from the command prompt to ensure you
did this correctly. You may have to close down all dos boxes to get this to
update
correctly, if not a log off log on normally works.
Now navigate to your gather log location. On my machine it is at
C:\Program Files\Microsoft SQL Server\MSSQL\FTDATA\SQLServer\XGatherLogs>
then type cscript.vbs gthrlog SQL0000600006.7.gthr or whatever you find
there.
these logs have time stamps on them, look for a date relevant one to
examine.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"tshad" <tscheiderich@.ftsolutions.com> wrote in message
news:eeSITHLMFHA.3016@.TK2MSFTNGP15.phx.gbl...
> I am running on Sql Server 2000.
> This was set up a couple of weeks ago and ran fine. I came in today and
was
> looking at some of my asp.net pages and started to get the error:
> Execution of a full-text operation failed. The catalog does not exist or
is
> currently unavailable
> I tried just a simple query:
> select * from position where Contains(jobDescription,'sales')
> and got the same error.
> What causes the problem? When I right-click on the table and go the
> fulltext menu and wizard, it says it is already set up for FullText
> indexing.
> Thanks,
> Tom
>
>
|||> Can you check for any messages in the event log from MSSearch or MSSCI?
> You might also want to use the gthrlog.vbs to examine your gatherer logs
> for
> this catalog.
> Go to c:\program files\Common files\system\mssearch\bin copy the
> gthrlog.vbs
> to c:\winnt\system32 directory or add the above path to your
> path (control panel - system - Environment - user and in the path variable
> append the above path in the path value (separate it from the entry before
> with a ;).
> Click on set, apply and OK. Run path from the command prompt to ensure you
> did this correctly. You may have to close down all dos boxes to get this
> to
> update
> correctly, if not a log off log on normally works.
> Now navigate to your gather log location. On my machine it is at
>
> C:\Program Files\Microsoft SQL Server\MSSQL\FTDATA\SQLServer\XGatherLogs>
>
> then type cscript.vbs gthrlog SQL0000600006.7.gthr or whatever you find
> there.
> these logs have time stamps on them, look for a date relevant one to
> examine.
We don't have cscript.vbs on our server which is a "Windows 2003 Server".
But the date of the only file in the GatherLogs folder is 3/15/05 and this
happened today.
There is no entry in the Event log or the Sql Server Logs about this
either - the last entry was 2:00 am this morning for our backups.
However, I did look at the FullTextCatalogs in the Databases folder on EM
and saw that the JobDescriptions Catalog is idle. Is this normal?
Thanks,
Tom
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "tshad" <tscheiderich@.ftsolutions.com> wrote in message
> news:eeSITHLMFHA.3016@.TK2MSFTNGP15.phx.gbl...
> was
> is
>
|||Possibly, can you try to run a full population.
Btw its cscript gthrlog SQL0000600006.7.gthr
My mistake
"tshad" <tscheiderich@.ftsolutions.com> wrote in message
news:e$rh5NMMFHA.3960@.TK2MSFTNGP12.phx.gbl...
> We don't have cscript.vbs on our server which is a "Windows 2003 Server".
> But the date of the only file in the GatherLogs folder is 3/15/05 and this
> happened today.
> There is no entry in the Event log or the Sql Server Logs about this
> either - the last entry was 2:00 am this morning for our backups.
> However, I did look at the FullTextCatalogs in the Databases folder on EM
> and saw that the JobDescriptions Catalog is idle. Is this normal?
> Thanks,
> Tom
>
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uiDrhnMMFHA.4044@.TK2MSFTNGP12.phx.gbl...
> Possibly, can you try to run a full population.
I did try the full population, but that didn't seem to help. But when I did
a rebuild catalog and then full population it worked fine.
Why would it do that and how would I get around that?
I can't have people trying to use our site and finding that their searches
won't work.
Thanks,
Tom
> Btw its cscript gthrlog SQL0000600006.7.gthr
> My mistake
>
> "tshad" <tscheiderich@.ftsolutions.com> wrote in message
> news:e$rh5NMMFHA.3960@.TK2MSFTNGP12.phx.gbl...
>
|||Its hard to say - their may have been some catalog corruption, but there
should have been error messages logged in the event log, or in the gatherer
logs.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"tshad" <tscheiderich@.ftsolutions.com> wrote in message
news:e26H3zMMFHA.3760@.TK2MSFTNGP12.phx.gbl...
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uiDrhnMMFHA.4044@.TK2MSFTNGP12.phx.gbl...
> I did try the full population, but that didn't seem to help. But when I
did[vbcol=seagreen]
> a rebuild catalog and then full population it worked fine.
> Why would it do that and how would I get around that?
> I can't have people trying to use our site and finding that their searches
> won't work.
> Thanks,
> Tom
MSSCI?[vbcol=seagreen]
logs[vbcol=seagreen]
find[vbcol=seagreen]
Server".[vbcol=seagreen]
EM
>
|||Hilary,
I have had a similiar issue; I cannot read any of my data from a simple
query or returning all rows from SQL. I tried to reinstal my *.dll files for
MSSearch, to no avail.
I am running Server 2003, SQL 2000 sp3.
Any help would be appreciated.
Derek
"Hilary Cotter" wrote:

> Its hard to say - their may have been some catalog corruption, but there
> should have been error messages logged in the event log, or in the gatherer
> logs.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "tshad" <tscheiderich@.ftsolutions.com> wrote in message
> news:e26H3zMMFHA.3760@.TK2MSFTNGP12.phx.gbl...
> did
> MSSCI?
> logs
> find
> Server".
> EM
>
>
|||Its difficult to assess what the problem could be. Could you check the event
log from messages coming from MSSearch or MSSCi? This might refer to your
gatherer logs, which can be accessed by using the gthrlog.vbs utility.
go to c:\program files\Common files\system\mssearch\bin, copy the
gthrlog.vbs to c:\winnt\system32 directory or add the above path to your
path (control panel - system - Environment - user and in the path variable
append the above path in the path value (separate it from the entry before
with a ;).
Click on set, apply and OK. Run path from the command prompt to ensure you
did this correctly. You may have to close down all dos boxes to get this to
update
correctly, if not a log off log on normally works.
Now navigate to your gather log location. On my machine it is at C:\Program
Files\Microsoft SQL Server\MSSQL\FTDATA\SQLServer\XGatherLogs
then type cscript.vbs gthrlog SQL0000600006.7.gthr or whatever you find
there. these logs have time stamps on them, look for a date relevant one
to examine.
The most common reason for such a failure is the the SQL Server Service
account was changed through control panel as opposed to through EM. Refer to
this kb article for more information.
http://support.microsoft.com/default...b;en-us;295034
http://support.microsoft.com/default...b;en-us;317746
http://support.microsoft.com/default...b;en-us;295772
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"dkoz" <dkoz@.discussions.microsoft.com> wrote in message
news:D0FA563F-B9B0-4ABF-887B-DEA64EE7DDE9@.microsoft.com...
> Hilary,
> I have had a similiar issue; I cannot read any of my data from a simple
> query or returning all rows from SQL. I tried to reinstal my *.dll files
for[vbcol=seagreen]
> MSSearch, to no avail.
> I am running Server 2003, SQL 2000 sp3.
> Any help would be appreciated.
> Derek
> "Hilary Cotter" wrote:
gatherer[vbcol=seagreen]
I[vbcol=seagreen]
searches[vbcol=seagreen]
gatherer[vbcol=seagreen]
entry[vbcol=seagreen]
ensure[vbcol=seagreen]
get[vbcol=seagreen]
to[vbcol=seagreen]
and[vbcol=seagreen]
this[vbcol=seagreen]
on[vbcol=seagreen]
today[vbcol=seagreen]
exist[vbcol=seagreen]
the[vbcol=seagreen]
FullText[vbcol=seagreen]

No comments:

Post a Comment