Full text stuck in a rut - error msg 7619

I have a full-text index on a production db. The catalog is currently empty. When I try to populate it, I get a message saying I must enable full text for this database. When I try to run sp_fulltext_database 'enable', I get the following message:
Server: Msg 7619, Level 16, State 1, Procedure sp_fulltext_database, Line 61
Execution of a full-text operation failed. The process cannot access the file because it is being used by another process.
Our OS team could not find any processes other than sqlserver.exe using files in the FTData dir. MSSearch is currently owned by the localsystem account, and ownership has not been changed since the SQL Server install.
I am using SQL 2000 EE. on a Windows 2000 cluster. SP3A is installed.
Has anyone else come across this error? Any advice would be appreciated!

Quote:

Originally posted by lisanova22
I have a full-text index on a production db. The catalog is currently empty. When I try to populate it, I get a message saying I must enable full text for this database. When I try to run sp_fulltext_database 'enable', I get the following message:
Server: Msg 7619, Level 16, State 1, Procedure sp_fulltext_database, Line 61
Execution of a full-text operation failed. The process cannot access the file because it is being used by another process.
Our OS team could not find any processes other than sqlserver.exe using files in the FTData dir. MSSearch is currently owned by the localsystem account, and ownership has not been changed since the SQL Server install.
I am using SQL 2000 EE. on a Windows 2000 cluster. SP3A is installed.
Has anyone else come across this error? Any advice would be appreciated!

Full Text Search know which row has error in indexing

Hello everybody,
I have installed SQLServer 2005 for take advantage of full text seach
features.
When I start full population, there are some rows that cause error and not
are indexed.
I see the log in C:\Programmi\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\SQLFT0000700005.LOG. In this file there are seven
rows that have error and for everyone a line that say:
"Error '0x8004fd01: The IFilter::Init() function call failed.' ...
full-text key value 0x495532303045594154504B55. Attempt will be made to
reindex it. The component 'pdffilt.dll' reported error while indexing.
Component path 'C:\Programmi\Foxit Software\Foxit PDF IFilter\pdffilt.dll'."
With different full-text key value for every line.
My question is:
1) Start from a full-text key (ie. 0x495532303045594154504B55), how I arrive
to the record in the source table for understand which is the
problem?Otherwise how can I examine the problem if I don't know the row that
cause the error?
2) What is the error 0x8004fd01?
3) Could be that the PDF filter of Foxit is better than Adobe? With Adobe
filter (version 6) my full pupulation is endless!
Thanks!
OK resolved !!!
1)The hexadecimal value must to be converted to decimal and then to ASCII
(http://www.vortex.prodigynet.co.uk/misc/ascii_conv.html)
2) Probably due to the incorrect format because changing the type column
value from ".pdf" to ".txt" the problem has been resolved!!!
3) Wait your opinions :-)
NicolaZap
"NicolaZap" wrote:

> Hello everybody,
> I have installed SQLServer 2005 for take advantage of full text seach
> features.
> When I start full population, there are some rows that cause error and not
> are indexed.
> I see the log in C:\Programmi\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\SQLFT0000700005.LOG. In this file there are seven
> rows that have error and for everyone a line that say:
> "Error '0x8004fd01: The IFilter::Init() function call failed.' ...
> full-text key value 0x495532303045594154504B55. Attempt will be made to
> reindex it. The component 'pdffilt.dll' reported error while indexing.
> Component path 'C:\Programmi\Foxit Software\Foxit PDF IFilter\pdffilt.dll'."
> With different full-text key value for every line.
>
> My question is:
> 1) Start from a full-text key (ie. 0x495532303045594154504B55), how I arrive
> to the record in the source table for understand which is the
> problem?Otherwise how can I examine the problem if I don't know the row that
> cause the error?
> 2) What is the error 0x8004fd01?
> 3) Could be that the PDF filter of Foxit is better than Adobe? With Adobe
> filter (version 6) my full pupulation is endless!
>
> Thanks!
>
|||Is this the 64 bit version of SQL server? If so you should be using Foxit.
"NicolaZap" <NicolaZap@.discussions.microsoft.com> wrote in message
news:091F34B8-1140-4A74-9D2A-03F02B00DB8A@.microsoft.com...[vbcol=seagreen]
> OK resolved !!!
> 1)The hexadecimal value must to be converted to decimal and then to ASCII
> (http://www.vortex.prodigynet.co.uk/misc/ascii_conv.html)
> 2) Probably due to the incorrect format because changing the type column
> value from ".pdf" to ".txt" the problem has been resolved!!!
> 3) Wait your opinions :-)
>
> NicolaZap
>
> "NicolaZap" wrote:
|||NO, it is the 32 bit versione of SQLServer2005.
"Hilary Cotter" wrote:

> Is this the 64 bit version of SQL server? If so you should be using Foxit.
> "NicolaZap" <NicolaZap@.discussions.microsoft.com> wrote in message
> news:091F34B8-1140-4A74-9D2A-03F02B00DB8A@.microsoft.com...
>
>

Full Text Search know which row has error in indexing

Hello everybody,

I have installed SQLServer 2005 for take advantage of full text seach features.

When I start full population, there are some rows that cause error and not are indexed.

I see the log in C:\Programmi\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLFT0000700005.LOG. In this file there are seven rows that have error and for everyone a line that say:

"Error '0x8004fd01: The IFilter::Init() function call failed.' ... full-text key value 0x495532303045594154504B55. Attempt will be made to reindex it. The component 'pdffilt.dll' reported error while indexing. Component path 'C:\Programmi\Foxit Software\Foxit PDF IFilter\pdffilt.dll'."

With different full-text key value for every line.

My question is:

1) Start from a full-text key (ie. 0x495532303045594154504B55), how I arrive to the record in the source table for understand which is the problem?Otherwise how can I examine the problem if I don't know the row that cause the error?

2) What is the error 0x8004fd01?

3) Could be that the PDF filter of Foxit is better than Adobe? With Adobe filter (version 6) my full pupulation is endless!

Thanks!

OK resolved

1)The hexadecimal value must to be converted to decimal and then to ASCII (http://www.vortex.prodigynet.co.uk/misc/ascii_conv.html)

2) Probably due to the incorrect format because changing the type column value from ".pdf" to ".txt" the problem has been resolved!!!

3) Wait your opinions :-)

NicolaZap

full text search error - catalogue does not exist

Hi guys, I sent the following queries to my DB and they seem to work with success messages after each line but when I try to test it I get the message at the bottom. Any ideas? there's a good chance my test sql is all wrong!

sp_fulltext_database 'enable'

sp_fulltext_catalog 'Fulltextcatalog1','create'

sp_fulltext_table 'test','create','Fulltextcatalog1','PK_test'

sp_fulltext_column 'test','text','add'

sp_fulltext_table 'test','activate'

sp_fulltext_table 'test','start_full'

sp_fulltext_table test, 'Start_change_tracking'

sp_fulltext_table test, 'Start_background_updateindex'

-- now test it --

SELECT * FROM test WHERE FREETEXT(*,'spotless')

gets this result:
Error -2147217900
Execution of a full-text operation failed. The catalog does not exist or is currently unavailable. Please retry the action again later and if this symptom persists, contact the system administrator.Just tried this (where my field name is 'text' and my table is called 'test') but get the same catalogue error
SELECT * FROM test WHERE CONTAINS(text,'spotless')

Full Text Repair

We had a customer request a full text installation after
the application of SP4 and the slammer hotfix. It throws
an error that refers to a re-installation of SP4, which
will not work with any hot fixes applied after the fact.
Does anyone have a different route to follow that
uninstall the hotfix, then reapply the SP4, and then
reapply the hot fix?
Thanks in advance for any information.
Emil
what is the exact error message you are getting?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Emil" <emilcaruthers@.hotmail.com> wrote in message
news:698301c4758b$4e941cd0$a301280a@.phx.gbl...
> We had a customer request a full text installation after
> the application of SP4 and the slammer hotfix. It throws
> an error that refers to a re-installation of SP4, which
> will not work with any hot fixes applied after the fact.
> Does anyone have a different route to follow that
> uninstall the hotfix, then reapply the SP4, and then
> reapply the hot fix?
> Thanks in advance for any information.
> Emil
|||use culture;
SELECT * from FREETEXTTABLE(tblMasterEvents,*,'art');
Get this:
Search on full-text catalog 'culture' for database ID 41, table ID
1381579960 with search condition 'art' failed with unknown result (565f9c4).
The name of the database is not relevant, as all return the error.
Thanks for looking.
Emil Caruthers
"Hilary Cotter" wrote:

> what is the exact error message you are getting?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Emil" <emilcaruthers@.hotmail.com> wrote in message
> news:698301c4758b$4e941cd0$a301280a@.phx.gbl...
>
>
|||Emil,
Since your customer has already applied SP4, I'm assuming that this is a SQL
Server 7.0 installation as there currently is no publicly released SP4 for
SQL Sever 2000.
For SQL Server 7.0 installations, there is a registry key and value that you
can change in order to successfully re-install SP4 after applying a post-SP4
hotfix. Specifically, registry key called
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQL Server\Current Version\
"CSDVersion"
It will contain your hotfix build version number such that 7.00.xxx is the
build number. Record this value and then change it to the SP4 build value of
7.00.1063 and then re-install SP4. If successful, then re-install your
hotfix and confirm that this registry key value has changed back to your
recorded hotfix build number.
BTW, the hex value in the unknown result below is a 'garbage' value as this
is a bug with SQL Server 7.0 FTS and is fixed by applying (or re-applying)
the latest service pack.
Regards,
John
"Emil" <Emil@.discussions.microsoft.com> wrote in message
news:76173F35-121A-4ED7-852F-3328824CEC69@.microsoft.com...
> use culture;
> SELECT * from FREETEXTTABLE(tblMasterEvents,*,'art');
> Get this:
> Search on full-text catalog 'culture' for database ID 41, table ID
> 1381579960 with search condition 'art' failed with unknown result
(565f9c4).[vbcol=seagreen]
>
> The name of the database is not relevant, as all return the error.
> Thanks for looking.
> --
> Emil Caruthers
>
> "Hilary Cotter" wrote:
|||Thank you kindly, and I will try this.
Emil
Emil Caruthers
"John Kane" wrote:

> Emil,
> Since your customer has already applied SP4, I'm assuming that this is a SQL
> Server 7.0 installation as there currently is no publicly released SP4 for
> SQL Sever 2000.
> For SQL Server 7.0 installations, there is a registry key and value that you
> can change in order to successfully re-install SP4 after applying a post-SP4
> hotfix. Specifically, registry key called
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQL Server\Current Version\
> "CSDVersion"
> It will contain your hotfix build version number such that 7.00.xxx is the
> build number. Record this value and then change it to the SP4 build value of
> 7.00.1063 and then re-install SP4. If successful, then re-install your
> hotfix and confirm that this registry key value has changed back to your
> recorded hotfix build number.
> BTW, the hex value in the unknown result below is a 'garbage' value as this
> is a bug with SQL Server 7.0 FTS and is fixed by applying (or re-applying)
> the latest service pack.
> Regards,
> John
>
> "Emil" <Emil@.discussions.microsoft.com> wrote in message
> news:76173F35-121A-4ED7-852F-3328824CEC69@.microsoft.com...
> (565f9c4).
>
>

Full Text not working

I cannot get fulltext indexing to work, nor can I get any error messages to
indicate whats wrong. Here's what I did (for the pubs database)
1. From the top menu, select Tools, Full Text Indexing.
2. Click next on the opening screen.
3. On the "Select a Database" screen, choose pubs.
4. For the next screen, select "titles" as the table and click next.
5. Keep the default unique index; there is only one on the pubs table.
6. In the next screen, select Title and Notes as the fields to be indexed.
7. On the "Select a Catalog" screen, because this is the first Catalog on
the server, we are prompted for a name. In this example, "demo" is used as
the Catalog name.
8. Click next.
9. Click Finish.
10. From Enterprise Manager, expand Full-Text Catalogs
11. Right click and select "Start Full Population."
12. The catalog is now complete.
If I type sp_help_fulltext_catalogs everything looks ok.
If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
I get a 1 which means ok.
If I type
SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
I get 0 rows
Same if I enter
SELECT title, notes
FROM titles
--where notes like '%quick%'
WHERE CONTAINS (notes, ' quick ')
of course entering
SELECT title, notes
FROM titles
where notes like '%quick%'
gets me the record I want. Anyone have any ideas what I can check?
BTW I did this on another server and it works. The server is works is using
SQL Server developer edition. The server that doesn't work is my production
box using SQL Server standard edition
Thanks for the help.
Francis,
Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
the item listed...might compare with CONTAINS in SQL BOL...same SP?
HTH
Jerry
"Francis" <Francis@.discussions.microsoft.com> wrote in message
news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
>I cannot get fulltext indexing to work, nor can I get any error messages to
> indicate whats wrong. Here's what I did (for the pubs database)
> 1. From the top menu, select Tools, Full Text Indexing.
> 2. Click next on the opening screen.
> 3. On the "Select a Database" screen, choose pubs.
> 4. For the next screen, select "titles" as the table and click next.
> 5. Keep the default unique index; there is only one on the pubs table.
> 6. In the next screen, select Title and Notes as the fields to be
> indexed.
> 7. On the "Select a Catalog" screen, because this is the first Catalog on
> the server, we are prompted for a name. In this example, "demo" is used as
> the Catalog name.
> 8. Click next.
> 9. Click Finish.
> 10. From Enterprise Manager, expand Full-Text Catalogs
> 11. Right click and select "Start Full Population."
> 12. The catalog is now complete.
> If I type sp_help_fulltext_catalogs everything looks ok.
> If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
> I get a 1 which means ok.
> If I type
> SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
> I get 0 rows
> Same if I enter
>
> SELECT title, notes
> FROM titles
> --where notes like '%quick%'
> WHERE CONTAINS (notes, ' quick ')
>
> of course entering
>
> SELECT title, notes
> FROM titles
> where notes like '%quick%'
>
> gets me the record I want. Anyone have any ideas what I can check?
>
> BTW I did this on another server and it works. The server is works is
> using
> SQL Server developer edition. The server that doesn't work is my
> production
> box using SQL Server standard edition
> Thanks for the help.
>
>
>
|||Thanks Jerry. I have tried various combinations like
SELECT title, notes
FROM titles
WHERE CONTAINS (notes, 'quick')
or using double quotes with spaces in front of and behind the work quick.
I have also set up other full text indexes on this and other tables and other
databases on this server and it doesn't seem to work.
"Jerry Spivey" wrote:

> Francis,
> Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
> the item listed...might compare with CONTAINS in SQL BOL...same SP?
> HTH
> Jerry
> "Francis" <Francis@.discussions.microsoft.com> wrote in message
> news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
>
>
|||Thanks for the help. I found the problem in KB317746;
I executed the workaround described:
EXEC sp_grantlogin [NT Authority\System]
EXEC sp_addsrvrolemember @.loginame = [NT Authority\System]
, @.rolename = 'sysadmin'
and all is well now.
"Francis" wrote:
[vbcol=seagreen]
> Thanks Jerry. I have tried various combinations like
> SELECT title, notes
> FROM titles
> WHERE CONTAINS (notes, 'quick')
> or using double quotes with spaces in front of and behind the work quick.
> I have also set up other full text indexes on this and other tables and other
> databases on this server and it doesn't seem to work.
>
> "Jerry Spivey" wrote:

Full Text not working

I cannot get fulltext indexing to work, nor can I get any error messages to
indicate whats wrong. Here's what I did (for the pubs database)
1. From the top menu, select Tools, Full Text Indexing.
2. Click next on the opening screen.
3. On the "Select a Database" screen, choose pubs.
4. For the next screen, select "titles" as the table and click next.
5. Keep the default unique index; there is only one on the pubs table.
6. In the next screen, select Title and Notes as the fields to be indexed.
7. On the "Select a Catalog" screen, because this is the first Catalog on
the server, we are prompted for a name. In this example, "demo" is used as
the Catalog name.
8. Click next.
9. Click Finish.
10. From Enterprise Manager, expand Full-Text Catalogs
11. Right click and select "Start Full Population."
12. The catalog is now complete.
If I type sp_help_fulltext_catalogs everything looks ok.
If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
I get a 1 which means ok.
If I type
SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
I get 0 rows
Same if I enter
SELECT title, notes
FROM titles
--where notes like '%quick%'
WHERE CONTAINS (notes, ' quick ')
of course entering
SELECT title, notes
FROM titles
where notes like '%quick%'
gets me the record I want. Anyone have any ideas what I can check?
BTW I did this on another server and it works. The server is works is using
SQL Server developer edition. The server that doesn't work is my production
box using SQL Server standard edition
Thanks for the help.Francis,
Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
the item listed...might compare with CONTAINS in SQL BOL...same SP?
HTH
Jerry
"Francis" <Francis@.discussions.microsoft.com> wrote in message
news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
>I cannot get fulltext indexing to work, nor can I get any error messages to
> indicate whats wrong. Here's what I did (for the pubs database)
> 1. From the top menu, select Tools, Full Text Indexing.
> 2. Click next on the opening screen.
> 3. On the "Select a Database" screen, choose pubs.
> 4. For the next screen, select "titles" as the table and click next.
> 5. Keep the default unique index; there is only one on the pubs table.
> 6. In the next screen, select Title and Notes as the fields to be
> indexed.
> 7. On the "Select a Catalog" screen, because this is the first Catalog on
> the server, we are prompted for a name. In this example, "demo" is used as
> the Catalog name.
> 8. Click next.
> 9. Click Finish.
> 10. From Enterprise Manager, expand Full-Text Catalogs
> 11. Right click and select "Start Full Population."
> 12. The catalog is now complete.
> If I type sp_help_fulltext_catalogs everything looks ok.
> If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
> I get a 1 which means ok.
> If I type
> SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
> I get 0 rows
> Same if I enter
>
> SELECT title, notes
> FROM titles
> --where notes like '%quick%'
> WHERE CONTAINS (notes, ' quick ')
>
> of course entering
>
> SELECT title, notes
> FROM titles
> where notes like '%quick%'
>
> gets me the record I want. Anyone have any ideas what I can check?
>
> BTW I did this on another server and it works. The server is works is
> using
> SQL Server developer edition. The server that doesn't work is my
> production
> box using SQL Server standard edition
> Thanks for the help.
>
>
>|||Thanks Jerry. I have tried various combinations like
SELECT title, notes
FROM titles
WHERE CONTAINS (notes, 'quick')
or using double quotes with spaces in front of and behind the work quick.
I have also set up other full text indexes on this and other tables and othe
r
databases on this server and it doesn't seem to work.
"Jerry Spivey" wrote:

> Francis,
> Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
> the item listed...might compare with CONTAINS in SQL BOL...same SP?
> HTH
> Jerry
> "Francis" <Francis@.discussions.microsoft.com> wrote in message
> news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
>
>|||Thanks for the help. I found the problem in KB317746;
I executed the workaround described:
EXEC sp_grantlogin [NT Authority\System]
EXEC sp_addsrvrolemember @.loginame = [NT Authority\System]
, @.rolename = 'sysadmin'
and all is well now.
"Francis" wrote:
[vbcol=seagreen]
> Thanks Jerry. I have tried various combinations like
> SELECT title, notes
> FROM titles
> WHERE CONTAINS (notes, 'quick')
> or using double quotes with spaces in front of and behind the work quick.
> I have also set up other full text indexes on this and other tables and ot
her
> databases on this server and it doesn't seem to work.
>
> "Jerry Spivey" wrote:
>

Full Text not working

I cannot get fulltext indexing to work, nor can I get any error messages to
indicate whats wrong. Here's what I did (for the pubs database)
1. From the top menu, select Tools, Full Text Indexing.
2. Click next on the opening screen.
3. On the "Select a Database" screen, choose pubs.
4. For the next screen, select "titles" as the table and click next.
5. Keep the default unique index; there is only one on the pubs table.
6. In the next screen, select Title and Notes as the fields to be indexed.
7. On the "Select a Catalog" screen, because this is the first Catalog on
the server, we are prompted for a name. In this example, "demo" is used as
the Catalog name.
8. Click next.
9. Click Finish.
10. From Enterprise Manager, expand Full-Text Catalogs
11. Right click and select "Start Full Population."
12. The catalog is now complete.
If I type sp_help_fulltext_catalogs everything looks ok.
If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
I get a 1 which means ok.
If I type
SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
I get 0 rows
Same if I enter
SELECT title, notes
FROM titles
--where notes like '%quick%'
WHERE CONTAINS (notes, ' quick ')
of course entering
SELECT title, notes
FROM titles
where notes like '%quick%'
gets me the record I want. Anyone have any ideas what I can check?
BTW I did this on another server and it works. The server is works is using
SQL Server developer edition. The server that doesn't work is my production
box using SQL Server standard edition
Thanks for the help.Francis,
Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
the item listed...might compare with CONTAINS in SQL BOL...same SP?
HTH
Jerry
"Francis" <Francis@.discussions.microsoft.com> wrote in message
news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
>I cannot get fulltext indexing to work, nor can I get any error messages to
> indicate whats wrong. Here's what I did (for the pubs database)
> 1. From the top menu, select Tools, Full Text Indexing.
> 2. Click next on the opening screen.
> 3. On the "Select a Database" screen, choose pubs.
> 4. For the next screen, select "titles" as the table and click next.
> 5. Keep the default unique index; there is only one on the pubs table.
> 6. In the next screen, select Title and Notes as the fields to be
> indexed.
> 7. On the "Select a Catalog" screen, because this is the first Catalog on
> the server, we are prompted for a name. In this example, "demo" is used as
> the Catalog name.
> 8. Click next.
> 9. Click Finish.
> 10. From Enterprise Manager, expand Full-Text Catalogs
> 11. Right click and select "Start Full Population."
> 12. The catalog is now complete.
> If I type sp_help_fulltext_catalogs everything looks ok.
> If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
> I get a 1 which means ok.
> If I type
> SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
> I get 0 rows
> Same if I enter
>
> SELECT title, notes
> FROM titles
> --where notes like '%quick%'
> WHERE CONTAINS (notes, ' quick ')
>
> of course entering
>
> SELECT title, notes
> FROM titles
> where notes like '%quick%'
>
> gets me the record I want. Anyone have any ideas what I can check?
>
> BTW I did this on another server and it works. The server is works is
> using
> SQL Server developer edition. The server that doesn't work is my
> production
> box using SQL Server standard edition
> Thanks for the help.
>
>
>|||Thanks Jerry. I have tried various combinations like
SELECT title, notes
FROM titles
WHERE CONTAINS (notes, 'quick')
or using double quotes with spaces in front of and behind the work quick.
I have also set up other full text indexes on this and other tables and other
databases on this server and it doesn't seem to work.
"Jerry Spivey" wrote:
> Francis,
> Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
> the item listed...might compare with CONTAINS in SQL BOL...same SP?
> HTH
> Jerry
> "Francis" <Francis@.discussions.microsoft.com> wrote in message
> news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
> >I cannot get fulltext indexing to work, nor can I get any error messages to
> > indicate whats wrong. Here's what I did (for the pubs database)
> >
> > 1. From the top menu, select Tools, Full Text Indexing.
> >
> > 2. Click next on the opening screen.
> >
> > 3. On the "Select a Database" screen, choose pubs.
> >
> > 4. For the next screen, select "titles" as the table and click next.
> >
> > 5. Keep the default unique index; there is only one on the pubs table.
> >
> > 6. In the next screen, select Title and Notes as the fields to be
> > indexed.
> >
> > 7. On the "Select a Catalog" screen, because this is the first Catalog on
> > the server, we are prompted for a name. In this example, "demo" is used as
> > the Catalog name.
> >
> > 8. Click next.
> >
> > 9. Click Finish.
> >
> > 10. From Enterprise Manager, expand Full-Text Catalogs
> >
> > 11. Right click and select "Start Full Population."
> >
> > 12. The catalog is now complete.
> >
> > If I type sp_help_fulltext_catalogs everything looks ok.
> >
> > If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
> > I get a 1 which means ok.
> >
> > If I type
> >
> > SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
> > I get 0 rows
> >
> > Same if I enter
> >
> >
> > SELECT title, notes
> > FROM titles
> > --where notes like '%quick%'
> > WHERE CONTAINS (notes, ' quick ')
> >
> >
> >
> > of course entering
> >
> >
> > SELECT title, notes
> > FROM titles
> > where notes like '%quick%'
> >
> >
> >
> > gets me the record I want. Anyone have any ideas what I can check?
> >
> >
> > BTW I did this on another server and it works. The server is works is
> > using
> > SQL Server developer edition. The server that doesn't work is my
> > production
> > box using SQL Server standard edition
> >
> > Thanks for the help.
> >
> >
> >
> >
> >
>
>|||Thanks for the help. I found the problem in KB317746;
I executed the workaround described:
EXEC sp_grantlogin [NT Authority\System]
EXEC sp_addsrvrolemember @.loginame = [NT Authority\System]
, @.rolename = 'sysadmin'
and all is well now.
"Francis" wrote:
> Thanks Jerry. I have tried various combinations like
> SELECT title, notes
> FROM titles
> WHERE CONTAINS (notes, 'quick')
> or using double quotes with spaces in front of and behind the work quick.
> I have also set up other full text indexes on this and other tables and other
> databases on this server and it doesn't seem to work.
>
> "Jerry Spivey" wrote:
> > Francis,
> >
> > Shot in the dark...QUOTED IDENTIFIER setting...might check the spacing for
> > the item listed...might compare with CONTAINS in SQL BOL...same SP?
> >
> > HTH
> >
> > Jerry
> > "Francis" <Francis@.discussions.microsoft.com> wrote in message
> > news:1899D25D-7325-4501-9B55-691C7C053686@.microsoft.com...
> > >I cannot get fulltext indexing to work, nor can I get any error messages to
> > > indicate whats wrong. Here's what I did (for the pubs database)
> > >
> > > 1. From the top menu, select Tools, Full Text Indexing.
> > >
> > > 2. Click next on the opening screen.
> > >
> > > 3. On the "Select a Database" screen, choose pubs.
> > >
> > > 4. For the next screen, select "titles" as the table and click next.
> > >
> > > 5. Keep the default unique index; there is only one on the pubs table.
> > >
> > > 6. In the next screen, select Title and Notes as the fields to be
> > > indexed.
> > >
> > > 7. On the "Select a Catalog" screen, because this is the first Catalog on
> > > the server, we are prompted for a name. In this example, "demo" is used as
> > > the Catalog name.
> > >
> > > 8. Click next.
> > >
> > > 9. Click Finish.
> > >
> > > 10. From Enterprise Manager, expand Full-Text Catalogs
> > >
> > > 11. Right click and select "Start Full Population."
> > >
> > > 12. The catalog is now complete.
> > >
> > > If I type sp_help_fulltext_catalogs everything looks ok.
> > >
> > > If I type Select DATABASEPROPERTY('Pubs', 'IsFulltextEnabled')
> > > I get a 1 which means ok.
> > >
> > > If I type
> > >
> > > SELECT title, notes FROM titles WHERE CONTAINS (notes, ' "quick easy" ')
> > > I get 0 rows
> > >
> > > Same if I enter
> > >
> > >
> > > SELECT title, notes
> > > FROM titles
> > > --where notes like '%quick%'
> > > WHERE CONTAINS (notes, ' quick ')
> > >
> > >
> > >
> > > of course entering
> > >
> > >
> > > SELECT title, notes
> > > FROM titles
> > > where notes like '%quick%'
> > >
> > >
> > >
> > > gets me the record I want. Anyone have any ideas what I can check?
> > >
> > >
> > > BTW I did this on another server and it works. The server is works is
> > > using
> > > SQL Server developer edition. The server that doesn't work is my
> > > production
> > > box using SQL Server standard edition
> > >
> > > Thanks for the help.
> > >
> > >
> > >
> > >
> > >
> >
> >
> >

Full Text Indexing Error

I see a lot of these in my Event log on the SQL Server for my Windows
Sharepoint Services site.
It would be nice to know what files are not being indexed and why.
Posting in the WSS group got me advice to update to SQL Server SP3 (done at
install) and/or post here.
Event Log Messages:
One or more documents stored in image columns with extension 'xls' did not
get full-text indexed because loading the filter failed with error '0x1'.
Note: These documents will not be passed to MSSearch for indexing, and
therefore this failure will not be reflected in the end of crawl summary
statistics.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
One or more documents stored in image columns with extension '' did not get
full-text indexed because loading the filter failed with error '0x1'.
Note: These documents will not be passed to MSSearch for indexing, and
therefore this failure will not be reflected in the end of crawl summary
statistics.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
This normally means your iFilter or related components has/have crashed. Try
to bounce MSSearch to solve this problem.You may need to reboot your server.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> I see a lot of these in my Event log on the SQL Server for my Windows
> Sharepoint Services site.
> It would be nice to know what files are not being indexed and why.
> Posting in the WSS group got me advice to update to SQL Server SP3 (done
at
> install) and/or post here.
> Event Log Messages:
> One or more documents stored in image columns with extension 'xls' did not
> get full-text indexed because loading the filter failed with error '0x1'.
> Note: These documents will not be passed to MSSearch for indexing, and
> therefore this failure will not be reflected in the end of crawl summary
> statistics.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> One or more documents stored in image columns with extension '' did not
get
> full-text indexed because loading the filter failed with error '0x1'.
> Note: These documents will not be passed to MSSearch for indexing, and
> therefore this failure will not be reflected in the end of crawl summary
> statistics.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
|||OK
A little more information...
The server is rebooted weekly
These errors have been cropping up for a while - So far i have had no
reports from users of any problems, but they are not using Sharepoint's
search very extensivly yet.
I hope to change that, but want to have some confidence in the results.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OnhOjEkAFHA.4028@.TK2MSFTNGP15.phx.gbl...
> This normally means your iFilter or related components has/have crashed.
Try
> to bounce MSSearch to solve this problem.You may need to reboot your
server.[vbcol=seagreen]
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
> news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> at
not[vbcol=seagreen]
'0x1'.
> get
>
|||David,
The first event log error indicates that an Excel (*.xls) file did not get
FT Indexed and the 2nd event log error indicates that a file extension of
'' (or NULL) did not get FT Indexed. The former, may occur because of a bad
file, but the latter should not occur, unless you are storing un-known
extensions. You should examine the gather log files (*.gthr) under
\FTDATA\SQLServer\GatherLogs\ with the gthrlog.vbs utility for additional
information and post the output of the gthrlog.vbs utility.
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> I see a lot of these in my Event log on the SQL Server for my Windows
> Sharepoint Services site.
> It would be nice to know what files are not being indexed and why.
> Posting in the WSS group got me advice to update to SQL Server SP3 (done
at
> install) and/or post here.
> Event Log Messages:
> One or more documents stored in image columns with extension 'xls' did not
> get full-text indexed because loading the filter failed with error '0x1'.
> Note: These documents will not be passed to MSSearch for indexing, and
> therefore this failure will not be reflected in the end of crawl summary
> statistics.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> One or more documents stored in image columns with extension '' did not
get
> full-text indexed because loading the filter failed with error '0x1'.
> Note: These documents will not be passed to MSSearch for indexing, and
> therefore this failure will not be reflected in the end of crawl summary
> statistics.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
|||John,
Thanks for the quick reply.
I had to switch to my network, security and training hats respectivly but am
now under the Sharepoint hat and have the following result:
1/31/2005 12:55:34 AM Add The gatherer has started
1/31/2005 12:55:36 AM Add The initialization has completed
1/31/2005 8:57:26 AM
MSSQL75://SQLServer/1de57479/CB325AA2334BED409E0F527D35A87A67 Add Error
fetching URL, (80041201 - The object was not found. )
1/31/2005 10:20:06 AM
MSSQL75://SQLServer/1de57479/EBB20D5D67E2EC4F820041532CB288BC Add Error
fetching URL, (80041201 - The object was not found. )
1/31/2005 11:03:36 AM
MSSQL75://SQLServer/76cba758/A86817082BA3E0469D8D07C2D70A8905 Add Error
fetching URL, (80041201 - The object was not found. )
1/31/2005 11:03:36 AM
MSSQL75://SQLServer/1de57479/C774194838E91540868BDAF8027CCEC8 Add Error
fetching URL, (80041201 - The object was not found. )
Clear enough, some reference is either expired or corrupt.
In your experience, is this something to be concerned about?
Searches have become much slower than the last time I tried anything, but we
also have 4 or 5 gb more data.
Bt slow, I mean durations of minutes while the SQL Server (dual pentium 4
2.something with 4gb ram) shows 80-95% processor consumed by MSSEARCH.
My users are not making much use of Search in Sharepoint, and at this point
I am holding off on encouraging them
David
btw - Nice pic on your blog - I really need to get out skiing again one of
these years...
"John Kane" <jt-kane@.comcast.net> wrote in message
news:uTVnh0pAFHA.1404@.TK2MSFTNGP11.phx.gbl...
> David,
> The first event log error indicates that an Excel (*.xls) file did not get
> FT Indexed and the 2nd event log error indicates that a file extension of
> '' (or NULL) did not get FT Indexed. The former, may occur because of a
bad[vbcol=seagreen]
> file, but the latter should not occur, unless you are storing un-known
> extensions. You should examine the gather log files (*.gthr) under
> \FTDATA\SQLServer\GatherLogs\ with the gthrlog.vbs utility for additional
> information and post the output of the gthrlog.vbs utility.
> Thanks,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "David McKenzie" <DavidMcKenzie@.noemail.nospam> wrote in message
> news:uL7DVujAFHA.2792@.TK2MSFTNGP15.phx.gbl...
> at
not[vbcol=seagreen]
'0x1'.
> get
>

Full Text Index Error

I am trying to define Full Text Indexing on the following table:
CREATE TABLE [dbo].[CCINFORMATION] (
[Name] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[AWID] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[Title] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Status] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Steffdt] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[CostCtr] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[CostCtrEffdt] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[PrevCostCtr] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Email] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[MgrName] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[MgrAWID] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[MgrEmail] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[MgrTitle] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[ID] [int] IDENTITY (1, 1) NOT NULL
) ON [PRIMARY]
GO

But it keeps giving me the following error when I try to run the wizard:
The selected table has no
unique single column index on a column that does not allow NULLS.

Database: CCReport

Table: [dbo].[CCINFORMATION]

Both the AWID field, and the ID field (which I added after first receiving this message), are NOT NULL...what am I doing wrong here?I have a solution to this. The syntaxes which you have given..I have copied the same and run. It did give me the error which you have mentioned.

Go to table design and create a Primakry Key. I have set the ID column as the primary key. Now it creates the Full-Text Index.

Thanks & Regards,
Dipayan Sarkar
(dipayan@.covisible.com)
[CoVisible Solutions - a Knowledge Management Software Company)

Full Text index catalog population error

Does anyone know what the services are involved during the SQL full
text index catalog population?
Some of my application event log errors are "Error: 80070426 - The
service has not been started.".
I know that my SQL server is running and MSsearch is running. I don't
know any other services needed for this operation.
Thank you in advance for any help!
Its MSSearch, SQL Server, SQL Server Agent (if you are scheduling your
populations).
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
"discover" <hongc@.lanproinc.com> wrote in message
news:1163533752.261545.225040@.f16g2000cwb.googlegr oups.com...
> Does anyone know what the services are involved during the SQL full
> text index catalog population?
> Some of my application event log errors are "Error: 80070426 - The
> service has not been started.".
> I know that my SQL server is running and MSsearch is running. I don't
> know any other services needed for this operation.
> Thank you in advance for any help!
>

Full Text Error

Hi,
We can successfully create catalogs on a database on our server. However,
we can never get any data from any of the searches. We have since
discovered a few errors in the Application log.
Version of SQL running is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows
NT 5.2 (Build 3790: )
SP3 has been applied and re-applied.
Errors are as follows:
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
One or more warnings or errors for Gatherer project <SQLServer
SQL0000700005> were logged to file <C:\Program Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs\SQL000070 0005.1.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).
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
Error from the gthrlog.vbs file reveals the following:
C:\Program Files\Common Files\System\MSSearch\Bin>cscript gthrlog.vbs
"C:\Progra
m Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs\SQL000070 0005.1.g
thr"
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
5/18/2004 11:26:44 AM Add The gatherer has started
5/18/2004 11:26:48 AM Add The initialization has completed
5/18/2004 11:27:16 AM Add Started Full crawl
5/18/2004 11:27:16 AM MSSQL75://SQLServer/75d7831f Add URL is
excluded
because the URL protocol is not recognized or restricted
5/18/2004 11:27:16 AM Add Completed Full crawl
C:\Program Files\Common Files\System\MSSearch\Bin>
Yours desperately.
Os
The crawl seeds error is normally generated by changing the SQL Server Service account through the services applet in Control Panel.
Please refer to these kbs for more information on how to solve this error.
http://support.microsoft.com/default...b;en-us;277549
http://support.microsoft.com/default...b;en-us;283811
http://support.microsoft.com/default...b;en-us;308787
Your error does look a little different from the usual ones. Can you give us any history about this problem? Do you have Sharepoint Portal Server 2003 or any other server application on this machine?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||I think you will need to open a second dblib connection to get this to work.
Microsoft is advising its customers not to use dblib any more as it may not be supported in future versions of the product, is slower than other access methods (ole-db), can't connect to instances or is unaware of instances (but you can make this work by
using an alias).
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||Oz,
Hilary, it seems to me that the following "Error: 80040d07 - The specified
URL is excluded and will not be cataloged. The URL restriction rules may
have to be modified to include this URL." and this error is not addressed in
any of the below KB articles.
I previously posted the following info here in the fulltext newsgroup back
in March 2004, "The key error is "80040d07 - The specified URL is excluded
and will not be cataloged". This is very unusual error for SQL FTS, but I
*believe* not so unusual for a SPS/WSS upgrade to SQL Server. Specifically,
the crawl seed is "MSSQL75://SQLServer/75d7831f " which SQL Server 2000 and
your FT enabled table. Did you enable FTS within SPS? Specifically, see WSS
Admin Guide title "Managing and Customizing Search" and "Enabling Search"
for more info. I *believe* this error is a symptom of not "Enabling Search"
after upgrading WSS to SQL Server 2000. Below is more info...
Examine the URL associated with this message and check the list of path
rules defined. This URL corresponds to one of the URLs or URL expressions
defined in the path rules. If you are interested in this URL, modify the
path rules. If you are satisfied with the current rules, then this warning
message is benign and can be ignored.
Regards,
John
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:502691A0-7D26-400D-8FD3-932519C47A61@.microsoft.com...
> The crawl seeds error is normally generated by changing the SQL Server
Service account through the services applet in Control Panel.
> Please refer to these kbs for more information on how to solve this error.
> http://support.microsoft.com/default...b;en-us;277549
> http://support.microsoft.com/default...b;en-us;283811
> http://support.microsoft.com/default...b;en-us;308787
> Your error does look a little different from the usual ones. Can you give
us any history about this problem? Do you have Sharepoint Portal Server
2003 or any other server application on this machine?
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>

Full Text Error

Hi,
We can successfully create catalogs on a database on our server. However,
we can never get any data from any of the searches. We have since
discovered a few errors in the Application log.
Version of SQL running is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows
NT 5.2 (Build 3790: )
SP3 has been applied and re-applied.
Errors are as follows:
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
One or more warnings or errors for Gatherer project <SQLServer
SQL0000700005> were logged to file <C:\Program Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs\SQL000070 0005.1.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).
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
Error from the gthrlog.vbs file reveals the following:
C:\Program Files\Common Files\System\MSSearch\Bin>cscript gthrlog.vbs
"C:\Progra
m Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs\SQL000070 0005.1.g
thr"
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
5/18/2004 11:26:44 AM Add The gatherer has started
5/18/2004 11:26:48 AM Add The initialization has completed
5/18/2004 11:27:16 AM Add Started Full crawl
5/18/2004 11:27:16 AM MSSQL75://SQLServer/75d7831f Add URL is
excluded
because the URL protocol is not recognized or restricted
5/18/2004 11:27:16 AM Add Completed Full crawl
C:\Program Files\Common Files\System\MSSearch\Bin>
Yours desperately.
Os
Oz,
Hilary, it seems to me that the following "Error: 80040d07 - The specified
URL is excluded and will not be cataloged. The URL restriction rules may
have to be modified to include this URL." and this error is not addressed in
any of the below KB articles.
I previously posted the following info here in the fulltext newsgroup back
in March 2004, "The key error is "80040d07 - The specified URL is excluded
and will not be cataloged". This is very unusual error for SQL FTS, but I
*believe* not so unusual for a SPS/WSS upgrade to SQL Server. Specifically,
the crawl seed is "MSSQL75://SQLServer/75d7831f " which SQL Server 2000 and
your FT enabled table. Did you enable FTS within SPS? Specifically, see WSS
Admin Guide title "Managing and Customizing Search" and "Enabling Search"
for more info. I *believe* this error is a symptom of not "Enabling Search"
after upgrading WSS to SQL Server 2000. Below is more info...
Examine the URL associated with this message and check the list of path
rules defined. This URL corresponds to one of the URLs or URL expressions
defined in the path rules. If you are interested in this URL, modify the
path rules. If you are satisfied with the current rules, then this warning
message is benign and can be ignored.
Regards,
John
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:502691A0-7D26-400D-8FD3-932519C47A61@.microsoft.com...
> The crawl seeds error is normally generated by changing the SQL Server
Service account through the services applet in Control Panel.
> Please refer to these kbs for more information on how to solve this error.
> http://support.microsoft.com/default...b;en-us;277549
> http://support.microsoft.com/default...b;en-us;283811
> http://support.microsoft.com/default...b;en-us;308787
> Your error does look a little different from the usual ones. Can you give
us any history about this problem? Do you have Sharepoint Portal Server
2003 or any other server application on this machine?
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>

Full Text Error

Hi,
We can successfully create catalogs on a database on our server. However,
we can never get any data from any of the searches. We have since
discovered a few errors in the Application log.
Version of SQL running is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows
NT 5.2 (Build 3790: )
SP3 has been applied and re-applied.
Errors are as follows:
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
One or more warnings or errors for Gatherer project <SQLServer
SQL0000700005> were logged to file <C:\Program Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs\SQL0000700005.1.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).
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
Error from the gthrlog.vbs file reveals the following:
C:\Program Files\Common Files\System\MSSearch\Bin>cscript gthrlog.vbs
"C:\Progra
m Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs\SQL0000700005.1.g
thr"
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
5/18/2004 11:26:44 AM Add The gatherer has started
5/18/2004 11:26:48 AM Add The initialization has completed
5/18/2004 11:27:16 AM Add Started Full crawl
5/18/2004 11:27:16 AM MSSQL75://SQLServer/75d7831f Add URL is
excluded
because the URL protocol is not recognized or restricted
5/18/2004 11:27:16 AM Add Completed Full crawl
C:\Program Files\Common Files\System\MSSearch\Bin>
Yours desperately.
OsOz,
Hilary, it seems to me that the following "Error: 80040d07 - The specified
URL is excluded and will not be cataloged. The URL restriction rules may
have to be modified to include this URL." and this error is not addressed in
any of the below KB articles.
I previously posted the following info here in the fulltext newsgroup back
in March 2004, "The key error is "80040d07 - The specified URL is excluded
and will not be cataloged". This is very unusual error for SQL FTS, but I
*believe* not so unusual for a SPS/WSS upgrade to SQL Server. Specifically,
the crawl seed is "MSSQL75://SQLServer/75d7831f " which SQL Server 2000 and
your FT enabled table. Did you enable FTS within SPS? Specifically, see WSS
Admin Guide title "Managing and Customizing Search" and "Enabling Search"
for more info. I *believe* this error is a symptom of not "Enabling Search"
after upgrading WSS to SQL Server 2000. Below is more info...
Examine the URL associated with this message and check the list of path
rules defined. This URL corresponds to one of the URLs or URL expressions
defined in the path rules. If you are interested in this URL, modify the
path rules. If you are satisfied with the current rules, then this warning
message is benign and can be ignored.
Regards,
John
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:502691A0-7D26-400D-8FD3-932519C47A61@.microsoft.com...
> The crawl seeds error is normally generated by changing the SQL Server
Service account through the services applet in Control Panel.
> Please refer to these kbs for more information on how to solve this error.
> http://support.microsoft.com/default.aspx?scid=kb;en-us;277549
> http://support.microsoft.com/default.aspx?scid=kb;en-us;283811
> http://support.microsoft.com/default.aspx?scid=kb;en-us;308787
> Your error does look a little different from the usual ones. Can you give
us any history about this problem? Do you have Sharepoint Portal Server
2003 or any other server application on this machine?
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>

Full Text Error

Hi,
We can successfully create catalogs on a database on our server. However,
we can never get any data from any of the searches. We have since
discovered a few errors in the Application log.
Version of SQL running is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows
NT 5.2 (Build 3790: )
SP3 has been applied and re-applied.
Errors are as follows:
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
One or more warnings or errors for Gatherer project <SQLServer
SQL0000700005> were logged to file <C:\Program Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs
\SQL0000700005.1.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).
The crawl on project <SQLServer SQL0000700005> cannot be started. All of the
crawl seeds have been ignored because of host, extension, or other URL
restrictions. Error: 80040d07 - The specified URL is excluded and will not
be cataloged. The URL restriction rules may have to be modified to include
this URL.
Error from the gthrlog.vbs file reveals the following:
C:\Program Files\Common Files\System\MSSearch\Bin>cscript gthrlog.vbs
"C:\Progra
m Files\Microsoft SQL
Server\MSSQL\FTDATA\SQLServer\GatherLogs
\SQL0000700005.1.g
thr"
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
5/18/2004 11:26:44 AM Add The gatherer has started
5/18/2004 11:26:48 AM Add The initialization has completed
5/18/2004 11:27:16 AM Add Started Full crawl
5/18/2004 11:27:16 AM MSSQL75://SQLServer/75d7831f Add URL is
excluded
because the URL protocol is not recognized or restricted
5/18/2004 11:27:16 AM Add Completed Full crawl
C:\Program Files\Common Files\System\MSSearch\Bin>
Yours desperately.
OsOz,
Hilary, it seems to me that the following "Error: 80040d07 - The specified
URL is excluded and will not be cataloged. The URL restriction rules may
have to be modified to include this URL." and this error is not addressed in
any of the below KB articles.
I previously posted the following info here in the fulltext newsgroup back
in March 2004, "The key error is "80040d07 - The specified URL is excluded
and will not be cataloged". This is very unusual error for SQL FTS, but I
*believe* not so unusual for a SPS/WSS upgrade to SQL Server. Specifically,
the crawl seed is "MSSQL75://SQLServer/75d7831f " which SQL Server 2000 and
your FT enabled table. Did you enable FTS within SPS? Specifically, see WSS
Admin Guide title "Managing and Customizing Search" and "Enabling Search"
for more info. I *believe* this error is a symptom of not "Enabling Search"
after upgrading WSS to SQL Server 2000. Below is more info...
Examine the URL associated with this message and check the list of path
rules defined. This URL corresponds to one of the URLs or URL expressions
defined in the path rules. If you are interested in this URL, modify the
path rules. If you are satisfied with the current rules, then this warning
message is benign and can be ignored.
Regards,
John
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:502691A0-7D26-400D-8FD3-932519C47A61@.microsoft.com...
> The crawl seeds error is normally generated by changing the SQL Server
Service account through the services applet in Control Panel.
> Please refer to these kbs for more information on how to solve this error.
> http://support.microsoft.com/defaul...kb;en-us;277549
> http://support.microsoft.com/defaul...kb;en-us;283811
> http://support.microsoft.com/defaul...kb;en-us;308787
> Your error does look a little different from the usual ones. Can you give
us any history about this problem? Do you have Sharepoint Portal Server
2003 or any other server application on this machine?
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>

Full text content index corrupt

Hello,
I am getting this error on my full text search...
Msg 7619, Lvl 16, State 1, Execution of a full-text operation failed. The
content index is corrupt. , Server ULSM1, Procedure , Line 1
I am using SQL 2000 Standard...
This happens on only ONE of my tables... i have 2 tables, that are almost
identical in structure, but 1 table has 100k records, and the other has 600k
records..
It is the table that has 600k records where this corrupt action happens...
Can anyone help me with this? This is the first time i've seen this error
(and i've done a couple google searches, but nothing this specific).
Thank you.
Is this table the only table in its catalog? If so rebuild the catalog to
see if this solves the problem. Review the event log to see if there are any
disk errors, or errors from MSSearch or MSSCI.
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
"RL Tech" <tech_support@.nospamuls.com> wrote in message
news:O2Sb09hFGHA.3892@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I am getting this error on my full text search...
> Msg 7619, Lvl 16, State 1, Execution of a full-text operation failed. The
> content index is corrupt. , Server ULSM1, Procedure , Line 1
> I am using SQL 2000 Standard...
> This happens on only ONE of my tables... i have 2 tables, that are almost
> identical in structure, but 1 table has 100k records, and the other has
> 600k
> records..
> It is the table that has 600k records where this corrupt action happens...
> Can anyone help me with this? This is the first time i've seen this error
> (and i've done a couple google searches, but nothing this specific).
> Thank you.
>
|||Hi Hilary,
I'll review the event log, but in the meantime i'll start the rebuild of the
catalog and see if that helps...
Thanks...
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23JMqh1lFGHA.1260@.TK2MSFTNGP15.phx.gbl...
> Is this table the only table in its catalog? If so rebuild the catalog to
> see if this solves the problem. Review the event log to see if there are
any[vbcol=seagreen]
> disk errors, or errors from MSSearch or MSSCI.
> --
> 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
> "RL Tech" <tech_support@.nospamuls.com> wrote in message
> news:O2Sb09hFGHA.3892@.TK2MSFTNGP12.phx.gbl...
The[vbcol=seagreen]
almost[vbcol=seagreen]
happens...[vbcol=seagreen]
error
>
|||Thanks hilary, that has helped...
Just an odd error i've never seen, nor could i find any topics on this
error.
Anyway, thanks again.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23JMqh1lFGHA.1260@.TK2MSFTNGP15.phx.gbl...
> Is this table the only table in its catalog? If so rebuild the catalog to
> see if this solves the problem. Review the event log to see if there are
any[vbcol=seagreen]
> disk errors, or errors from MSSearch or MSSCI.
> --
> 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
> "RL Tech" <tech_support@.nospamuls.com> wrote in message
> news:O2Sb09hFGHA.3892@.TK2MSFTNGP12.phx.gbl...
The[vbcol=seagreen]
almost[vbcol=seagreen]
happens...[vbcol=seagreen]
error
>

Full text content index corrupt

Hello,
I am getting this error on my full text search...
Msg 7619, Lvl 16, State 1, Execution of a full-text operation failed. The
content index is corrupt. , Server ULSM1, Procedure , Line 1
I am using SQL 2000 Standard...
This happens on only ONE of my tables... i have 2 tables, that are almost
identical in structure, but 1 table has 100k records, and the other has 600k
records..
It is the table that has 600k records where this corrupt action happens...
Can anyone help me with this? This is the first time i've seen this error
(and i've done a couple google searches, but nothing this specific).
Thank you.Is this table the only table in its catalog? If so rebuild the catalog to
see if this solves the problem. Review the event log to see if there are any
disk errors, or errors from MSSearch or MSSCI.
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
"RL Tech" <tech_support@.nospamuls.com> wrote in message
news:O2Sb09hFGHA.3892@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I am getting this error on my full text search...
> Msg 7619, Lvl 16, State 1, Execution of a full-text operation failed. The
> content index is corrupt. , Server ULSM1, Procedure , Line 1
> I am using SQL 2000 Standard...
> This happens on only ONE of my tables... i have 2 tables, that are almost
> identical in structure, but 1 table has 100k records, and the other has
> 600k
> records..
> It is the table that has 600k records where this corrupt action happens...
> Can anyone help me with this? This is the first time i've seen this error
> (and i've done a couple google searches, but nothing this specific).
> Thank you.
>|||Hi Hilary,
I'll review the event log, but in the meantime i'll start the rebuild of the
catalog and see if that helps...
Thanks...
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23JMqh1lFGHA.1260@.TK2MSFTNGP15.phx.gbl...
> Is this table the only table in its catalog? If so rebuild the catalog to
> see if this solves the problem. Review the event log to see if there are
any
> disk errors, or errors from MSSearch or MSSCI.
> --
> 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
> "RL Tech" <tech_support@.nospamuls.com> wrote in message
> news:O2Sb09hFGHA.3892@.TK2MSFTNGP12.phx.gbl...
The[vbcol=seagreen]
almost[vbcol=seagreen]
happens...[vbcol=seagreen]
error[vbcol=seagreen]
>|||Thanks hilary, that has helped...
Just an odd error i've never seen, nor could i find any topics on this
error.
Anyway, thanks again.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23JMqh1lFGHA.1260@.TK2MSFTNGP15.phx.gbl...
> Is this table the only table in its catalog? If so rebuild the catalog to
> see if this solves the problem. Review the event log to see if there are
any
> disk errors, or errors from MSSearch or MSSCI.
> --
> 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
> "RL Tech" <tech_support@.nospamuls.com> wrote in message
> news:O2Sb09hFGHA.3892@.TK2MSFTNGP12.phx.gbl...
The[vbcol=seagreen]
almost[vbcol=seagreen]
happens...[vbcol=seagreen]
error[vbcol=seagreen]
>

Full text content index corrupt

Hello,
I am getting this error on my full text search...
Msg 7619, Lvl 16, State 1, Execution of a full-text operation failed. The
content index is corrupt. , Server ULSM1, Procedure , Line 1
I am using SQL 2000 Standard...
This happens on only ONE of my tables... i have 2 tables, that are almost
identical in structure, but 1 table has 100k records, and the other has 600k
records..
It is the table that has 600k records where this corrupt action happens...
Can anyone help me with this? This is the first time i've seen this error
(and i've done a couple google searches, but nothing this specific).
Thank you.Is this table the only table in its catalog? If so rebuild the catalog to
see if this solves the problem. Review the event log to see if there are any
disk errors, or errors from MSSearch or MSSCI.
--
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
"RL Tech" <tech_support@.nospamuls.com> wrote in message
news:O2Sb09hFGHA.3892@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I am getting this error on my full text search...
> Msg 7619, Lvl 16, State 1, Execution of a full-text operation failed. The
> content index is corrupt. , Server ULSM1, Procedure , Line 1
> I am using SQL 2000 Standard...
> This happens on only ONE of my tables... i have 2 tables, that are almost
> identical in structure, but 1 table has 100k records, and the other has
> 600k
> records..
> It is the table that has 600k records where this corrupt action happens...
> Can anyone help me with this? This is the first time i've seen this error
> (and i've done a couple google searches, but nothing this specific).
> Thank you.
>|||Hi Hilary,
I'll review the event log, but in the meantime i'll start the rebuild of the
catalog and see if that helps...
Thanks...
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23JMqh1lFGHA.1260@.TK2MSFTNGP15.phx.gbl...
> Is this table the only table in its catalog? If so rebuild the catalog to
> see if this solves the problem. Review the event log to see if there are
any
> disk errors, or errors from MSSearch or MSSCI.
> --
> 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
> "RL Tech" <tech_support@.nospamuls.com> wrote in message
> news:O2Sb09hFGHA.3892@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > I am getting this error on my full text search...
> >
> > Msg 7619, Lvl 16, State 1, Execution of a full-text operation failed.
The
> > content index is corrupt. , Server ULSM1, Procedure , Line 1
> >
> > I am using SQL 2000 Standard...
> >
> > This happens on only ONE of my tables... i have 2 tables, that are
almost
> > identical in structure, but 1 table has 100k records, and the other has
> > 600k
> > records..
> >
> > It is the table that has 600k records where this corrupt action
happens...
> >
> > Can anyone help me with this? This is the first time i've seen this
error
> > (and i've done a couple google searches, but nothing this specific).
> >
> > Thank you.
> >
> >
>|||Thanks hilary, that has helped...
Just an odd error i've never seen, nor could i find any topics on this
error.
Anyway, thanks again.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23JMqh1lFGHA.1260@.TK2MSFTNGP15.phx.gbl...
> Is this table the only table in its catalog? If so rebuild the catalog to
> see if this solves the problem. Review the event log to see if there are
any
> disk errors, or errors from MSSearch or MSSCI.
> --
> 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
> "RL Tech" <tech_support@.nospamuls.com> wrote in message
> news:O2Sb09hFGHA.3892@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > I am getting this error on my full text search...
> >
> > Msg 7619, Lvl 16, State 1, Execution of a full-text operation failed.
The
> > content index is corrupt. , Server ULSM1, Procedure , Line 1
> >
> > I am using SQL 2000 Standard...
> >
> > This happens on only ONE of my tables... i have 2 tables, that are
almost
> > identical in structure, but 1 table has 100k records, and the other has
> > 600k
> > records..
> >
> > It is the table that has 600k records where this corrupt action
happens...
> >
> > Can anyone help me with this? This is the first time i've seen this
error
> > (and i've done a couple google searches, but nothing this specific).
> >
> > Thank you.
> >
> >
>

Full Text - Trusted account

Hello,
When I run an incremental/full job for a full text
catalog on win 2k , SQL 2K sp3a cluster server, i am
getting this in the SQL error log
Login failed for user domain\servername$
We recently removed the local admin group having syadmin
access to the server.
I changed the Job owner to the SQL Startup account, even
then it is using the above login. Why is that ?
I couldnt be able to grant the login access as i am not
able to see in the list of users...
Where is this login, can i change something to fix ?
Thanks
- Saravana
can you add this account to the system administrator role?
if not exists (select * from master.dbo.syslogins where loginname = N'NT
Authority\System')
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System', N'us_english'
GO
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
GO
"SK" <anonymous@.discussions.microsoft.com> wrote in message
news:1420b01c41808$d9e0f460$a601280a@.phx.gbl...
> Hello,
> When I run an incremental/full job for a full text
> catalog on win 2k , SQL 2K sp3a cluster server, i am
> getting this in the SQL error log
> Login failed for user domain\servername$
> We recently removed the local admin group having syadmin
> access to the server.
> I changed the Job owner to the SQL Startup account, even
> then it is using the above login. Why is that ?
> I couldnt be able to grant the login access as i am not
> able to see in the list of users...
> Where is this login, can i change something to fix ?
> Thanks
> - Saravana
>

Full log files

Hi, I am new to SQL server and need some help with full
log files. The error I am getting is:
Full msdb log error 9002; and
Full tempdb log error 9002.
How do I fix it?
Col :-)Hi,
"This error occurs when the transaction log becomes full"
Execute the below command in Query analyzer and check the log file % usage:-
DBCC SQLPERF(LOGSPACE)
If it is not 100% then the cause for this error is that there is no room on
the disk for the transaction log file to autogrow.
Solution:
Either you have to shrink the log file belongs to TEMPDB (this must be the
guy who used the maximum hard disk space). Normally MSDB will not have
much transaction log growth.
There are 3 methods to shrink the tempdb,
1. ALTER DATABASE TEMPDB MODIFY FILE ...
2. DBCC SHRINKDB
3. DBCC SHRINKFILE
look into this link for details,
http://support.microsoft.com/defaul...b;en-us;Q307487
Thanks
Hari
MCDBA
"Col" <colin.james@.waca.com.au> wrote in message
news:293901c42827$c5159ca0$a001280a@.phx.gbl...
> Hi, I am new to SQL server and need some help with full
> log files. The error I am getting is:
> Full msdb log error 9002; and
> Full tempdb log error 9002.
> How do I fix it?
> Col :-)