## Installation Troubleshooting

This section provides information to help troubleshoot common issues you might encounter while installing Turbo Server.

Common Issues

The following table lists common issues/questions and their solutions:

Performance Counters

Turbo Server uses performance counters to track and report server load information. These reports may be viewed on the Turbo Server administration site Domain page.

If the load information for a server is missing, then the Turbo service user may not have permission to access performance counter data. To grant permission to the Service user:

1. Log on to the application server.
2. Open Server Manager and click on Tools > Computer Management.
3. From the Computer Management window, click on Local Users and Groups > Users.
4. Right-click on the service user and click Properties.
5. Click on the Member Of tab and check that the Performance Monitor Users group is listed.
6. If the group is not listed, click Add and enter Performance Monitor Users, then click OK.

This group is automatically added to the service user during Turbo Server installation.

Enable Diagnostic Mode

Enabling diagnostic mode generates debug output logs. These can be used to help the Turbo support staff diagnose and debug issues.

Turbo Client

Diagnostic logs are written to the c:\users[user]\appdata\local\turbo\logs directory.

Turbo Server

When troubleshooting an issue related to the general administration of Turbo Server, enable diagnostic mode for Turbo Server. Complete the following steps to enable diagnostic mode for Turbo Server:

1. Open a Windows Command Prompt as an administrator (cmd.exe).

2. Enter the following command: net stop turbo

3. Navigate to C:\ProgramData\Turbo Server and open settings.xml with Notepad or another text editor.

4. 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:

     <?xml version="1.0" encoding="utf-8"?>
     <settings>
   	  <InstallPath>[Path]</InstallPath>
   	  <InstalledVersion>[Version]</InstalledVersion>
   	  <DbLibraryConnection>embedded</DbLibraryConnection>
   	  <DbManagerConnection>embedded</DbManagerConnection>
   	  <TraceLevel>Debug</TraceLevel>
     </settings>
   

5. 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 Server Installation Logs

• [Install Directory]\logs\Setup.log

Turbo Server Service Logs

• [Install Directory]\logs\*.log

Turbo 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 Server SQL Server Logs (Embedded SQL Server Express)

• [Install Directory]\Sandbox\MODIFIED\@PROGRAMFILESX86@\Microsoft SQL Server\MSSQL.1\MSSQL\LOG

Turbo Server Apache Logs

• [Install Directory]\Sandbox\MODIFIED\@PROGRAMFILESX86@\Apache Software Foundation\Apache2.2\logs\error.log

Turbo 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:\path to 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:

1. 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

2. 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 Server there may be information reported in the Window Event Viewer to help diagnose the problem.

Setup Failed!

Error details: A network related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify the instance name is correct and that SQL Server is configured to allow remote connections.

The error may occur during setup due to the database being unavailable. Please ensure the SQL server can be connected from the server with the specified installation credentials. If installing in standalone server mode, the embedded database may not be available yet. Check to see if the Turbo Server Service was installed correctly and is in the process of booting up. If so, then wait a few minutes and attempt to access the administration website (typically available at http://localhost/admin).