Problem with PsExec after upgrading to FB5

FinalBuilder Bugs
1

Just upgraded all our FB4 projects to FB5. Every project upgraded without a hitch except for one that has an Execute Program action that executes PsExec.

I am using PsExec to excute a FinalBuilder project on a remote machine. I have been able to reproduce the problem by writing two very simple FB5 projects. One project I copied to the remote machine, the other project contains an Execute Program action that executes PsExec on the remote machine in order to run the project on the remote machine. I created a replica of the same two projects in FB4 as a control.

The FB4 project ran successfully, and executed its counterpart on the remote machine. The FB5 project does not run successfully. Running Task manager on the remote machine, I see the FinalBuilder5.Exe appear in the list of processes (along with the PsExec service) but FinalBuilder5.Exe does not return control - its as though the remote project has got stuck executing its actions.

Here's the command line that is being run in the Execute Program action:

\\SEVSQ07 -u my_user -p *** -n 20 "C:\Program Files\FinalBuilder 5\FinalBuilder5.exe" -n -r -e "D:\Temp\ExecuteByPsTools.fbp5"

Here are the versions that I'm running:

FB5.0.0.130 / FB4.2.0.296 on both machines

PsExec 1.55.0.0 on the local machine (its not installed on the remote machine - I assume it doesn't have to be?)

Windows 2003 on the remote machine

Windows XP SP2 on the local machine

Can you figure out what the problem is?

Thanks

Christian

2

Hi Christian,

Sorry to hear you’re having problems.

We have noted some problems with PsExec and FinalBuilder, but this has mostly been using programs which output a lot of text to the console. The FinalBuilder IDE does not output any, so it’s not likely this is the problem. Nevertheless, I have three suggestions which may help:

1) Run the Execute Program action with “Log output” disabled.

2) Add the “-i” option to psexec, and see if the FinalBuilder process appears on the host machine’s desktop.

3) Try using the built-in psexec action (instead of Execute Program) and see if things are any different.

Please let us know how you go.

Regards,


Angus