Message - Unable to run the tested application.

Make sure that the application’s executable file exists on the disk and that its path is spelled correctly. If the application resides in a network share, make sure that this location is available.

If the test project is shared among multiple computers, specify the application path using variables or similar methods, so that the path is computer-independent. For more information, see Avoiding Computer-Specific Settings.

The problem can occur if –

• User Account Control (UAC) is enabled,

• and the tested application requires administrator privileges,

• and TestComplete is running without administrator privileges.

To resolve the problem, you must run TestComplete with administrator privileges as explained in Using TestComplete With Administrator Privileges. In this case, TestComplete will launch your tested application with administrator privileges as well.

(Simple, RunAs and Debug modes only.) TestedApps require an executable file to run -- .exe, .com, .bat or .cmd. This is different from the Windows command prompt, where you can type an arbitrary file name (text file, audio file, Control Panel applet, and so on) and Windows will open that file in its associated application.

To open an arbitrary file by using TestedApps, add its associated application as a TestedApp and specify the file name as a command-line argument. For example, to open a text file in Notepad:

To run Java, AIR and ClickOnce applications, use the corresponding type of tested applications.

To open web pages, use the Run Browser keyword test operation or the Browsers.Item(...).Run(url) scripting method.

Make sure that the specified command-line arguments are valid, listed in the correct order and are not duplicated. Try running your tested application with these arguments from the Windows command prompt and see if it works.

For information about the command-line syntax of your tested application, please refer to its documentation.

(Simple, RunAs and Debug modes only.) Make sure the Working folder exists, is spelled correctly, and you can access it from Windows Explorer.

The user account (either the one that TestComplete is running under or the one specified in the RunAs mode parameters) does not have enough permissions to launch the specified application. For example, this account may not have access to the application’s folder. To resolve the problem, ask your system administrator to grant that user account the necessary permissions.

Check Windows Event Viewer or the application log for any errors and contact the application developers to troubleshoot the problem.

Note that you can trace application exceptions and capture process dumps with TestComplete. For more information, see Tracing Exceptions, Crashes and Freezes in Tested Applications.

Make sure you have specified all three values -- Login, Password and Domain. Letter case may be important.

This account must have a non-empty password. The RunAs mode does not support accounts with empty passwords.

If this is a local (non-domain) account, specify the computer name as the domain name.

The Secondary Logon service is required to run applications under another user account. Make sure this service is enabled and running:

• Open the Control Panel | Administrative Tools | Services applet.

• Locate the Secondary Logon service in the list.

• Right-click the service and select Properties from the context menu.

• In the Properties dialog, set Startup type to Automatic and click OK.

• Right-click the service and select Start or Restart from the context menu.

Make sure that the manifest or shortcut exists and that its path is spelled correctly. If the manifest resides in a network share, make sure that this location is available.

If you launch the application via an .appref-ms shortcut, make sure that its path is valid for the current computer. The Start menu and desktop shortcut paths include components specific to the user and the Windows version, so if you copied the test project from another computer the shortcut path may become invalid. To avoid the problem, copy the shortcut to a common folder location, or launch the application using a deployment manifest instead. See Avoiding Computer-Specific Settings.

Increase the Wait timeout value specified for the application in the TestedApps editor.

The specified ClickOnce application is launched from an URL, but the computer has no Internet connection. To resolve the problem, make sure that the computer has a working Internet connection. Check whether the network cable is connected to the computer and whether you can open web sites (for example, https://smartbear.com).