| Event Id | 5079 |
| Source | Application Center |
| Description | Synchronization could not rename the file %Path% for session %ReplicationID% and job %ReplicationJobID%. Status is %Status%%StatusMessage%. |
| Event Information | According to Microsoft: CAUSE: When you perform automatic synchronization and a file is either modified while it is being replicated or the file is replicated by two different replication sessions at the same time, multiple threads may try to apply the same file on the target at the same time. When this occurs, one or more of the threads may fail because another thread may have locked the file. When files are applied, they are moved from $ACSRPL$ to their target directory with names such as $n$.$r$, and the files are then renamed to the original name. If the rename is unsuccessful, the files are left in the target directory with the $n$.$r$ name. RESOLUTION: Full synchronization transfers the correct version of the file and deletes the $n$.$r$ file. Microsoft recommends that you do not run multiple deployments or synchronizations that involve the same files at the same time. |
| Reference Links | Application Center 2000 Replication Logs Event 5079 and Creates Temporary Files with Names such as $0$.$r$ Event ID: 5079 Replication UpdateListApply FileTempMoveFailed |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.