SOTI Connect Installation/ Upgrade Issues

This section provides troubleshooting instructions for issues that may occur during the installation or upgrade of SOTI Connect.

Services Fail to Start During Installation

The system encounters a "Cannot start service" error during SOTI Connect installation, and the SOTI Connect service does not start.
SOTI Connect service not started
Resolution
  1. Stop any running antivirus programs.
  2. Re-run the SOTI Connect installer.

Installation Fails During Database Data Deletion Step

During the SQL connection step, selecting the database data deletion checkbox does not delete data and causes a rollback error. The installer logs show entries similar to:
2023-07-25 17:48:59,992 [ERROR] [ 8] Installer - Database migration failed and the installation/update cannot be continued.
Please contact support for further assistance.
2023-07-25 17:48:59,992 [ERROR] Installer - Installation failed System.Exception: Database migration failed and the installation/update cannot be continued.
Please contact support for further assistance.

Resolution

Manually delete the SQL data and log files.
  1. Navigate to the Server Properties panel of the VM hosting the SQL, then select Database Settings.
  2. Record the location of the Data and Logs.
    The Database Settings tab shows the location of data and log files
  3. Navigate to the Data and Log directories and delete all files inside.
    Note: Delete only the files, not the directories themselves.

Database Migration Failure: 2024.0 to 2024.1.0.7405

Upgrading from SOTI Connect 2024.0 to 2024.1.0.7405 may fail during database migration and trigger a rollback.
SOTI Connect migration error
  • Affected versions: SOTI Connect 2024.0 and later

Resolution

Before updating, run the following SQL script to prepare the SOTI Connect database:
use SotiConnectManagementServer

IF OBJECT_ID('tempdb..#removeJsonMetadata') IS NOT NULL
	DROP PROCEDURE #removeJsonMetadata
GO

CREATE PROCEDURE #removeJsonMetadata
@JsonText nvarchar(max),
@Result nvarchar(max) OUTPUT
as 
	declare @idBegin int = 0;
	declare @idEnd int = 0;
	select @idBegin = CHARINDEX('"$id":"', @JsonText, @idBegin)
	WHILE @idBegin > 0
	BEGIN
		select @idEnd = @idBegin +  LEN('"$id":"')
		select @idEnd = CHARINDEX('"', @JsonText, @idEnd)
		select @idEnd = case when SUBSTRING(@JsonText, @idEnd + 1, 1) = ',' then @idEnd + 2 else @idEnd + 1 end
		select @JsonText = REPLACE(@JsonText, SUBSTRING(@JsonText, @idBegin, @idEnd - @idBegin), '');
		select @idBegin = CHARINDEX('"$id":"', @JsonText, @idBegin)
	END
	select @Result = @JsonText
RETURN
GO


declare @JsonText nvarchar(max)

DECLARE employee_cursor CURSOR FOR
  SELECT RuleJson
  FROM   [SotiConnectManagementServer].[dbo].[Rules]

OPEN employee_cursor;
FETCH NEXT FROM employee_cursor INTO @JsonText
WHILE @@FETCH_STATUS = 0
  BEGIN  
	  exec #removeJsonMetadata @JsonText, @JsonText output
      UPDATE [SotiConnectManagementServer].[dbo].[Rules]
      SET    RuleJson = @JsonText
      WHERE  CURRENT OF employee_cursor;

      FETCH NEXT FROM employee_cursor INTO @JsonText
  END;
CLOSE employee_cursor;
DEALLOCATE employee_cursor; 

DTD Repair Failure During SOTI Connect Upgrade

Device Type Definition (DTD) Repair is utilized when SOTI Connect changes the semantic ID of a property for a device. During any update, the installer automatically runs DTD Repair with a timeout of 5 minutes. If the repair process is not completed within this time-frame, an explicit warning message displays in the installer UI indicating that DTD Repair has failed.

Resolution

Run the Repair DTD option from the SOTI Connect installer manually, as it does not time out.
  1. Run the SOTI Connect installer as an administrator.
  2. Press CTRL + Double-click on the installer window to reveal the Repair DTD option.
    Repair DTD option
  3. Choose Repair DTD and follow the installer instructions.
Important: Users must run Repair DTD using the installer corresponding to their current version of SOTI Connect (the installer which received the error) before updating to a new version. Otherwise, Repair DTD does not execute during the upgrade process.

Unavailable Actions After Upgrading to SOTI Connect 2025.0

Before SOTI Connect version 2025.0, any changes to the supported actions on some devices resulted in those specific actions becoming obsolete, causing the rules/configurations utilizing these actions to stop working. Starting with version 2025.0, SOTI Connect introduces the action state "Unavailable." Whenever SOTI Connect no longer supports a specific action on a particular device type, the action will be marked as "Unavailable". This can occur in scenarios such as:
  • The OEM has discontinued support for action X.
  • A specific OEM model does not support action X, which is otherwise supported by all other OEM models. To support common properties/actions, SOTI Connect marks the action as "Unavailable".

Prevention

There are no workarounds for this specific issue since the action becomes genuinely unavailable on the OEM side. However, to prevent such situation:
  1. Delete the "Unavailable" action from the rule or configuration.
  2. Reconfigure the rule to exclude unavailable actions.
Note: In rare cases, previously unavailable actions may be restored—search the action list again to confirm.

Cannot Run SOTI Connect Installer: App Activation Error

Users are unable to run the SOTI Connect installer. When running the installer with the built-in administrator account, users may encounter the following error in the Event Viewer:
Activation of app failed with error:
This app can't be activated by the Built-in Administrator. See the Microsoft-Windows-TWinUI/Operational log for additional information.
This error occurs because the built-in administrator account is restricted from activating certain apps. This restriction is in place to enhance security and prevent unauthorized changes to the system.

Issue Resolution

  • Make sure your screen resolution is at least 1024x768.
  • Ensure User Account Control (UAC) is enabled. See Windows forum for more information.

Failover Management Service (MS) Does Not Start After Deploying a Root Certificate

After deploying a new root certificate, the failover MS does not start.
Management Server Not Running

Cause

The failover instance is unable to use the updated root certificate.

Resolution
Note: You must have the root certificate handy.
Manually update the root certificate of the failover instance using the SOTI Connect installer.
  1. Launch the SOTI Connect installer as an administrator.
  2. Navigate to the SOTI Connect Root Certificate view.
  3. Select Import Root Certificate From File.
    Generating a new certificate
  4. Select Browse, locate the root certificate file, and enter the Certificate Password.
  5. Select Next, then follow the remaining steps in the installer to complete the update.

The updated root certificate is applied, and the Failover Management Service (MS) starts successfully.

Fresh Installation Fails Due to MS Not Starting Automatically

During a fresh installation, the installer fails with the error:
Installer - Could not start service SOTI Connect - Management Server

Cause

The Management Server does not start automatically, preventing installation from completing.

Prevention

Reboot the VM before re-running the installer.

SOTI Connect URL is not Accessible After Update

After upgrading the SOTI Connect instance, the console URL might be inaccessible. Affected versions: SOTI Connect 2024.2 and later.

Cause

The Management Service does not open port 443 after the update.

Resolution

Restart the Management Service (MS). See Restarting Management Service for more details.