3.36.4. I can’t start the AUT
Prev | 3.36. Troubleshooting | Next

### 3.36.4. I can’t start the AUT

If the start AUT button is disabled
If you cannot start a particular AUT, this could be because:

- You have not connected to the AUT Agent (Section 3.2.3, “Connecting to the AUT Agent”).

- You have not defined an AUT (Section 3.7, “Defining applications under test (AUTs)”).

- You have not configured an AUT (Section 3.8.1, “Configuring AUTs to be started from the ITE”).

Errors starting the AUT

If there is an error starting the AUT, this could be because:

The AUT cannot be found:

  Make sure that the JAR or executable file for the AUT is correct (Section 3.8.1, “Configuring AUTs to be started from the ITE”).

The main class has not been found:

  Make sure that the JAR file you have entered contains the main class (Section 3.8.1, “Configuring AUTs to be started from the ITE”).

The JAR given as a classpath is not valid:

  Check that you have entered the right JAR file, and that the path to it is correct from this computer. If you have entered a relative path, make sure that it is relative to the AUT working directory, if there is one, or to the AUT Agent directory if you have not specified a AUT working directory.

The JAR given as a classpath does not contain a distinct main class:

  Check that you have entered a JAR which contains a main class.

If the AUT does not appear in the Running AUTs View
If the AUT does not appear in the Running AUTs View and you are testing an RCP application, make sure that the RCP Remote Control plugin has been installed (Section 4.3, “Testing RCP AUTs”).

Otherwise, check that the toolkit you specified in the AUT configuration (Section 3.8.1, “Configuring AUTs to be started from the ITE”) is the right toolkit for this AUT.