Can u install FTS later on? I have a clustered env. and due to failure in
registering FTS the entire install is rolling back? so perhaps I can delete
the FTS Resource and install it later...
TIA
Yes, it can be installed later, just like any other component of the SQL
Server 2005 install.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Vai2000" <nospam@.microsoft.com> wrote in message
news:uEsn7dQIGHA.528@.TK2MSFTNGP12.phx.gbl...
> Can u install FTS later on? I have a clustered env. and due to failure in
> registering FTS the entire install is rolling back? so perhaps I can
> delete
> the FTS Resource and install it later...
> TIA
>
2012年3月27日星期二
2012年3月9日星期五
Full Text catalogue build failure
I'm having severe problems implementing Search/Full Text Indexing service
with SQL Server 2000 (SP3). Following a successful test using a development
server (Win Svr 2003) I've attempted to roll out an application that makes
use of Full Text indexing using a production server. The development server
and production server are identical in terms of OS, SQL server, other
applications etc and I've followed the same steps that were used to implement
the Full Text Search on the developement server, on the production server.
Initially my problems started with not being able to create a Full Text
Indexiong catalogue. I've now rectified this (it was to do with the logon id
being used during the install of Search service - as part of the SQL server
install).
I now have a problem with actually populating the catalogue itself. The
Event log is issuing two errors when trying to populate the catalogue. The
first is:
"The crawl seed <MSSQL75://SQLServer/014935cb> in project <SQLServer
SQL0001900005> cannot be accessed. 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."
The second is:
"The crawl on project <SQLServer SQL0001900005> 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."
Any help with this would be greatly appreciated.
I've spent ages trawling the web to see if anybody else has had a similar
problem. The only items I found appear to point to Sharepoint services. As
far as I know SharePoint is not installed on the server in question (or is it
installed by default?) I feel a little bit out of my depth on this one!
Thanks
Kevin
Kevin,
I think I know what the problem might be. This invovles modifying the
registry so I will issue the standard disclaimer of proceed with caution
when making any registry changes.
This problem is caused because the SQL Server 2000 Protocol Handler is
missing
from the Registry. The following key is the key that should be added to the
registry
and the problem should be fixed:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\ ProtocolHandlers]
"MSSQL75"="sqlfth75.sqlfth75.1"
Most likely you will see the following entries there, but not the one above.
"File"="MSSearch.FileHandler.1"
"Http"="MSSearch.HttpHandler.1"
"OleDb"="MSSearch.OleDbHandler.1"
Let me know if this works.
David Gerard
Microsoft SQL Server Support
|||"David Gerard" wrote:
> Let me know if this works.
>
David,
Many Many Thanks.
Added the key, restarted Full Text Search service and hey presto.
Thanks again
Kevin
with SQL Server 2000 (SP3). Following a successful test using a development
server (Win Svr 2003) I've attempted to roll out an application that makes
use of Full Text indexing using a production server. The development server
and production server are identical in terms of OS, SQL server, other
applications etc and I've followed the same steps that were used to implement
the Full Text Search on the developement server, on the production server.
Initially my problems started with not being able to create a Full Text
Indexiong catalogue. I've now rectified this (it was to do with the logon id
being used during the install of Search service - as part of the SQL server
install).
I now have a problem with actually populating the catalogue itself. The
Event log is issuing two errors when trying to populate the catalogue. The
first is:
"The crawl seed <MSSQL75://SQLServer/014935cb> in project <SQLServer
SQL0001900005> cannot be accessed. 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."
The second is:
"The crawl on project <SQLServer SQL0001900005> 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."
Any help with this would be greatly appreciated.
I've spent ages trawling the web to see if anybody else has had a similar
problem. The only items I found appear to point to Sharepoint services. As
far as I know SharePoint is not installed on the server in question (or is it
installed by default?) I feel a little bit out of my depth on this one!
Thanks
Kevin
Kevin,
I think I know what the problem might be. This invovles modifying the
registry so I will issue the standard disclaimer of proceed with caution
when making any registry changes.
This problem is caused because the SQL Server 2000 Protocol Handler is
missing
from the Registry. The following key is the key that should be added to the
registry
and the problem should be fixed:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\ ProtocolHandlers]
"MSSQL75"="sqlfth75.sqlfth75.1"
Most likely you will see the following entries there, but not the one above.
"File"="MSSearch.FileHandler.1"
"Http"="MSSearch.HttpHandler.1"
"OleDb"="MSSearch.OleDbHandler.1"
Let me know if this works.
David Gerard
Microsoft SQL Server Support
|||"David Gerard" wrote:
> Let me know if this works.
>
David,
Many Many Thanks.
Added the key, restarted Full Text Search service and hey presto.
Thanks again
Kevin
Full Text catalogue build failure
I'm having severe problems implementing Search/Full Text Indexing service
with SQL Server 2000 (SP3). Following a successful test using a development
server (Win Svr 2003) I've attempted to roll out an application that makes
use of Full Text indexing using a production server. The development server
and production server are identical in terms of OS, SQL server, other
applications etc and I've followed the same steps that were used to implemen
t
the Full Text Search on the developement server, on the production server.
Initially my problems started with not being able to create a Full Text
Indexiong catalogue. I've now rectified this (it was to do with the logon i
d
being used during the install of Search service - as part of the SQL server
install).
I now have a problem with actually populating the catalogue itself. The
Event log is issuing two errors when trying to populate the catalogue. The
first is:
"The crawl seed <MSSQL75://SQLServer/014935cb> in project <SQLServer
SQL0001900005> cannot be accessed. 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."
The second is:
"The crawl on project <SQLServer SQL0001900005> 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 b
e
cataloged. The URL restriction rules may have to be modified to include this
URL."
Any help with this would be greatly appreciated.
I've spent ages trawling the web to see if anybody else has had a similar
problem. The only items I found appear to point to Sharepoint services. As
far as I know SharePoint is not installed on the server in question (or is i
t
installed by default?) I feel a little bit out of my depth on this one!
Thanks
KevinKevin,
I think I know what the problem might be. This invovles modifying the
registry so I will issue the standard disclaimer of proceed with caution
when making any registry changes.
This problem is caused because the SQL Server 2000 Protocol Handler is
missing
from the Registry. The following key is the key that should be added to the
registry
and the problem should be fixed:
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\Search\1.0\ProtocolHandlers]
"MSSQL75"="sqlfth75.sqlfth75.1"
Most likely you will see the following entries there, but not the one above.
"File"="MSSearch.FileHandler.1"
"Http"="MSSearch.HttpHandler.1"
"OleDb"="MSSearch.OleDbHandler.1"
Let me know if this works.
David Gerard
Microsoft SQL Server Support|||"David Gerard" wrote:
> Let me know if this works.
>
David,
Many Many Thanks.
Added the key, restarted Full Text Search service and hey presto.
Thanks again
Kevin
with SQL Server 2000 (SP3). Following a successful test using a development
server (Win Svr 2003) I've attempted to roll out an application that makes
use of Full Text indexing using a production server. The development server
and production server are identical in terms of OS, SQL server, other
applications etc and I've followed the same steps that were used to implemen
t
the Full Text Search on the developement server, on the production server.
Initially my problems started with not being able to create a Full Text
Indexiong catalogue. I've now rectified this (it was to do with the logon i
d
being used during the install of Search service - as part of the SQL server
install).
I now have a problem with actually populating the catalogue itself. The
Event log is issuing two errors when trying to populate the catalogue. The
first is:
"The crawl seed <MSSQL75://SQLServer/014935cb> in project <SQLServer
SQL0001900005> cannot be accessed. 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."
The second is:
"The crawl on project <SQLServer SQL0001900005> 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 b
e
cataloged. The URL restriction rules may have to be modified to include this
URL."
Any help with this would be greatly appreciated.
I've spent ages trawling the web to see if anybody else has had a similar
problem. The only items I found appear to point to Sharepoint services. As
far as I know SharePoint is not installed on the server in question (or is i
t
installed by default?) I feel a little bit out of my depth on this one!
Thanks
KevinKevin,
I think I know what the problem might be. This invovles modifying the
registry so I will issue the standard disclaimer of proceed with caution
when making any registry changes.
This problem is caused because the SQL Server 2000 Protocol Handler is
missing
from the Registry. The following key is the key that should be added to the
registry
and the problem should be fixed:
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\Search\1.0\ProtocolHandlers]
"MSSQL75"="sqlfth75.sqlfth75.1"
Most likely you will see the following entries there, but not the one above.
"File"="MSSearch.FileHandler.1"
"Http"="MSSearch.HttpHandler.1"
"OleDb"="MSSearch.OleDbHandler.1"
Let me know if this works.
David Gerard
Microsoft SQL Server Support|||"David Gerard" wrote:
> Let me know if this works.
>
David,
Many Many Thanks.
Added the key, restarted Full Text Search service and hey presto.
Thanks again
Kevin
2012年2月19日星期日
Full - text Catalog
When I create a full-text catalog in Enterprise Manager, the following error
pops up "An unknown full-text failure (80077007e) occurred in function
EnumCatalogs on full-text catalog". Any idea?
Can you give us a history of this database? Was it restored from another
machine which had a full text catalog on it?
Can you build a catalog in another database? IE pubs.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:7EB74048-4477-4367-9BAE-83D1C7CF3EA7@.microsoft.com...
> When I create a full-text catalog in Enterprise Manager, the following
error
> pops up "An unknown full-text failure (80077007e) occurred in function
> EnumCatalogs on full-text catalog". Any idea?
|||Peter,
Could you post the full output of -- SELECT @.@.version -- as this is very
helpful for troubleshooting SQL FTS issues.
Could you also post the contents of the most current non-zero length Gather
log file? These files are located under \FTDATA\SQLServer\GatherLogs\*.gthr
(for example: SQL0000500005.296.gthr). You can "read" the "Gatherer Logs"
via Command Scripting Host, WSH's CScript.exe, for example:
cscript //nologo <path>\gthrlog.vbs <path>\GatherLogs\SQL0000500005.1.gthr
Post the output of the @.@.version and the above file.
Thanks,
John
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:7EB74048-4477-4367-9BAE-83D1C7CF3EA7@.microsoft.com...
> When I create a full-text catalog in Enterprise Manager, the following
error
> pops up "An unknown full-text failure (80077007e) occurred in function
> EnumCatalogs on full-text catalog". Any idea?
pops up "An unknown full-text failure (80077007e) occurred in function
EnumCatalogs on full-text catalog". Any idea?
Can you give us a history of this database? Was it restored from another
machine which had a full text catalog on it?
Can you build a catalog in another database? IE pubs.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:7EB74048-4477-4367-9BAE-83D1C7CF3EA7@.microsoft.com...
> When I create a full-text catalog in Enterprise Manager, the following
error
> pops up "An unknown full-text failure (80077007e) occurred in function
> EnumCatalogs on full-text catalog". Any idea?
|||Peter,
Could you post the full output of -- SELECT @.@.version -- as this is very
helpful for troubleshooting SQL FTS issues.
Could you also post the contents of the most current non-zero length Gather
log file? These files are located under \FTDATA\SQLServer\GatherLogs\*.gthr
(for example: SQL0000500005.296.gthr). You can "read" the "Gatherer Logs"
via Command Scripting Host, WSH's CScript.exe, for example:
cscript //nologo <path>\gthrlog.vbs <path>\GatherLogs\SQL0000500005.1.gthr
Post the output of the @.@.version and the above file.
Thanks,
John
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:7EB74048-4477-4367-9BAE-83D1C7CF3EA7@.microsoft.com...
> When I create a full-text catalog in Enterprise Manager, the following
error
> pops up "An unknown full-text failure (80077007e) occurred in function
> EnumCatalogs on full-text catalog". Any idea?
订阅：
博文 (Atom)