On a newly installed server we have installed webdeploy 3.6 and started to deploy our web application with the dbFullSql provider.
The deployment package consists of a ASP.NET Web Application and a SQL file to be deployed with the dbFullSql provider. It appears that the web management service goes into an endless loop and starts eating memory when the deployment occurs and it never ends.
Interestingly this only occurs after access is granted to the database: If I disallow the credentials for connection to the database this is reflected as a failure in the web deployment. However, following the happy path results in the situation above.
Does anyone know how to resolve this situation?