none
User Profile Import Warning RRS feed

  • Question

  • On every environment we have a warning appear when the User Profile begins.
    It delays once, twice or three times and then stops until the next profile
    import. This happens on both full and incremental imports every single time
    in every environment. Granted, I don't know of any errors or problems caused by this, but
    we are trying to get things polished for production.

    Has anyone else seen this?


    Event Type: Warning
    Event Source: Office SharePoint Server
    Event Category: Office Server Shared Services
    Event ID: 7078
    Date: 11/7/2007
    Time: 3:03:12 AM
    User: N/A
    Computer: MOSS30
    Description:
    Job 'User Profile Incremental Import Job' failed. It will be re-tried again
    in 240 second(s).

    Reason: User profile import is in progress!Import could not be started.
    Please start import later or stop import now for new import to start.

    Techinal Details:
    Microsoft.Office.Server.UserProfiles.ImportInProgressException: User profile
    import is in progress!Import could not be started. Please start import later
    or stop import now for new import to start.
    at
    Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.StartImport(Boolean fIncremental, String contentSourceName, Boolean fByPassAdminCheck)
    at Microsoft.Office.Server.UserProfiles.UserProfileImportJob.Execute()
    at Microsoft.Office.Server.Administration.JobHandler.Execute(Object
    state, Boolean timedOut)

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Thursday, November 29, 2007 11:23 PM

All replies

  • The error suggests that there is already an import running. Didn't you by any chance configure the full and incremental import on exactly the same schedule??

     

    Go to the Operations tab and click Timer Job Status in the right column. Check if there is a job with the name 'User Profile Incremental Import Job' or 'User Profile Full Import Job' currently running.

     

    What happens when you start the import manually??

    Tuesday, December 4, 2007 3:46 PM
  • No, full and incremental are on seperate schedules.  Full is only weekly and incremental is nightly.  The warning occurs during every scheduled import. 

     

    If I start the job manually, it completes without any warnings.  Any time it is scheduled the warning occurs.  That led me to believe that it had something to do with another timer job, because the profile import occurs "on the hour".  There are only four timer jobs that occur every hour on the hour, all having to do with "Profile Synchronization".  So I disabled those four, hoping that it would explain the conflict.  But the warning still occurs regardless.

     

    Thank you for looking at this.

    Tuesday, December 4, 2007 4:08 PM
  • Have you changed any service accounts (password of changed to other account)?? Sounds a little like the import runs under an account which does not have permissions to do the import. What account is the Windows SharePoint Timer Service running under?? Is this the account you used as you "configuration database" account (account entered when running the Configuration Wizard after installing MOSS)??

     

    Are there any log entries about this profile import in the logs in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\Logs at the time the import runs?

    Wednesday, December 5, 2007 9:34 AM
  •  Yorick wrote:

    Have you changed any service accounts (password of changed to other account)?? Sounds a little like the import runs under an account which does not have permissions to do the import. What account is the Windows SharePoint Timer Service running under?? Is this the account you used as you "configuration database" account (account entered when running the Configuration Wizard after installing MOSS)??

     

    It is most definitely not a permissions problem.  The account has access to AD and to run everything.  In fact because this is in a development environment, I have the same account doing everything and is a local admin. 

     

     Yorick wrote:

    Are there any log entries about this profile import in the logs in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\Logs at the time the import runs?

     

    I spent quite a bit of time on this after you mentioned it.  I turned on verbose logging to be able to see exactly what was happening.  Here's a snippet.

     

    Starting incremental import of  PEOPLE_IMPORT content source
    Starting incremental import of  PEOPLE_IMPORT content source
    Job 'User Profile Incremental Import Job' failed. It will be re-tried again in 60 second(s).  

    Reason: User profile import is in progress!Import could not be started.  Please start import later or stop import now for new import to start.  Techinal Details: Microsoft.Office.Server.UserProfiles.ImportInProgressException: User profile import is in progress!Import could not be started.  Please start import later or stop import now for new import to start.     at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.StartImport(Boolean fIncremental, String contentSourceName, Boolean fByPassAdminCheck)     at Microsoft.Office.Server.UserProfiles.UserProfileImportJob.Execute()     at Microsoft.Office.Server.Administration.JobHandler.Execute(Object state, Boolean timedOut)

    Starting incremental import of  PEOPLE_IMPORT content source
    Job 'User Profile Incremental Import Job' failed. It will be re-tried again in 120 second(s).  

    Reason: User profile import is in progress!Import could not be started.  Please start import later or stop import now for new import to start.  Techinal Details: Microsoft.Office.Server.UserProfiles.ImportInProgressException: User profile import is in progress!Import could not be started.  Please start import later or stop import now for new import to start.     at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.StartImport(Boolean fIncremental, String contentSourceName, Boolean fByPassAdminCheck)     at Microsoft.Office.Server.UserProfiles.UserProfileImportJob.Execute()     at Microsoft.Office.Server.Administration.JobHandler.Execute(Object state, Boolean timedOut)

    Starting incremental import of  PEOPLE_IMPORT content source

     

    After this last start it completes successfully.  The first two on the list happen at 9:00:01 and 9:00:48, respectively.  The first failure occurs at 9:00:49.  That leads me to believe that for some reason SharePoint is kicking off one import and then another right afterwards.  Trust me we have only scheduled one.  And I have duplicated this in 9 different environments.  Then it tries again, but the first one is still running so it fails too.  Then the final attempt on this list completes successfully. 

     

    Thanks to anyone that looks at this. 

Friday, December 7, 2007 4:50 PM
  • It does sound like SharePoint is starting multiple jobs at the same time and then complains there are multiple jobs running. I haven't noticed this behaviour before on any environment I have installed.

     

    Just to be sure: Is the Windows SharePoint Services Administration service running?

    Tuesday, December 11, 2007 3:26 PM
  • Yes it is running on all servers.

     

    Tuesday, December 11, 2007 3:49 PM
  • I have the same problem. Warning occurs, even though schedules are configured correctly and imports are running fine.

     

    Friday, December 14, 2007 9:47 AM
  • I have the same issue on my server farm. I thought initially, that Sharepoint starts the import on all 3 Sharepoint servers and than complains that it cannot start the import more than once, but in fact it uses only the indexing server (which is correct) but seems to start it at least twice. The odd thing is, although my import log says it completed after 13 minutes the last warning occurs 15 minutes after the import starts.
    Has anyone an idea how to fix it? I mean it's not that bad but still annoying. I have MOSS 2007 SP1 and also the recent infrastructure upgrade.
    Friday, August 1, 2008 7:31 AM
  •  Annoying to say the least.  We've patched up to the October Update and it is still occuring exactly as you all describe on all our farms.
    Wednesday, January 7, 2009 2:01 PM
  • We're also seeing this.
    Monday, January 12, 2009 8:00 AM
  • Same here, December update installed.
    Sunday, February 8, 2009 7:00 PM
  • I'm also seeing the same exact issue in 3 different farms and I have the incremental and full scheduled to occur at different times. I know it is just a warning but it would be nice to clean up events like this on servers so I foresee a patch coming from MS for this hopefully.
    Friday, February 27, 2009 8:23 PM
  • Hi all!

    I have only recently been introduced to SharePoint, but I'm going to give it a try here.
    It seems that SharePoint is throwing the error due to a job that has expired in SQL Server. When you access your management studio, you should probably deleteExpiredJobs in the Server Agent.

    I haven't had time to test chandima's method, but I will try to get to it by the end of today!

    http://www.chandima.net/Blog/archive/2008/02/20/troubleshooting-event-18456.aspx

    R.



    EDIT:

    I have discovered some other cause. If the first method (above) shouldn't seem to work, try checking your search services and see if it is running. If not you must have this service up and running before attempting to restore succesfully.
    Monday, March 2, 2009 8:27 AM
  • any update, i am also experinecing the same issue
    Monday, March 16, 2009 10:34 AM
  • I still see the same error (16 months after my original post), in every environment I have, even single server dev environments.  I don't know any negative effects, but it would be nice if this would go away (through a hotfix)...  
    • Proposed as answer by Falak Mahmood Friday, February 17, 2012 10:02 AM
    • Unproposed as answer by Falak Mahmood Friday, February 17, 2012 10:02 AM
    Monday, March 16, 2009 9:00 PM
  • Same here. Would be great is someone from MS could confirm/deny this!
    Friday, July 10, 2009 6:38 AM
  • Hi Any updates on this.

    I am getting this on one of my web front ends.  My profile imports seems to be running fine and able to complete it but it is logging this warning message on my web front end, everytime when it is scheduled for full imports.

    Thursday, April 15, 2010 8:53 AM
  • Hi Any updates on this

    Has anyone been able to resolve this problem?  I'm having the exact same problem.

    Thanks

    Tuesday, July 20, 2010 7:01 AM
  • I assume that this issue was not resolved but rather ignored?

     

    Experiencing the same issues and could not find any resolution.

     

    If someone have found a solution, could they post it?

     

    Thanks.

    Monday, February 14, 2011 8:20 AM
  • I assume that there are no answers to this issue?
    Wednesday, March 9, 2011 5:34 AM
  • Yeah ... i have the same problem too ...

     

    In Central Administration

    >Services

    >User Profile Syncronisation Service

    Stop and Start this service and it should work after !


    Moderator Note: NEVER propose your own posts as answers. The function is for proposing the good answers of other people.
    • Proposed as answer by Jourjaque Monday, April 4, 2011 12:55 PM
    • Unproposed as answer by Mike Walsh FIN Friday, July 15, 2011 3:41 PM
    • Edited by Mike Walsh FIN Friday, July 15, 2011 3:42 PM Moderator Note added about not proposing own posts
    Monday, April 4, 2011 9:05 AM
  • Has anyone found a solution to this issue?

    In addition to the error message the first poster mentioned I'm also seeing Event ID 5782 (see below) thousands of times (I guess one for each user import) each day. This happens on multiple farms and where I have August 2010 CU applied (version 12.0.0.6545).

    As others mentioned import seems to work fine and this issue happens for both scheduled import as well as manual ones.

    Please note '' is NOT name of my SSP - not sure where that coming from. My SSP names are different in different farms but the same '' error showing up everywhere.

     

     PS. Can moderator please remove the self 'proposed answer' - as seems to me proposer was confused thinking this was a SP 2010 issue.

     

     

    Event Type:	Warning
    Event Source:	Office SharePoint Server
    Event Category:	User Profiles 
    Event ID:	5782
    Date:		7/14/2011
    Time:		6:07:35 PM
    User:		N/A
    Computer:	SP_APP
    Description:
    Provisioning for Shared Services Provider '' has failed and will be retried.
    
    Reason: 
    
    Technical Support Details:
    㝘ƕ㜰ƕ
    
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    

     


    BlueSky2010

    Friday, July 15, 2011 3:36 PM
  • >  PS. Can moderator please remove the self 'proposed answer' - as seems to me proposer was confused thinking this was a SP 2010 issue.

    Already done before I saw your post. I must have missed the self-proposal first time around.


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
    Friday, July 15, 2011 3:43 PM
  • to my investigation, looks like import is starting two times, since import get triggered from timer job, try to sync time with NTP server. not to worry much with error since first import always finish successfully.
    gurvinder
    Thursday, August 18, 2011 1:18 PM
  • Hi Gurvinder,

    I suspected duplicate timer job too and tested running the import manually and I still get all those warnings. Luckily import works fine it's just the nuisance getting thousands of warnings in the log file.

    Does not look like there is a solution to this issue???

    Thank you!


    BlueSky2010
    Friday, August 26, 2011 1:21 PM