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.

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??

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.

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?

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 sourceStarting incremental import of PEOPLE_IMPORT content sourceJob '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 sourceJob '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.

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?

Yes it is running on all servers.

I have the same problem. Warning occurs, even though schedules are configured correctly and imports are running fine.

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.

Annoying to say the least. We've patched up to the October Update and it is still occuring exactly as you all describe on allour farms.

We're also seeing this.

Same here, December update installed.

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.

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

any update, i am also experinecing the same issue

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

Same here. Would be great is someone from MS could confirm/deny this!

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.

Hi Any updates on this Has anyone been able to resolve this problem? I'm having the exact same problem. Thanks

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.

I assume that there are no answers to this issue?

I assume that there are no answers to this issue?

Yeah ... i have the same problem too ...it's unbelievable ! :))

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 !