Application Troubleshooting
If your application fails to start when launched from the Turbo Server workspace, identify what causes the failure.
Test Known Application
Confirm that there isn't a problem with Turbo Server by launching an application that is known to work.
A good example is npp/notepadplusplus from Turbo.net Hub, which can be added to Turbo Server from Admin > Hub > Add Repository > Import Repository.
If this application fails similarly, then the problem is likely with Turbo Server rather than the application configuration. In this case, see the Application Server Troubleshooting section.
If the issue is isolated to your application, see the Application Troubleshooting section.
Launch Modes
Check the application behavior in each launch mode by right-clicking on the application in the workspace and selecting Run in Cloud (HTML5), Run in Cloud (Windowed), and Run on My PC.
If the application works in HTML5 but not Windowed mode (or vise versa), it is likely a bug in the Turbo Server or Client. Please report the issue to us.
If the application works with Run in Cloud but not Run on my PC, it is probably an application issue. See the Application Troubleshooting section.
If the application works with Run on my PC but not Run in Cloud, test an application that is known to work to determine if the issue is with the server or application configuration.
Command-Line Launch
Run the application from the command-line by opening a command prompt and executing the following to launch the application in a new temporary container: turbo try application-image. Perform this test on the system where the application fails to start (for example, the application server).
If the application fails, then the issue is probably related to the configuration. See the Application Troubleshooting section.
If the application works, then the issue may be caused by a corrupted sandbox or the workspace application settings, such as container isolation or components.
Sandbox Problem
Check if the application launches successfully when using a clean sandbox. The easiest way to perform this test is to create a temporary internal user by going to Admin > Users > Add User and using it to launch the application.
If the application launches successfully, clear the persisted session from the Hub for the affected user by going to Admin > Users > Username > Sessions.
In addition, clear the local session sandbox on systems where the issue occurs by opening a command prompt and executing turbo containers & turbo rm containername or deleting the session folder from C:\Users*username*\AppData\Local\Turbo\Containers\Sandboxes.
Component Conflict
Remove all components that are not required to start the application from the Workspace Application settings > Components to check if the issue is caused by a conflict with one of its component.
If the application launches successfuly, see the Application Troubleshooting section to troubleshoot the component issue.
Container Isolation
The default container isolation mode is set to Full isolation, which would hide most applications installed on the system and may cause launch failures in some cases. Decrease the container isolation mode to Write-Copy or Merge to check if this is the cause for the failure.
If the application launches successfully after changing the isolation, review the application configuration for missing dependencies.
Generate VM Diagnostic Logs
For some applications issues, it may be necessary to generate and analyze VM diagnostic logs. To generate the logs, append &diagnostic= to the launch page URL.
Original: https://turboserver/run/3c3120d5-0151-41fa-9f35-bb2a8082c291?loc=2&title=Notepad%2B%2B
Diagnostic Logging Enabled: https://turboserver/run/3c3120d5-0151-41fa-9f35-bb2a8082c291?loc=2&title=Notepad%2B%2B&diagnostic=
The VM logs will be written to the container sandbox folder on the local system (when using Run on my PC) or application server (when using Run in Cloud). By default, this would be in %LOCALAPPDATA%\Turbo\Containers\sandboxes*sandbox-guid*\logs.
For more information on analyzing VM logs, see the Application Troubleshooting section.
Application Updates
If you have recently published an application update, ensure that the new application image is being used by opening a command prompt and running turbo images on the system where the application is executed. Confirm that the application image ID matches your updated image.
The Turbo Client checks for application updates once every 24 hours. If you have pushed an update recently, perform a manual pull to update the client repository immediately instead of having to wait for the automatic update check by running the following in a command prompt: turbo pull application-image.
Licensing
Some applications and licensing mechanisms require the application to be executed under an Active Directory Windows user.
If the application has this requirement, set the Workspace Application settings > General > Profile Mode to Ask for Credentials, then launch the application and enter your user credentials when prompted to execute it under your user.
Security Software
If a particular application runs on one environment and not another, it could also be related to the security software installed on the particular system. Please refer to the Antivirus and Security Software documentation.
Internet Explorer Does Not Launch Inside Virtual Application
If Internet Explorer is required by your application, ensure the application isolation is set to write-copy or merge. Full isolation may not be compatible with applications that require external software built into Windows such as Internet Explorer.