Most likely that file is being read or utilized by another process. What you might do is try a simple iisreset
on the production server to reset IIS, then try the synchronization again. This should free up the resource that might have been using it before.