Having a lot of offline drops seems to break deployment (File locked)

I have a deployment to a customer’s environment where I need the offline package drop (what a life saver!).
There are currently ~10 but this will grow into more than 20.

When I make a deployment it fails quite reliably (10 out of 10 today) with the following error:
The step failed: Activity Stop clients on XXX failed with error ‘The process cannot access the file ‘\localhost\C$\Drops\ABC\DEF\0.0.120\Scripts\Stop clients.ps1’ because it is being used by another process.’.

Another one is:
The step failed: Activity failed with error 'Access to the path ‘\localhost\C$\Drops\ABC\DEF\0.0.120\Calamari\de’ is denied. (showing in each individual drop step all kind of country codes)

Another one is:
The step failed: Activity Stop clients on XXX failed with error ‘The process cannot access the file ‘\localhost\C$\Drops\ABC\0.0.120\Scripts\Stop clients.ps1’ because it is being used by another process.’.

Seems like if there are more than one offline package drop the writing to the ps1 is not going as fluent as one would expect :wink:

For now I just try to retry until it works (proves unsuccessful today). Any hints on at making it work in the meantime would be much appreciated!

This was actually solved quite easily by having different package drop locations for each environment. Liked the way it worked by putting it all in one (easier deployment) but do understand this might not be a usual use case!

Notice:

This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.