Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 835521 - Last Review: September 9, 2004 - Revision: 3.4
"The address could not be found" error messages are logged to the gatherer log after you update a content index in SharePoint Portal Server 2003
In your server farm deployment of Microsoft Office SharePoint Portal Server 2003, when you view the gatherer log of a content index after you update that content index, you may see error messages that are similar to the following:
Error Message 1
Date Time Modify sps://ServerName/site$$$people
The address could not be found, (0x80042617 - Error in PortalCrawl Web Service. )
Error Message 2
Date Time Modify http://ServerName
The address could not be found, (0x80042616 - Error in the Site Data Web Service.)
This problem may occur if you configure SharePoint Portal Server 2003 to use a proxy server when it creates full-text indexes of external Web sites, and if all the following conditions are true:
- You specify the Bypass proxy server for local (intranet) addresses option.
- In the Do not use proxy server for address beginning with box, you specify one or more URLs that start with an asterisk (*) wildcard character. For example, you specify a URL that is similar to the following:
*.DomainName.com
In this scenario, SharePoint Portal Server 2003 does not process the asterisk (*) wildcard character correctly when it crawls content.
To work around this problem, do not use an asterisk (*) wildcard character in URLs that you specify in the
Do not use proxy server for address beginning with box. Instead, use one of the following prefixes in the URLs that you specify in the
Do not use proxy server for address beginning with box, depending on your situation:
- http://*.DomainName.com
- https://*.DomainName.com
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
To configure SharePoint Portal Server 2003 to use a proxy server when it creates full-text indexes of external Web sites, use the
Configure Server Farm Account Settings page in SharePoint Central Administration. For more information about how to configure proxy server settings in SharePoint Portal Server, see the "Configuring Server Farm Account Settings" topic in the "Managing Search" section of the "Administration" chapter of the
Microsoft Office SharePoint Portal Server 2003 Administration Guide. The
Microsoft Office SharePoint Portal Server 2003 Administration Guide (Administrator's Help.chm) is located in the Docs folder in the root directory of the SharePoint Portal Server 2003 CD.
For more information about SharePoint Portal Server 2003, visit the following Microsoft Web site:
APPLIES TO
- Microsoft Office SharePoint Portal Server 2003
| kberrmsg kbnofix kbbug KB835521 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate