Scheduled run fails

I have a strange problem in FinalBuilder that I don’t understand.
There is a batfile that is executed 6:00 every morning.

taskkill /IM "FinalBuilder8.exe" /F
taskkill /IM "bds.exe" /F
taskkill /IM "InitializeSystem.exe" /F
taskkill /IM "TestAttracs.exe" /F
del *.fb8lck
"C:\Program Files (x86)\FinalBuilder 8\FBCMD.EXE" -cf "F:\Attracs\AttracsBuildXE.fbp8"

Sometimes Delphi, FinalBuilder GUI etc is left from previous day. So those processes was killed before start. Lock-files deleted etc. And it worked fine. But now something changed.

So endtime is 0. Runtime seems to have some kind of overflow.

The history now show full path instead of just name of log-file.

What can I do to solve this ?

If you kill FinalBuilder while it has a project open, you risk corrupting the log file (it’s a database). Not sure why the log file entries show the full path, will need to look into that. The runtime overflow will be from FinalBuilder being killed and the end time not being written to the log file.

I have to question why you are killing FinalBuilder? Are actions that you run hanging? If so then you should use the timeout feature on the actions Runtime tab, Timing Options (available on most actions that execute processes).

Is FinalBuilder running as an automated task each day? If that is the case then you should be running FBCMD.exe rather than the IDE. The Tash Scheduler wizard in FinalBuilder has options to have it close other instances of FinalBuilder when running a scheduled task - this should close the other instances cleanly.

The issue is that we both use Finalbuilder IDE and FBCMD.EXE.
So what can happen is that someone login to buildmachine and do a manual build in IDE.
Then forgot to close IDE.
Next morning a scheduled build with FBCMD.EXE. That will fail if the script is opened in IDE.

But now found IDE Command Line Interface - FinalBuilder 8 - VSoft Technologies Documentation Wiki
So it seems to be possible to close IDE a nice way :slight_smile:

I forgot that I usually login as another user than the one that do automatic builds.
It was a permission problem to github…