Catastrophic failure when running VBScript in ASync Action Group

FinalBuilder Bugs
1

Hi all,

I am trying to take advantage of overlapping checkout time with compile time and using ASync Action Groups to do so.

Now I tried to add the following VBScript BeforeAction script:

Echo("*** BeforeAction Script Started ***")
SetCurrentDir(ExtractFilePath(ProjectFile))
FullPath = ExpandRelativePath(OutputPath, ExeName)
Echo("Output file: " + FullPath + ExeName)
Echo("*** BeforeAction Script Ended ***")

It runs as expected (gives me the fully defined output file for a VB6 compile action) when I run current action, but If I run from within an ASync Action Group it gives me the error:

Error Executing script : BeforeAction
Catastrophic failure
Line : 0
Char : 0
------------------------------------------------------
Error in BeforeScript : VBScript
This Action did not execute.
------------------------------------------------------

 Any ideas of why this would fail?  It fails even if it is the only action defined in the group.  I am using FB v.4.2.0.317

Thanks,

Rob

2

Hi Rob,

Thanks for your post. Unfortunately, I can’t yet reproduce this in 4.2.0.317 (I pasted your script into a BeforeAction event of a Run Script action, then put it into an Async group.) Do you have any special values in any of the variables? Is there anything else unusual which may be contributing to the problem?

Regards,

Angus

3

Hi Angus,

I have a project variable assigned into the action to determine the project file location.  I wonder if this makes a difference?

Note, I tried moving the beforeAction to an AfterAction thinking that it might resolve the variable, but no difference.

I tried removing the variable and replacing with a fully defined path - no difference.

I have the project file in a subst'ed drive.  I tried giving the full path from the source drive, and still no difference.

I wonder if it is related to being a VB6 action?

Running out of ideas quickly now... 

Thanks,

Rob

4

Hi Rob,

Could you please zip up the project file (and the logs, if possible) and email it to us at support at finalbuilder dot com? That should help us track the problem down.

Regards,

Angus