I had a similar problem and fixed it by changing the publish method from ZipDeploy to MSDeploy. But I still don't have an idea what causes this problem.