Locked file in SharePoint Configuration Cache

Comments

8 responses to “Locked file in SharePoint Configuration Cache”

1. 

   sachin

   November 18, 2013

   Thanks,

   Same thing happened to me. Your post was the only one i could find reagarding this error. I ended up rebooting the server as i found this post at the very last moment befor server was going to reboot. Anyway whatever you explained, i was able to see from the process and was exact same issue.

   Thank you very much for the post.

   Reply
2. 

   Chet Chudasama

   August 19, 2014

   Thats absolutely fantastic – thanks you!!!

   Reply
3. 

   Rich

   April 7, 2015

   Here is a script you can use… buddy sent this my way:

   # Script created by Ingo Karstein (http://ikarstein.wordpress.com)
   # http://support.microsoft.com/kb/939308

   $cacheFolderRoot = Join-Path ${env:ProgramData} “Microsoft\SharePoint\Config”
   $cacheFileCopy = Join-Path ${env:temp} “cacheFileTmp.ini.ik”

   Write-Host “” -ForegroundColor DarkBlue
   Write-Host “Starting” -ForegroundColor DarkBlue

   if( Test-Path $cacheFileCopy -PathType Leaf) {
   write-host “Cache File copy lopcation does already exist. Please remove it: $($cacheFileCopy)” -ForegroundColor Red
   return
   }

   Write-Host “Looking for cache folder” -ForegroundColor DarkBlue
   $cacheFolder = @(GEt-ChildItem -Path $cacheFolderRoot | ? {Test-Path $_.FullName -PathType Container} | ? {Test-Path -Path (Join-Path $_.FullName “cache.ini”) -PathType Leaf})

   if( $cacheFolder -ne $null -and $cacheFolder.Count -eq 1) {
   $cacheFolder0 = $cacheFolder[0].FullName
   Write-Host “Cache folder found: $($cacheFolder0)” -ForegroundColor DarkBlue
   $cacheFile = join-path $cacheFolder0 “cache.ini”
   Write-Host “Cache ini file: $($cacheFile)” -ForegroundColor DarkBlue

   Write-Host “Stop SharePoint timer service” -ForegroundColor DarkBlue
   stop-service sptimerv4

   Write-Host “Copy cache.ini to it’s temp location ($($cacheFileCopy))” -ForegroundColor DarkBlue
   copy-item -path $cacheFile -Destination $cacheFileCopy -force

   Write-Host “Set the content of cache.ini to “”1″”” -ForegroundColor DarkBlue
   “1” | set-content $cacheFile -encoding ascii -force

   Write-Host “Remove all .XML files from the cache folder” -ForegroundColor DarkBlue
   get-childitem $cacheFolder0 -filter “*.xml” | remove-item -force -confirm:$false

   Write-Host “Start SharePoint timer service” -ForegroundColor DarkBlue
   start-service sptimerv4

   $xmlFound = -1
   $xmlFoundLast = -1
   $eqCount = 0

   Write-Host “Now the cache will be recreated… Waiting… This will take a minute or so…” -ForegroundColor DarkBlue
   write-host “(every second a dot will appear on the end of the next line)” -ForegroundColor gray
   do {
   write-host “.” -nonewline -ForegroundColor Magenta
   start-sleep -second 1
   $xmlFoundLast = $xmlFound
   $xmlFound = (@(get-childitem $cacheFolder0 -filter “*.xml”)).Count
   if( $xmlFound -eq $xmlFoundLast ) {
   $eqCount++
   } else {
   $eqCount = 0
   }
   } while ($eqCount -lt 30)

   Write-Host “”
   Write-Host “Done” -ForegroundColor DarkBlue

   $a = get-content $cacheFileCopy
   $b = get-content $cacheFile

   if( $a -ne $b ) {
   if( [int]$a -gt [int]$b ) {
   write-host “An error occured. the content of the cache file is not identically to it’s value before processing.” -ForegroundColor Red
   write-host “Old: $($a)”
   write-host “New: $($b)”
   } else {
   write-host “MAYBE an error occured. the content of the cache file is not identically to it’s value before processing.” -ForegroundColor DarkYellow
   write-host “Old: $($a)”
   write-host “New: $($b)”
   }
   } else {
   write-host “Processing finished successfully! You need to execute the script on every server!!” -foregroundcolor darkgreen
   remove-item $cacheFileCopy -Force -confirm:$false
   }
   } else {
   write-host “Could not find the cache folder or found too much cache folders!” -foregroundcolor red
   }

   Reply
4. 

   Thembane

   August 29, 2017

   Thanks mate, i googled for days before your valuable info.

   Reply
   1. 

      derek

      August 29, 2017

      Glad to help. Sorry it took so long for you to find the post!

      Reply
      1. 

         Nektar A

         October 13, 2020

         Dear Derek,

         you’d be happy to know that even in 2020 your article is a lifesaver! 🙂
         There are still many old systems under maintenance that need this to get
         back to normal.
         I can’t thank you enough!

         Reply
5. 

   Susan Barnes

   December 6, 2017

   Great post Derek. After reading, I stopped both Forefront services, and then the bad file was deleted, This way I did not have to re-provision the User Profile Sync (always a chore). Thanks for the assist!

   Reply
6. 

   Super Dave

   April 23, 2020

   you’re Awesome!

   Reply