Failed Deployment creating locks?

System

We see a new lock on an adjacent file when a deployment fails because a file is locked. So after the first failure, there are 2 locked files. After the next, 3 - and so on.

1) Could there be a bug in OD 6.1.1 causing this?
2) Can OD be told to ignore locks, especially if it's the task holding the lock? I see the 4 parms rmReadOnly, svrTryCount, svrTryInterval, and scrTryDisableOverwrite. I'm not quite sure what the 4th does, but the first 2 don't help if the file's locked and the third deals with read-only, not locked, files. Is there another parm that might help?
3) Is there an easy way to find all locked files (Windows Server 2003)?

Thanks in advance,
Peter Buck

hitc

I don't think it's a bug of OD...if a file is locked by Windows or another process OD will not be able to overwrite it and will rollback.
Are you trying to deploy under adirectory in IIS?if you stop/start OD,does the deployment is failig again?is deployment always failing on the same file?Could you provide me with a log and or a errno(sometimes it's looked like a file is locked but the problem is something else)?

The parameters are working as follow,they can be the solution if some files are locked for a few second by a process or IIS:
- svrTryCount (Windows only) — enter the number of times OpenDeploy will attempt to deploy the file to the target. This feature works in conjunction with Microsoft IIS, and is designed to accommodate times of heavy production server traffic.
- svrTryInterval (Windows only) — enter the amount of time in seconds OpenDeploy waits between deployment attempts. This feature works in conjunction with Microsoft
IIS, and is designed to accommodate times of heavy production server traffic.
- svrTryDisableOverwrite (Windows only) — indicate whether (yes) or not (no) to disable the ability of OpenDeploy to deploy files to a server even if the svrTryCount and svrTryInterval elements are specified. This feature works in conjunction with
Microsoft IIS, and is designed to accommodate times of heavy production server traffic.
Default value is no.
- rmReadOnly (Windows only) — indicate whether (yes) or not (no) you want a deployed file to be able to overwrite its read-only target equivalent. If this feature is enabled with a value of yes, OpenDeploy will remove the read-only attribute from the target file, allowing the deployment.

There is no other parameters that help to manage the locked files

I'm not sure there is an easy way to find all locked files,I'm not a Windows specialist