An update conflict has occurred, and you must re-try this action. The object UserProfileImportJob – SharePoint 2013 User Profile Service Application

Issue Statement

1. Trying to Start a User Profile Synchronization through User Profile Application.
2. Action completes but still the status is idle.
3. After few minutes still the status is idle and seems there’s something wrong.
4. Getting in to "Configure Synchronization Timer Job" and trying to Start sync through "Run Now"

5. Boomed ! and here it showed the real thing saying "Error Occurred when trying to run User Profile Synchronization in SharePoint 2013 "An update conflict has occurred, and you must re-try this action. The object UserProfileImportJob Name=User Profile Service Application Name _ProfileImportJob was updated by Domain\Service Account, in the OWSTIMER (14108) process, on machine SPAPPSVR. View the tracing log for more information about the conflict".

This problem occurs if the contents of the file system caches on the Web frontend Servers are newer than

the contents of the backend Configuration Database. this can even happen in standalone setups like i faced just now.

Resolution

To resolve this we have to clear the file system cache on all Servers which are running SharePoint Time Service (this will run in all SharePoint Servers except the Database Servers).

Let’s do below few steps and Microsoft also has written the guidance for the same in KB-939308.

Before we proceed take a note that if your environment is a Production and running any scheduled stuff such as Workflow or whatever the timer service involved tasks do not execute this during peak hours (Day Time) try to make it in night time which is off peak as stopping Timer will cause re-starting of scheduled tasks which is critical when you are in production.

1.Type Services.msc in RUN and find the SharePoint Timer Service there and Stop it.

2.Navigate to the Cache Folder

In Windows Server 2008/2012 it’ll be here – C:\ProgramData\Microsoft\SharePoint\Config

For 2003 here – C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config

(Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)

3.You will see GUID Named folder inside it and Find the Cache.ini file and Back It up somewhere

4.Delete all the XML configuration files in the GUID folder except the Cache.ini file. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt. Note : Do not Delete the folder or Cache file when you perform deletion.

5.Go ahead and double click on Cache.ini file to open it.

6.Select all inside it and delete

7.Then save and Close the window

8.Go to Services again and now Start the SharePoint Timer Service

9.The file system cache is re-created after you perform this procedure. You may see some XML files are keeping generated inside the folder. Make sure that you perform this procedure on all servers in the server farm.

10.Go ahead and Start the Profile Synchronization now, it will sync smoothly.

Advertisement

There was no endpoint listening at http://ServerName:5725 ResourceManagementService/MEX that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details

Error Occurred when Creating a New Connection in SharePoint User Profile Service Application.

There was no endpoint listening at http://ServerName:5725 ResourceManagementService/MEX that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

Quite scary error which seems like due to ports blocking ? Not really, In my case it was Forefront Identity Manager Service which was stopped.

I remember that I restarted this server after doing some heavy site collections creation and noticed the FIM Service has not been started automatically though it was set to automatic start. Just started it from Services and Connection came back to work.

You will get "LDAP Server is Unavailable" Massage if you have checked SSL option at the same page (will depend on the environment that you are dealing with).

“Sorry We’re Having trouble reaching the server” Error Occurred When adding user to a permission level in SharePoint 2013.

You may face to this problem when you are running SharePoint 2013 with limited Hardware Resources. When Processor and Memory utilization is higher you may get this frequently. This can be even worse if you are running SharePoint in a VM with less resources.

In my test environment I had 8 GB Ram for SharePoint Server 2013 ENT which is not really recommended but I had no option due to my hardware box was fully utilized so couldn’t allocate much resources to this VM.

To solve this out temporary we can search a different user instead of keep trying to add the same one. Wait a 30 second and try to add "Everyone" –> Error again –> then try another –> now try your originally needed one –> success !

Though it’s a development environment you have to at least allocate 12 GB of memory with Minimum 2-4 Cores v processor if it’s SharePoint 2013 which is depends on how many web applications/Site collection being created and used frequently for your day to day developments.

Refer here for Microsoft recommendations on hardware perspective – http://technet.microsoft.com/en-us/library/cc262485.aspx#reqOtherCap