Microsoft Knowledge Base Email Alertz

(840518) - Describes an issue in SharePoint Portal Server that occurs when you try to import user profile information from Active Directory and the first part of the FQDN of the server is different from the NetBIOS domain name.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 840518 - Last Review: September 9, 2004 - Revision: 2.4

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

SYMPTOMS

When 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.)

CAUSE

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

WORKAROUND

To 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:
  1. On the home page of the portal site, click Site Settings.
  2. Under User Profile, Audiences, and Personal Sites, click Manage profile database.
  3. On the Manage Profile Database page, click Configure profile import under Profile and Import Settings.
  4. On the Configure Profile Import page, click Custom source in the Source area, and then click OK.
  5. On the Manage Profile Database page, click Manage connections under Profile and Import Settings.
  6. On the Manage Connections page, click the domain name, and then click Edit.
  7. 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.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about how to manage profiles from Active Directory in SharePoint Portal Server 2003, see the "Managing User Profiles from Active Directory" topic in the "Administration" chapter of the Microsoft Office SharePoint Portal Server 2003 Administrator's Guide.

The Microsoft Office SharePoint Portal Server 2003 Administrator's Guide (Administrator's Help.chm) is located in the Docs folder in the root folder of the SharePoint Portal Server 2003 CD.

For more information about SharePoint Portal Server, visit the following Microsoft Web site:
http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=2f7ba03d-1762-4ae9-b059-23aa198c08fb (http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=2f7ba03d-1762-4ae9-b059-23aa198c08fb)

APPLIES TO
  • Microsoft Office SharePoint Portal Server 2003
Keywords: 
kberrmsg kbimport kbnofix kbbug KB840518
       

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