To resolve the SharePoint server error event id 6482, let’s overview the history behind this error.

The synchronization service found under “Services on server” in SharePoint 2010, you encounter an error.

“An update conflict has occurred, and you must re-try this action. The object UserProfileApplication Name=User Profile Service Application was updated by [User]”


 The details of the error are mentioned below.

ULS:

“An update conflict has occurred, and you must re-try this action. The object UserProfileApplication Name=User Profile Service Application was updated by [User]”

ULS:

SharePoint Foundation Runtime Unpredicted-

Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException

An update conflict has occurred, and you must re-try this action. The object UserProfileApplication Name=User Profile Service Application was updated by [User], in the OWSTIMER (3456) process, on machine [Server Name].

Event Viewer:

The Event 6482 is recorded once every minute and consist of the following information:

An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by [User], in the OWSTIMER (1756) process, on machine [Server Name].

The reason behind this Error:

The error 6482 occurs when the data of the system cache file is latest compared to the information of the configuration database. After performing a system recovery, one might have to manually erase the file system cache of the localhost.


How to Fix SharePoint server error 6482 Manually?

To solve the issue, erase the file system cache on all servers of the internet on which the Windows SharePoint Services Timer service is working. Follow the below- mentioned instructions to resolve SharePoint server error event id 6482.


  • First, pause the Windows SharePoint Services Timer service 
  • Browse the cache folder
    In Windows 2008 server, the configured cache current path is: Drive:\ProgramData\Microsoft\SharePoint\Config
    In Windows 2003 server, the configured cache path is: Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
    Navigate the folder that includes the “Cache.ini” file in it.

Note: The Application Data folder may be unrevealed. To access the hidden folder, modify the folder options as required.

  • Restore the Cache.ini file.
  • Erase all the existing XML configuration files in the GUID folder. Follow this to verify whether the GUID folder is replaced by new XML configured files when the cache was restored.

Note: When you erase the cache file of the GUID folder, you must make that do not eliminate the GUID folder and Cache.ini file stored in it.

  • Double-click the Cache.ini file stored in the GUID folder.
  • In the Edit menu, hit Select All and then click Delete. Type 1 and then save the changes by going to the File menu. Next, return to the File menu, press the Exit tab.

  • Begin the Windows SharePoint Services Timer service.

Note: The file system cache then recreates itself after the procedure is initiated. Remember, perform the procedure on all servers of the internet.

  • Make sure the Cache.ini file is back to its previous value. For eg, recheck the value of Cache.ini file. Its value should not be 1.

 

If the user finds it difficult to operate with the above instructions, then they can try using a third-party solution to resolve the error 6482. One such utility is SharePoint Server Recovery. The utility comprises the two modes of recovery for handling corruption, allows previewing erased files of the database, facilitates scanning of existing MDF files, a hierarchical preview of files before downloading, auto-create a LOG file regarding recovery process, Intuitive GUI for novice users, etc.

 

Conclusion:

To fix the SharePoint server error event id 6482, we have discussed the appropriate solutions and reasons why the particular error occurs unexplainably. To fix this inconsistency of the SharePoint server, one must select a commercial utility that is specially created for this sole purpose. I hope you all find the above blog informative and helpful.