Multiple Hangs in version 7.0

[DougFarmer123]

I installed version 7.0 late last fall as I needed the VS 2008 capability. At the same time, I loaded VS 2008. Ever since then I have been experiencing two problems.

We run multiple (10) builds every night.

The first issue is that a file system step hangs with a "file in use" or "access denied" message. I cannot rule out our own network, but it is interesting this did not happen before. File system steps are like Delete Files, Copy Files, etc. Most of the time, the files in question are local (C:\) files, sometimes they are on a network drive.

The second issue is that when a step fails, Visual Build does not shut down. Sometimes, it runs the failure code, sometimes not. This is not consistent. Many times, when a step fails, it terminates OK. However, other times, I come in the next day to find it at the failure step and just not doing anything.

Has anyone else experienced anything like this?

[kinook]

Originally posted by DougFarmer123
I installed version 7.0 late last fall as I needed the VS 2008 capability. At the same time, I loaded VS 2008. Ever since then I have been experiencing two problems.

We run multiple (10) builds every night.

The first issue is that a file system step hangs with a "file in use" or "access denied" message. I cannot rule out our own network, but it is interesting this did not happen before. File system steps are like Delete Files, Copy Files, etc. Most of the time, the files in question are local (C:\) files, sometimes they are on a network drive.

VBP itself (i.e., Copy Files, Delete Files actions) does not keep open handles to files or folders that it processes, and just reports errors returned by Win32 file system API calls. If there is any script code in the project that manipulates files or folders, care must be taken to close file handles. You can use Process Explorer to find what has a handle to a given file or folder.

The second issue is that when a step fails, Visual Build does not shut down. Sometimes, it runs the failure code, sometimes not. This is not consistent. Many times, when a step fails, it terminates OK. However, other times, I come in the next day to find it at the failure step and just not doing anything.

Is the VBP process actually hung (can you continue the build or exit VBP or is it non-responsive)? Some possibilities:

http://www.kinook.com/Forum/showthre...?threadid=3931

http://www.kinook.com/Forum/showthre...?threadid=3892

Otherwise, I would recommend updating to v7.1, and please provide steps for reproducing the problem(s) if they persist:
http://www.kinook.com/Forum/showthre...?threadid=3044

Thanks.

[DougFarmer123]

Thanks,

I'll look next time it hangs at the process explorer and see if I can tell what is happening. Also at some of the other posts you mention.

Doug