[jdavidi]

Greetings,

We have 2 build machines, "A" and "B", both of whom utilize/update (via network share) VisBuildPro.macros on "A" when running similar yet separate nightly builds.

A failure routine is set up to kill the build process and email the error; two or three times over the last month has thrown the following error:

Failed to create '\\BuildMachineA\VBP6_files\VisBuildPro.macros': The process cannot access the file because it is being used by another process.

My first thought to get around this was to have my failure step search %FAILSTEP_OUTPUT% for this error and then just issue the equivalent of a Rebuild (Shift + F7) from script but after searching through the forums this doesn't seem to be an option (at least in v6.2a).

Was wondering if anyone had any ideas with regard to how to best mimic a build script Rebuild or otherwise prevent the .macros file lock?

Thanks!

--jdavidi