Microsoft KB Archive/286156

= Configuring and Troubleshooting Exchange Server 5.5 Content Sources =

Article ID: 286156

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft SharePoint Portal Server 2001

-



This article was previously published under Q286156



SUMMARY
SharePoint Portal Server can create an index of items that are stored in Microsoft Exchange Server 5.5 public folders. You can only create content sources that point to the public folder hierarchy on one Exchange Server 5.5 computer; however, if the folders reside on another Exchange Server computer, Search is redirected to the proper server so that Search can index them.



MORE INFORMATION
To index Exchange Server 5.5 public folders, you need to complete the following steps before you create the content source by using the Add Content Source Wizard:
 * Microsoft Outlook 2000 must be installed on your SharePoint Portal Server computer. Outlook must have the Collaboration Data Objects (CDO) component installed. CDO is not part of the default installation, so you need to run Outlook 2000 Setup again and select CDO if it is not installed. You do not need to configure a profile to create a content source; however, it is recommended that you create a profile for the account you want to use to index the server to verify that you have connectivity to the Exchange Server 5.5 computer.
 * If you want users to be able to view Search results that reside in the Exchange Server 5.5 public folders that you have indexed, you must install the Exchange Server Microsoft Outlook Web Access (OWA) component on a server in your Exchange Server organization.
 * You must configure the following information on the Exchange 5.5 tab in your server's properties in the SharePoint Portal Server Administration Console Microsoft Management Console (MMC) snap-in:
 * The name of the Exchange Server 5.5 computer.
 * The name of the OWA server on your network.
 * The name of the Exchange Server site that the server belongs to.
 * The name of the Exchange Server organization that the server belongs to.
 * A domain access account. The account that you provide must have Admin permissions on the Site and Site Configuration containers in Exchange Server, as well as read access to any public folder content that you want to index. The Admin permissions are used to verify permissions to folder items during searches. If a user does not have permissions to an item, it is not displayed in their search results. The access account that you provide must be in a domain that trusts the SharePoint Portal Server computer's domain or indexing does not work.

After you create the content source and start an update, check the status by clicking the content source icon in the content sources folder. If &quot;Update Failed&quot; is displayed, or you have an unexpectedly high number of errors, check the gatherer log for details. To view the log, click the Click here for Detailed Log link.

The following issues are common issues that can occur and the errors in the gatherer log that are associated with these issues.

Invalid Exchange Server 5.5 Access Account Specified
When you specify account credentials for the Exchange Server 5.5 computer in the MMC, the account credentials are not validated, so you might configure an invalid account, or a valid account with an incorrect password. This issue also occurs if the access account is in a domain that does not trust the domain that the SharePoint Portal Server computer is a member of.

Symptom
An account that has no access to the Exchange Server computer causes the update to stop working immediately. When the content source is selected in the Content Sources folder, an &quot;Update Failed&quot; error message is displayed. The following error message is logged in the gatherer log:

Error fetching URL, (800411a5 - The service cannot access the Exchange 5.5 server. The configured Microsoft Exchange 5.5 Server name may be invalid, the Exchange 5.5 Server may be temporarily unavailable, or the account used by the Search services may not have administrative access to the Exchange 5.5 Server. Check all of these properties, and then try again.)

Resolution
To resolve this issue, verify the account information in the MMC. Verify that you are using an account that is in a trusted domain.

The Exchange Server 5.5 Access Account Does Not Have Correct Permissions on the Exchange Server Computer
When you specify account credentials for the Exchange Server 5.5 computer in the MMC, they are not validated, so you might configure an account without the required permissions to the Exchange Server computer.

Symptom
A valid account that has insufficient permissions to the Exchange Server computer causes the crawl to stop working immediately. When the content source is selected in the Content Sources folder, an &quot;Update Failed&quot; error message is displayed. The following error message is logged in the gatherer log:

800411A6, The service cannot access the Exchange 5.5 service. The account used by the Search services may not be an Exchange 5.5 administrator, or the Site and Organization settings on the Search host may be invalid.

Resolution
To resolve this issue, verify that the account that you are using has Admin permissions to the Site and Site Configuration containers on the Exchange 5.5 server. Log on to the mailbox of the Exchange Server 5.5 access account that is provided by using Outlook 2000 on the server, and then verify that you have access to view all of the folder content that you want to index.

Incorrect Exchange Server 5.5 Site or Organization Name
If an incorrect site or organization name is specified in the MMC, the update does not work.

Symptom
The update stops working immediately and an &quot;Update Failed&quot; error message is displayed in the content sources folder. The following error message is logged in the gatherer log:

800411A6, The service cannot access the Exchange 5.5 service. The account used by the Search services may not be an Exchange 5.5 administrator, or the Site and Organization settings on the Search host may be invalid.

Resolution
To resolve this issue, verify the Exchange Server computer information in the MMC.

The Exchange Server 5.5 Information Store or Directory Service Is Not Started
If either the Exchange Server Information Store service or the Exchange Server Directory service is not started, the update does not work.

Symptom
The update stops working immediately and an &quot;Update Failed&quot; error message is displayed in the Content Sources folder. The following error message is logged in the gatherer log:

Error fetching URL, (80040115 - Mapi. A network error has occurred.)

Resolution
To resolve this issue, verify that the Information Store service and the Directory service are started on the Exchange Server computer.

File Attachment Was Not Filtered
During indexing, Search uses components called Index Filters that are able to read a document in its native format and extract the body text and metadata. Index Filters are registered to and operate on document file extensions (for example, .doc or .xls). When Search indexes Exchange Server 5.5 content sources, Search indexes file attachments in messages, but only those attachment types with a registered Index Filter. This is true regardless of whether you have added the file extension to the included file types list in your workspace. However, the message itself is still indexed.

Symptom
The update statistics show the items as &quot;Other errors&quot; in the &quot;Failed to index&quot; section. The following error message is logged in the gatherer log for each instance:

Error fetching URL, (8004121b - Some parts of the document could not be accessed.)

Resolution
This behavior is by design and means that the message that is being indexed had a file attachment that could not be filtered.

Gatherer Log Information
A gatherer log is created for the workspace each time that an index update occurs. By default, only documents that encounter errors are logged. When you troubleshoot indexing, you may want to view documents that were successfully indexed, as well as documents that were not indexed because of rules that are configured in the workspace (for example, documents that are excluded by means of site path rules). It is strongly recommended that you disable success and rule exclusion logging after you are finished troubleshooting, because logging success and rule exclusion might generate large log files and take up considerable disk space.

To configure log settings, click the Workspace Settings icon in the Management folder in your workspace, and then click the Logging tab. You can also gain access to the Logging tab by right-clicking your workspace name in the SharePoint Portal Server Administration Console MMC snap-in, and then clicking properties.

Additional query words: sps

Keywords: kbinfo KB286156

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.