I have faced this issue while trying to modify list items of a list. This issue encounters if the file system cache content on the SharePoint server is newer than the content present in the configuration database. One have to clear the cache manually to get rid of this issue. Sometimes it get solved by restarting, if luck is with you, otherwise this issue will always bugs.
Timer service restart could be one another option to try. But recommend you must follow one of the two possible ways to solve this issue:
I. Manual Steps:
- Need to stop the SharePoint Timer service: Navigate to Start > Administrative Tools > Servicesor go to run(Windows+R) command and type msc.
- Locate the SharePoint Timer Service, and right click on this service and click on Stop
- Close the Services window (In case you are performing these actions on Production/Test. Do this on each front end server)
- In Windows Explorer, locate and then double-click the following hidden folder.
- There may be two folders with a GUID name in the config directory. One has persisted files in it. You will be working with the one that has XML files and a cache.ini file in it. The Drive placeholder specifies the letter of the drive on which Windows is installed. By default, Windows is installed on drive C.
- The GUID placeholder specifies the GUID folder.
- The ProgramData folder may be hidden. To view the hidden folder, Navigaete to Tools > Folder Options > View Tab > Advanced settings. Click Show hidden files and folders under Hidden files and folders, and then click OK.
- Take a Backup of the ini file.
- Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
- Now delete all contents of Cache.ini. Double-click the Cache.ini file to open it. Click on the Edit menu, click Select All and click Delete.
- Type 1, and then click Saveon the File menu.
- On the Filemenu, click Exit.
- Start the Timer service. To do this, follow these steps: Navigate to Start > Administrative Tools > Servicesor go to run(Windows+R) command and type msc.
- Locate the SharePoint Timer Service, and right click on this service and click on Start
Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
- Make sure that the Cache.ini file has been updated. For example it should no longer be 1 if the cache has been updated.
Both methods does same thing, choice is all yours depending upon the comparability, permissions, time and of course ease.
Happy SharePointing 🙂