Hi



I get the following error in the Gatherer log


<ERROR>
The address could not be found, (0x80041221 - URL could not be resolved. The
host may be unavailable, or the proxy settings are not configured correctly
on the index server. To change proxy settings, from SharePoint Portal Server
Central Administration click Configure Search and Indexing. In the list of
index servers, choose the server name and edit the proxy settings on the
Server Settings page. )
<ERROR>


Which is strange because
1. The user account for the crawling can access the site and the DB
2. The Indexing Server is the same as the Content Server and the URL can be
resolved in a browser.
3. We don't use a proxy server on the network.

Any help is more than welcome.


Kind regards
Frederick D'hont
Amplexor.com

Re: Indexing Error : URL could not be resolved by Frederick

Frederick
Mon Oct 27 09:04:12 CST 2003

Ahum




Here's another error. I have multiple server configurations running on
different servers :)

<ERROR>
The address could not be found, (0x80042616 - Error in the Site Data Web
Service. ) Value cannot be null. Parameter name: uriString
</ERROR>

Until know I was only able to get one implementation running : the one that
doesn't use host header names :-s


Kind regards
Frederick D'hont
Amplexor.com


PS : Those MS guys are very quite on this newsgroup concerning configuration
problems with Sharepoint 2003.



"Frederick D'hont" <frederick.dhont@amplexor_nospam.com> wrote in message
news:#FFd2KKnDHA.2244@TK2MSFTNGP12.phx.gbl...
> Hi
>
>
>
> I get the following error in the Gatherer log
>
>
> <ERROR>
> The address could not be found, (0x80041221 - URL could not be resolved.
The
> host may be unavailable, or the proxy settings are not configured
correctly
> on the index server. To change proxy settings, from SharePoint Portal
Server
> Central Administration click Configure Search and Indexing. In the list of
> index servers, choose the server name and edit the proxy settings on the
> Server Settings page. )
> <ERROR>
>
>
> Which is strange because
> 1. The user account for the crawling can access the site and the DB
> 2. The Indexing Server is the same as the Content Server and the URL can
be
> resolved in a browser.
> 3. We don't use a proxy server on the network.
>
> Any help is more than welcome.
>
>
> Kind regards
> Frederick D'hont
> Amplexor.com
>
>