You receive a "The address could not be found" error message when you import user profile information from a server that is running the Active Directory directory service to SharePoint Portal Server 2003 (840518)
The information in this article applies to:
- Microsoft Office SharePoint Portal Server 2003
SYMPTOMSWhen you try to import user profile information from a server that is running the Active Directory directory service to Microsoft Office SharePoint Portal Server 2003, the import operation is not completed successfully. An error message that is similar to the following is logged to the gatherer log:
Date Add spsimport: Time The address could not be found, (0x8007054B - The specified domain either does not exist or could not be contacted.) CAUSEThis problem may occur if SharePoint Portal Server 2003 incorrectly retrieves the name of the domain controller. This problem may occur if both the following conditions are true: - The first part of the fully qualified domain name (FQDN) of the server is different from the NetBIOS domain name.
- The connection to the server that you want to import user profile information from is configured to use the Auto discover domain controller setting.
WORKAROUNDTo work around this problem, configure the connection to the domain controller to use the Select a domain controller setting, and then specify the name of the domain controller that you want to import user information from. To do so, follow these steps: - On the home page of the portal site, click Site Settings.
- Under User Profile, Audiences, and Personal Sites, click Manage profile database.
- On the Manage Profile Database page, click Configure profile import under Profile and Import Settings.
- On the Configure Profile Import page, click Custom source in the Source area, and then click OK.
- On the Manage Profile Database page, click Manage connections under Profile and Import Settings.
- On the Manage Connections page, click the domain name, and then click Edit.
- On the Edit Connection page, click Select a domain controller in the Connection Settings area, click the name of the domain controller in the Domain controller name box, and then click OK.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Major | Last Reviewed: | 9/9/2004 |
---|
Keywords: | kberrmsg kbImport kbnofix kbBug KB840518 kbAudITPRO |
---|
|