This section provides information to help troubleshoot common issues you might encounter while using Turbo Server.
The following table lists common issues/questions and their solutions:
|There is an error during installation: Turbo Hub Server installation failed, please contact the administrator.||This may occur if there is a timeout when starting or accessing the database services. Go to Control Panel > Administrative Tools > Services and try restarting the Turbo Hub Server service.|
|The Turbo Hub Server service fails to start.||This may occur if there is a timeout when starting or accessing the database services. Go to Control Panel > Administrative Tools > Services and try restarting the Turbo Hub Server service.|
I am unable to access the Administration Site or Hub Site from another machine.
Microsoft Windows security settings might be restricting external connections to the ports assigned to the Administration and/or Hub sites. For information about configuring Turbo Hub Server security settings, refer to Configuring Turbo Hub Server Security.
My application does not appear on the Turbo Streaming Server portal.
Verify that the application has been pushed to the correct org account dashboard (for turbo.net hub) or namespace (for Turbo Hub Server). For more information about publishing application versions, refer to Managing Applications.
Where do I install a new license?
New licenses can be applied by clicking the New License link found on the Admin page in the Administration Site.
|Turbo Hub Server is no longer accessible after making a Network Configuration change||Turbo Hub Server service may need to be restarted after making a network configuration change. Go to Control Panel > Administrative Tools > Services and try restarting the Turbo Hub Server service.|
HTML5 cloud launch fails to start the application and results in the generic error page.
Review the SSL troubleshooting documentation. If it is not a certificate issue, the application server may not be accessible from the broker. Check that port 8084 can be accessed from the broker to the application server.
Help! I forgot the administrator account password and can't access the Administration Site.
Remove the admin group by using the server cli. Open a command prompt as administrator and navigate to the installation folder. Run `Server.exe admin user-group 2 clear` which clears all users from the server administrator's group. This allows you to access the the Administration Site without login. Reset the admin user's password and add the user back to the administrator's group to secure the Administration Site.
Enable Diagnostic Mode
Enabling diagnostic mode generates debug output logs. These can be used to help the Turbo support staff diagnose and debug issues.
Diagnostic logs are written to the c:\users[user]\appdata\local\turbo\logs directory.
When troubleshooting an issue related to the general administration of Turbo Hub Server, enable diagnostic mode for Turbo Hub Server. Complete the following steps to enable diagnostic mode for Turbo Hub Server:
Open a Windows Command Prompt as an administrator (cmd.exe).
Enter the following command: net stop turbo
Navigate to C:\ProgramData\Turbo Server and open settings.xml with Notepad or another text editor.
Add a new element called TraceLevel with value Debug as a child element to Settings; after adding this element the file should resemble the following:
[Path] [Version] embedded embedded Debug
Enter the following command: net start turbo
Locating Log Files
There are several types of logs available for Turbo Server, including logs for the installation process, Apache, and SQL Server. The log file locations are dependent on the install location of Turbo Server. The default location is "C:\Program Files\Turbo Server".
Turbo Hub Server Installation Logs
- [Install Directory]\logs\Setup.log
Turbo Hub Server Service Logs
- [Install Directory]\logs\*.log
Turbo Hub Server Web Services Logs
- [Install Directory]\Sandbox\MODIFIED\@PROGRAMFILESX86@\Turbo Server\Web\logs\*.log
- [Install Directory]\Sandbox\MODIFIED\@PROGRAMFILESX86@\Turbo Server\Web\Hub\logs\*.log
Turbo Hub Server SQL Server Logs (Embedded SQL Server Express)
- [Install Directory]\Sandbox\MODIFIED\@PROGRAMFILESX86@\Microsoft SQL Server\MSSQL.1\MSSQL\LOG
Turbo Hub Server Apache Logs
- [Install Directory]\Sandbox\MODIFIED\@PROGRAMFILESX86@\Apache Software Foundation\Apache2.2\logs\error.log
Turbo Streaming Server Logs
- Portal and Broker servers write all log traces to the console. These are archived in their container logs xcstream_*.txt files. Use
turbo logs [container] --export=c:\pathto retrieve the logs.
- Application Server provisioning logs are stored in C:\Program Files (x86)\Turbo\ApplicationServer\logs.
Starting and Stopping the Turbo Server Service
Oftentimes, troubleshooting and fixing problems in Turbo Server requires the Turbo Server service be restarted.
There are currently two ways of doing this, through either the Control Panel or the Command Prompt. Each method is listed, below:
Through the Control Panel
a. Navigate to Control Panel > Administrative Tools > Services or Control Panel > System and Security > Administrative Tools > Services
b. Restart the Turbo Server service
Via the Command Prompt using the net command
a. Run a new command prompt (cmd.exe) as Administrator
b. Type the command net stop turbo to stop the Turbo Server service
The expected output for this command is:
The Turbo Server service is stopping. The Turbo Server service was stopped successfully.
c. Type the command net start turbo to start the Turbo Server service
The expected output for this command is:
The Turbo Server service is starting. The Turbo Server service was started successfully.
Windows Event Viewer
The Windows Event Viewer is another useful source of information. If there is an issue starting the Windows service for Turbo Hub Server there may be information reported in the Window Event Viewer to help diagnose the problem.
Application Launch Issues
The remote application failed to launch
There is a 20 second interval when the Turbo Server service is starting where the communication between the Broker and Application Server is out of sync. The application launch should succeed once the interval has elapsed.
Application Server performance is poor
Ensure that background processes such as Windows updates is disabled when the Application Server is expected to be in use. Log in as administrator and open Task Manager. If the TiWorker.exe is running with high CPU usage then it indicates that a Windows update is in progress.