1. Verify “Log on as a service” Permission

   • Sign in to Windows Server using an Administrator account

   • Open: Administrative Tools → Local Security Policy

   • Go to: Local Policies → User Rights Assignment

   • In the list on the right, open: Log on as a service

   • Click: Add User or Group

   • Select the user you are using for the installation and click OK

   • Save changes by clicking OK again

   • Right-click the Scout installer and choose Run as administrator

2. Confirm ODBC Driver Version

   • Ensure Microsoft ODBC Driver for SQL Server 18 or newer is installed

   • Check in: ODBC Data Sources (64-bit) → Drivers tab

   • If the version is lower than 18, update it first

3. Check SQL Server Database Permissions
   The installation user must have permission to:

   • Create tables

   • Insert/write data

   • Select/read data
     We recommend adding the user to the db_owner role for the Scout database during installation
     If a previous installation failed and left an incomplete database:

   • Delete that database completely

   • Create a new, empty database

   • Run the installer again

4. Verify Network Requirements

   • Scout Server and SQL Server must be able to communicate both ways

   • Make sure the firewall or security tools are not blocking the connection

   • Follow the official reference for Scout Server Network Requirements

5. Collect Installation Log Files (only if it still fails)

   • Open the folder: %USERPROFILE%\AppData\Local\Temp

   • Sort files by Date modified

   • Find the newest files that start with:
     • Scout* (ScoutInstaller logs)
     • eLux* (AllPackagesInstaller logs)

   • Files from the same installation attempt will have almost the same time

   • Send them to support

6. Follow Additional Recommendations

   • Install all Windows updates so the server is fully patched

   • Check that antivirus or endpoint protection is not blocking Scout or SQL communication

   • Confirm the firewall allows required ports

   • Run the installer from drive C: or another local drive (not a network folder)

   • If the installation still fails, send the latest logs and include:

     • Windows version

     • SQL Server version

     • ODBC driver version

Scout Server installation issues happen when Windows permissions, drivers, database rights, or network access are not set correctly. Following the steps below will solve most installation failures.
ter issues while installing Scout Server, follow the numbered steps carefully to verify configuration, permissions, and prerequisites.

Log files always start with: Scout* or eLux*

Logs from the same installation attempt have almost identical timestamps