none
Unable to import user profiles RRS feed

  • Question

  • Hi all,

    I would appreciate any assistance/pointers with the following issue please:

    We have an extranet using MOSS2007, containing several subsites.  When viewing "People and Groups -> All people", some of the users have their e-mail address pulled in from AD, and some don't.  This is impacting the ability of Sharepoint to be able to send notifications to these users.  All users have valid e-mail addresses configured in AD, but they are just not being pulled in/synched correctly.
    When I look at doing a profile import for the SSP we are using, I can see that an Import Connection was set up previously, but when I attempt to do an import I get the following error:

    "spsimport://ext.oursite.org?$$dl$$
    Exception from HRESULT: 0x8004400C (Error (0x800706ba) occurred, which may have resulted from the unavailability of directory service server (ourdc.ext.oursite.org). If the auto discovery option is turned on, import will re-try it with the newly discovered directory server. Otherwise, verify your import settings and make sure the server is still available. )" 

    I've also tried editing the existing connection as well as creating a new one (with the default settings) and constantly get the following error:
    "The query is not valid based on the specified search base and search filter. Please validate your input of search base and filter."
    This is very confusing as I know that the information is valid, the DC is up and responding to requests etc.

    So, 2 questions please:
    1) For the issue with e-mail addresses not synching, am I going about the solution in the right way?  ie do you think it is the profile import which will fix this?
    2)  What do I need to do to get the profile import to work/get rid of these error messages?

    My apologies if any of this is too vague; if you need any further info please let me know.
    Many thanks in advance,
    G
    Thursday, February 11, 2010 10:30 AM

Answers

All replies

  • Hi:

    As per my understanding you are going in the right direction.

    Can you confirm if your Central Sharepoint with Domain Controller in subsidiary?

    For Central SP and Central Domain Controller (I. Sharepoint installation on same server as that of AD) some time back even i had received exceptions.

    Also if they are different please try again after validating your i\ps for search base & filters. That is the only way you do profile imports ( go for Full Import).

    Also post eventvwr entries so that if someone has more to add can be helpfull for them.

    Thanks
    Best Regards, Mukesh Giri Sr.System Executive
    Thursday, February 11, 2010 11:11 AM
  • Hi there,

    Thanks for your reply.  To confim, the Central Admin is in the root domain and we're trying to connect to either of the DCs in a separate (extranet) domain.  Connectivity between the 2 should be fine; I'm busy verifying that with our network team at the same time.

    For the validation of the search base and filters, I am allowing it to autofill the search base and keeping the default filter, ie I select a connection type of "Active Directory", input the domain name (ext.ourdomain.org), autofill the search base (which results in "DC=ext,DC=ourdomain,DC=org") and then keep the default filter.  When I click on ok, I get the error mentioned in the opening post.

    Thanks again,
    G

    PS  I'm not receiving any event errors on the CA server that seem to relate to this issue.  Are there any particular event IDs/sources that I should be on the lookout for?

    Thursday, February 11, 2010 11:51 AM
  • Hi:

    On Sharepoint front you are going in the right direction, you do autofill the search base and other things as default.

    On AD front can you verify there is two way trust between the two DC's? Becos in the same forest the trust is automatically created for different forests you have to check for the trust btw them.

    As i understand connectivities is the sole issue here.

    Thanks,
    Best Regards, Mukesh Giri Sr.System Executive
    • Marked as answer by GuYuming Friday, February 26, 2010 9:39 AM
    • Unmarked as answer by yargray Friday, February 26, 2010 10:27 AM
    Thursday, February 11, 2010 12:10 PM
  • Hi again,

    Ok, I agree with you that the error message would seem to indicate a connectivity problem.  However, I have verified that a 2-way transitive trust exists between the 2 forests and from the Central Admin server I am able to ping/RDP the DC in the external domain without any problems.

    Kind regards,
    G
    Friday, February 12, 2010 8:48 AM
  • Hi:

    Well let us check ULS logs then (location is ...\12\Logs) and debug if that can provide some help.Others things and settings to me seems to be perfect. Try to have a full Add Import.

    Thanks,


    Best Regards, Mukesh Giri Sr.System Executive
    Friday, February 12, 2010 11:02 AM
  • Hi,

    In the log file location on the CA server, there are many different logs.  Is there a particular one which I should be looking for?  The most recent is named "machinename-20100212-1216" and basically all it has in there are lines and lines of this:

    02/12/2010 12:16:45.06  w3wp.exe (0x0B34)                        0x18C0 Excel Services                 Excel Calculation Services     8jg2 Medium   ResourceManager.PerformCleanup: Memory Manager: CurrentSize=517664768. 
    02/12/2010 12:16:45.06  w3wp.exe (0x0B34)                        0x18C0 Excel Services                 Excel Calculation Services     8jfe Medium   BackgroundTaskManager.ExecuteBackgroundTasks: Finished task Memory Manager.PerformCleanup 
    02/12/2010 12:16:46.99  OWSTIMER.EXE (0x08B4)                    0x08BC Windows SharePoint Services    Timer                          5uuf Monitorable The previous instance of the timer job 'Shared Services Timer Job', id '{DC58493B-2BF0-4A61-8DAA-8DBD89566987}' for service '{A9E60C7B-715F-4125-AB86-51FD52DD3D5F}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs. 
    02/12/2010 12:16:46.99  OWSTIMER.EXE (0x08B4)                    0x08BC Windows SharePoint Services    Timer                          5uuf Monitorable The previous instance of the timer job 'Shared Services Timer Job', id '{DC58493B-2BF0-4A61-8DAA-8DBD89566987}' for service '{A9E60C7B-715F-4125-AB86-51FD52DD3D5F}' is still running, so the current instance will be skipped.  Consider increasing the interval between jobs. 

    Thanks,
    G

    Friday, February 12, 2010 11:39 AM
    • Marked as answer by GuYuming Friday, February 26, 2010 9:39 AM
    Thursday, February 18, 2010 6:36 AM
  • Hi all,

    Sorry for the delay, but I just wanted to report back and thank you for your guidance.  Our issue has been resolved and it was due to the network management team not having opened the correct ports.

    Many thanks once again!
    G
    Friday, February 26, 2010 10:27 AM