Instances "Busy" after a deployment upgrade


While doing a deployment upgrade, in some cases the instances keep in "Busy" status. This is because the folder "C:\Resources\Directories\<deploymentId>_Sites\root" exists and it's not a symbolic link (normally because there is a log file inside the "logs" subfolder), causing an error in the symbolic link creation.

Workaround: RDP into the instance and manually delete the folder. In a few seconds the symbolic link will be created automatically and the site will be running.

This will be fixed in the next release.


davidjrh wrote Jan 17, 2014 at 11:10 PM

Fixed in changeset 27291

wrote Jan 17, 2014 at 11:11 PM