An application won't start

Microsoft Windows applications

Using Object Manager, check the following:

Is the correct Windows protocol set for the application server?
Make sure that the Application Command attribute contains the full pathname of the application's executable, including the correct filename extension.
Make sure that the pathname does not point to a Windows shortcut.
Make sure that the application is correctly installed and configured on all application servers that may run it. The application servers are defined in the application object's Hosts tab. The application must be installed in the same location on every application server.
Make sure that the connection method is appropriate to the application servers.
Make sure that the Windows NT Domain attribute is set correctly.
If no users can start applications (and no users can log in), try tarantella restart --warm.

Using Object Manager, check the following:

Make sure that the Application Command attribute contains the full pathname of the application's executable.
Make sure that the application is correctly installed and configured on all application servers that may run it. The application servers are defined in the application object's Hosts tab. The application must be installed in the same location on every application server.
Make sure that the connection method is appropriate to the application servers.
Make sure that all required Environment Variables are set correctly.
Make sure that the Login Script is set correctly.
If no users can start applications (and no users can log in), try tarantella restart --warm.

It may be worth increasing the launch timeouts on the application server.

Related topics
Creating and publishing an application object to users Introducing Object Manager