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.

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.aspx?scid=kb;en-us;27754
http://support.microsoft.com/default.aspx?scid=kb;en-us;28381
http://support.microsoft.com/default.aspx?scid=kb;en-us;30878

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.htm

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.htm

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




[quoted text, click to view]
us any history about this problem? Do you have Sharepoint Portal Server
2003 or any other server application on this machine?
[quoted text, click to view]