Parent topic: Configuring MySQL and Aspera Services
High Availability Installation / Configuring MySQL and Aspera Services

Configuring the Aspera Services

Edit Entries in the Services Panel

  1. Open the Services panel.
  2. Stop the Aspera Orchestrator service.


  3. For the MySQL Server (Aspera) service, change the Startup Type to Manual.

Edit Entries in the Registry Editor

Orchestrator requires a MySQL database to function. On a single-node system, that database resides on the same system as Orchestrator, and the Orchestrator service is configured to depend on the MySQL service. With this configuration, when a clustered environment is set up, the other node (which is not running MySQL) is unable to launch the Orchestrator service. Because of this issue, the administrator needs to remove the dependency on the MySQL service with the Registry Editor.

  1. Open the Registry Editor.
  2. Delete the DependOnService key from the Aspera Orchestrator service entry for the following three locations:
    • HKLM\System\CurrentControlSet\Services\Aspera Orchestrator
    • HKLM\System\ControlSet001\Services\Aspera Orchestrator
    • HKLM\System\ControlSet002\Services\Aspera Orchestrator


  3. Reboot the system after the changes are made.
Parent topic: Configuring MySQL and Aspera Services