View Single Post
  #28  
Old 09-30-2008, 04:48 PM
score score is online now
Registered User
 
Join Date: 02-15-2008
Location: austin,tx
Posts: 14
Ok, I upgraded to v6.7a and it has hung twice in two runs. So know I will do the other steps. I got to step 2 which is adding the
Application.Options.RunProgramOutputWaitTimeout = 1000
Application.Options.RunProgramInputWaitTimeout = 1000

Is this setting how long to wait for a process to end? is it in minutes or seconds? Some of the processes take over an hour to run. Could that be it?

It does seem to always hang after a long running step.

thanks



Quote:
Originally posted by kinook
We have not been able to reproduce the problem (and not for a lack of trying), but as far as we know, one or more of the following resolved the problem for others who have reported it:

1) Updating to v6.7a

2) Adding a Run Script (VBScript) step like this at the beginning of with this code:

Application.Options.RunProgramOutputWaitTimeout = 1000
Application.Options.RunProgramInputWaitTimeout = 1000

3) Removing the VBP DEP exclusions (Control Panel -> System -> Advanced -> Data Execution Prevention -> Turn on DEP for all programs and services except those I select, Remove Visual Build Professional and Visual Build Professional 6 Console App from the list, OK, and restart Windows) and then configuring Windows to 'Turn on DEP for essential Windows programs and services only' (in that same dialog) and restart again.

4) Adding a Wait step (5 seconds) at the end of a chained (child) build.

If none of those help, please provide the following information:

Are you building from a Scheduled Task, starting manually, or? Any ideas on anything that may have changed when the problem returned? Please ZIP and send:
1) The info from Help | About | Install Info (after updating to v6.7a)
2) A screen shot of System properties (Windows+Break)
3) A reproducible test case, including VBP project(s) that demonstrate the problem.

Thanks.
Reply With Quote