SOTI Connect Component Issues

Review the following scenarios to resolve common component-related issues.

SOTI Connect Becomes Slow or Unresponsive on Windows Virtual Machines (VM)

The machine gradually becomes slow or unresponsive when running SOTI Connect on a Windows VM.

Resolution

  1. Reboot the Windows VM weekly.
  2. Keep the Windows VM updated.
Note: Windows operating systems may not automatically release all resources, leading to gradual performance degradation on virtual machines. To restore optimal performance, reboot the VM periodically to reset resource allocation.

Automatic Remote Protocol Adapter (PA) Update Failures

In SOTI Connect versions 2025.0 and 2025.0.1, automatic PA updates may fail in environments with limited network speed (for example, excessive PAs or restricted load balancer throughput).

Workaround

  • Manually trigger the remote PA update from Administration > System Architecture.
  • Alternatively, manually update the PA version by running the installer on the target machine.

Protocol Adapter Stuck in "Started" State

After installing SOTI Connect components in a Management Server (MS) cluster, the Protocol Adapter (PA) is stuck in the Started state on the SOTI Connect web console.

Resolution

Manually restart the VM to transition the PA to the Running state.

Management Service (MS) unable to connect with File Store (FS) Service after Restore

The Management Service (MS) may fail to connect to the File Store (FS) following a restore operation.

Resolution

Manually reboot the Management Service (MS). See Restarting the Management Server for more details.

To prevent this issue in the future, restore components in the following order:

  1. Database
  2. File Store
  3. Management Service