Random Files Fail to Deploy to Live IIS Server

We are planning to use OpenDeploy 5.6 to deploy files (using file list-based deployments) from our TeamSite 6.1 server to our production web servers, which are Windows NT with some as-yet-undetermined version of IIS (I'm waiting to hear back from the folks in IT). Tribal knowledge is that they are using IIS 4, but we are waiting for official confirmation from IT.

During initial testing of the deployments, we encountered what appears to be the "Random Files File to Deploy to Live IIS Server" problem described in Knowledge Base Articles 1353 and 48488.

The symptom we are seeing matches the synopsis in 1353 - "Deploying files to a live IIS server causes random files to fail." According to the same article, "This is a known issue with IIS server as open files are locked for 60 seconds by default".

Article 48488 says that "IIS 4 has a known issue regarding holding locks on files, which is corrected in IIS 5".

Can anyone confirm that this problem goes away after upgrading to IIS 5?

We tried the workaround recommended in the articles (adding svrTryCount and svrTryInterval attributes to the transferRules element in the deployment configuration file), but that does not seem to help.

Thanks!

Find more posts tagged with

Comments

Adam Stoller

Isn't IIS up to version 6 ?

Regardless - I would strongly recommend upgrading from version 4 - I remember it causing a lot of problems in the past when I had to deal with it.

On the other hand I recall IIS 6 starting out in "hardened" mode - or some such security tag-line - and it used to screw up the TS post-install process (this was with 4.x I think, or perhaps early versions of 5.x -- the same problems may no longer exist due to the introduction of iw-webd)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Gregg Faus

IIS6 = Windows 2003

We've been sending out deployments to Win2k boxes (IIS 5) for years now without problems. For the short time that we deployed to IIS4 I didn't notice this problem, but obviously you do.

Tell your IT staff to upgrade those NT boxes. NT support is about to expire at the end of 2004 anyway unless you have a custom contract w/ Microsoft.

civ3

Hi

Just to give you another thought of this problem. Try to see if there is any process other than IIS locks those random files. We used to have this kind of problem regarding failure to update existing PDF files on IIS server (version 5). Finally we found those PDF files were locked by a search engine process running on the web server. We have to stop this particular process before the deployment and restart it after the deployment to solve this issue.

civ3.