I'm not entirely sure what would cause those errors - but as an alternative approach: do you really need to be replicating the alert manager 4.7.0 install packages, given that the product is completely end-of-life?
If not - I would delete the packages from your master repository (using the ePO GUI) and then try the replication again.
Removing the package doesn't help.
The same error occurs with the next package (Current\EEADMIN_1000\Install\0000\MfeEEAgent32.msi)
Hm - not that then
If you check the agent log on the SA machine, are there any errors at the time of replication?
Possibly an obvious thing but is there sufficient drive space? (Both on the drive where the SA repo is and on the drive hosting the temp folder)
A client machine could conceivably have a lock on the SA repo - restart the framework service on the SA machine and try the replication again?
The sync is busy atm without errors
Someone used the SA as a backup device and the drive ran out of diskspace.
I've cleaned it up and it seems to work now.
No disk space would do it
Glad it's OK now -