Web Deployment Tool (MS Deploy)
Web Deploy 2 RC: Maximum number of sync passess has been exceeded
Last post Jan 25, 2012 08:19 PM by jamesvecore
Jan 02, 2011 02:55 PM|LINK
I recently upgraded to Web Deploy 2 RC, and I'm getting the error below when running a synchronization for a package. Any ideas on what could be causing it?
The synchronization is being stopped because the maximum number of sync passes '5' has been exceeded even though all the changes could not be applied. This could occur if there are external changes being made to the destination.
Jan 04, 2011 04:53 PM|LINK
Could you give us a little more detail on your scenario? Is this a package for a site deployment? Does the external changes explanation sound unlikely (have you tried with site stopped)? Is this an error you did not see using Web Deploy version 1 for
the same deployment? Please let us know.
Jan 05, 2011 12:16 AM|LINK
The package is deploying 2 things: A directory path and a website.
The external changes does sound unlikely... the site is an internal test site with no activity.
This error didn't happen with Web Deploy 1.1... but the deploy seemed to hang (I would have to kill it after a dozen passes). I reported that problem here: http://forums.iis.net/t/1173186.aspx.
One thing to mention: The content of the website that I'm deploying actually points to a folder under the directory. So the archive.xml attached to my previous post has the following 2 elements:
1) dirPath: D:\MetraTech\RMP
2) Web site (content located in D:\MetraTech\RMP\UI)
In addition, there are a few XML files under these folders that are updated by Web Deploy based on the parameter configuration.
Could this be causing the issues? Is it possible that as part of deploying one of the elements, Web Deploy thinks that the other was affected by "external changes"?
Jun 06, 2011 11:29 AM|LINK
I'm getting this problem as well. Did you ever find a fix for this?
For me it seems to happen when the package is large. There is no other process running that is modifying the contents of the application directory. I even stop the website using remote powershell but still get this error.
Jan 25, 2012 08:19 PM|LINK