|
#1
|
|||
|
|||
From that information, I would guess that the licensing / software protection component utilized by Visual Build (purchased from a now-defunct third party) is preventing the normal ending of the build process. How long has the build been running when this occurs? We've tried to reproduce this behavior with long-running builds launched from a scheduled task but have not succeeded.
One thing you could try is adding a Kill Process action at the end of the project to terminate the build process when it's done ([Builder.ProcessID]). |
#2
|
|||
|
|||
The build has lately been taking 5 hours on average (give or take a few minutes).
Considering your answer, do you think I somehow messed up the VBP installation? Also, I may (probably?) have logged into the VM as a different admin user account when I installed VBP than the account the build runs under. Could that be part of the issue? I had seen in the forums other advice to kill the VBP process but I was holding off in trying that approach until exhausting all other avenues (since it seems like an ugly hack). Thanks for the help. |
#3
|
|||
|
|||
I wouldn't expect that to matter, but you could try uninstalling Visual Build, then reinstalling and registering with the user account that will be used for building.
|
#4
|
|||
|
|||
I previously tried setting the scheduled task to execute under my own logon account and the results were the same.
Is it possible the VBP licensing component is active because I neglected to register VBP? It's been so long since I installed VBP I don't recall (setting up this new VM has been an ongoing project for a long time, mostly relegated to the back burner). |
#5
|
|||
|
|||
I doubt that's the problem -- it probably wouldn't even build the project when unregistered, and would instead report a limit on the size of a project in eval mode.
|
#6
|
|||
|
|||
This is strange. Last Friday I added a new final step to my build project, a "Kill Process" step with [Builder.ProcessID] as the value. Tested the step in the VBP designer - VBP terminated. Let the build run over the weekend and again this morning for good measure, just to be sure what I was seeing. Despite the attempt to kill the process, VisBuildCmd.exe always remains running in Task Manager (and Task Scheduler says the latest task is still running). Monday morning there was three instances of VisBuildCmd.exe running (Saturday, Sunday and Monday builds). I rebooted the VM Monday and now (Tuesday) one VisBuildCmd.exe is running under this morning's scheduled task.
I am officially out of ideas. What could be going on? |
#7
|
|||
|
|||
What does the build log show? Did the Kill Process step execute? You might instead try configuring the scheduled task to stop the task if it runs longer than, say, 8 hours.
|
|
|