locked
Profile Import Problem RRS feed

  • Question

  •  

    I am currently having issues with the Profile Import with MOSS.  When I look at the import log, I notice 6 items, 2 successes, 2 Errors, 2 Warnings. The errors are below.  I did not deploy MOSS enterprise edition to this box.  It is a virtual server with a standalone deployment of MOSS enterprise edition with development tools (visual studio 2005, sharepoint designer, infopath, etcdeployed.  It does not have sql server 2005 installed currently.  The people picker in moss is able to connect to the Domain controller and return all users, but the profile importer does not seem to be able to pull in accounts.  Any assistance would be appreciated.

     

    spsimport://[servername]?$$dl$$
    The specified domain either does not exist or could not be contacted. (Exception from HRESULT: 0x8007054B)

    PEOPLE_DL_IMPORT

    6/18/2008 4:45 PM

    spsimport://$$dl$$
    Crawled

    PEOPLE_DL_IMPORT

    6/18/2008 4:45 PM

     

    spsimport://[servername]
    The specified domain either does not exist or could not be contacted. (Exception from HRESULT: 0x8007054B)

    PEOPLE_IMPORT

    6/18/2008 4:43 PM

     

    spsimport://7a6d9d9f-b173-4163-9934-88046234f6b4
    Crawled

    PEOPLE_IMPORT

    6/18/2008 4:43 PM

     

    spsimport://[domain.suffix]
    Deleted by the gatherer (This item was deleted because the crawler did not encounter it during the last full crawl.)

    PEOPLE_IMPORT

    6/18/2008 3:50 PM

     

    spsimport://[servername.domain.suffix]
    Deleted by the gatherer (This item was deleted because the crawler did not encounter it during the last full crawl.)

    PEOPLE_IMPORT

    6/18/2008 3:50 PM

     

    Thursday, June 19, 2008 2:30 PM

Answers

  • Albert Widjaja said:



    yeah i'm in the same boat as you Chad.

    I still got error and stuck in importing the user.


    how did you go with the solution then ?


    /* Support Engineer */



    Make sure that the domain showing in the Import Connection is exactly the same as the true NT domain name.  I ran into this recently at a client where the domain was detected by SharePoint as "Agency," but it was really "Agency_NT."  This was a mistake that was made years ago and hadn't been fixed, so now it's a problem, and SharePoint is one place it reared its ugly head.  All I had to do was make an import connection pointing to the proper NT domain name, and it worked.  If this is proper in your setup, then be sure your content access account has permissions to read AD.
    Tuesday, December 16, 2008 7:27 AM

All replies

  •  

    I have created a new Import connection to my doamin, because the default connection (created by MOSS) was with wrong domain name. Another point is that the AD content access account must have appropriate permissions to read from AD. After this I have deleted the default connection from "Manage Connections" page and started "Full import".

     

     

    My advice - recreate the import connection!

     

     

     

     

     

    Friday, June 27, 2008 9:24 AM
  • How do you have your web apps configured? are you using hostnames or cname aliases?

    Friday, June 27, 2008 12:08 PM
  • Hi James Milne,

    I think mine web app setting(s) are correct but still issue are coming.............


    Can any one please help me to resolve this issue......

    Cheers,
    Harsh Wordhan Gupta
    Tuesday, September 30, 2008 6:48 AM


  • yeah i'm in the same boat as you Chad.

    I still got error and stuck in importing the user.


    how did you go with the solution then ?

    /* Support Engineer */
    Tuesday, December 16, 2008 7:20 AM
  • Albert Widjaja said:



    yeah i'm in the same boat as you Chad.

    I still got error and stuck in importing the user.


    how did you go with the solution then ?


    /* Support Engineer */



    Make sure that the domain showing in the Import Connection is exactly the same as the true NT domain name.  I ran into this recently at a client where the domain was detected by SharePoint as "Agency," but it was really "Agency_NT."  This was a mistake that was made years ago and hadn't been fixed, so now it's a problem, and SharePoint is one place it reared its ugly head.  All I had to do was make an import connection pointing to the proper NT domain name, and it worked.  If this is proper in your setup, then be sure your content access account has permissions to read AD.
    Tuesday, December 16, 2008 7:27 AM
  • Clayton,

    it worked now :-)

    I had to create another import source, by selecting the manual option rather than using the autodiscover for the DOMAIN lookup.

    Thanks to All, this problem is now solved.

    Cheers.

    /* Support Engineer */
    Thursday, January 8, 2009 3:16 AM
  • We have a situation now on prod in sharepoint 2007 based intranet platform and it shows thousands of records under people_dl_import category with format spsimport://?$$dl$$/domain1/domain2/domain3/

    Also import was not stopping and added millions of records in database and was on verge of disk full.

    On other servers like dev we have very less data in this category. I need to know the cause of this garbage data and how to fix it. I tried resetting content source and I will do full import in this weekend to see if this garbage data gets cleared. Any idea on cause for thiss issue?

    Friday, June 18, 2010 5:26 AM
  • I recommend creating a new thread, because your problem is very different than the original topic, and this thread is already answered, so most people won't click on it.


    SharePoint Architect || Microsoft MVP || My Blog
    Friday, June 18, 2010 5:48 AM