Some actions run an executable program in order to to perform their function.
Some examples of these actions are:
| • | NDoc |
When an action runs an external executable, it allows you to set two extra properties for FinalBuilder Standard and four if using FinalBuilder Professional:
| • | Run Action As User |
| • | Enable Timeout |
| • | Processor Affinity (FinalBuilder Professional only) |
| • | Process Priority (FinalBuilder Professional only) |

Enable Timeout
If the action runs for longer than the set number of minutes, it will be aborted and will fail.
Processor affinity
FinalBuilder Professional allows you to set the processor affinity of any executable process. Processor affinity allows you to specify which CPUs a process may run on. You will need a multiple CPU computer in order for this to be of any use. See the Setting Processor affinity & Process priority help topic for more details.
Process priority
FinalBuilder Professional allows you to set the process priority class of any executable process. Setting process priority allows you to specify a program to be scheduled more or less frequently than other programs on the system. See the Setting Processor affinity & Process priority help topic for more details.
Run Action As User
By setting the Username and Password, FinalBuilder will attempt to run this particular action under a different user account. There are many security requirements that need to be met before Windows will allow this, the minimum requirements are detailed below. You may need to ask your System Administrator if you still cannot get past the security errors.
The following security privileges must be granted for a process to be run under a different users login:
Windows 2000:
| • | Act as part of the operating system |
| • | Create a token object |
| • | Replace a process-level token |
| • | Increase quotas |
Windows XP and Server 2003
| • | Act as part of the operating system |
| • | Create a token object |
| • | Replace a process-level token |
| • | Adjust memory quotas for a process |
Note that changing security privileges may compromise system security policies. Please ensure that your system is secure before and after modifying these settings.
One way of testing that the security requirements are met and that your username and password are correct is to use the Execute Program action to run the WhoAmI.exe program which is usually located in C:\Windows\System32\WhoAmI.exe
When this is run under a different user, the log will contain the username that the action successfully ran under.
Troubleshooting:
Invalid username or password
If the current user is not a domain account, and the impersonation account is set to a domain account then authentication fails.
The application failed to initialize properly (0xc0000142). Click on OK to terminate the application.
This message box appears if the user who you are impersonating has incorrect privileges. Try making the user part of the administration group to solve this problem.


