SOTI Pulse Logo

DB migration errors

Solved
EE
Emil Eek
Bulten Arendal AB

Hello,

I have migrated our SOTI Dbs (MobiControlDB, MobiControlDB_Archive, MobiControlDB_Signal, SotiAssist) from one dedicated DB-server to another DB-server. All on-prem.
Old SQL: 2019
New SQL: 2022

The problem now is that the "Mobicontrol Deployment Service" does not run properly. All other services are running smoothly. I can access the web console but I do not get any contact with any device. I have already ruled out any port errors. Everything works good again if I switch back to the old DB-server.

Any help regarding this would be invaluable.

soti services
6 months ago
SOTI MobiControl
ANSWERS
S
SSMOD@SOTI
6 months ago

Based on the screenshots from the MobiControl Admin Utility and the SOTI Pulse dashboard, the errors indicate that the system is still attempting to connect to the old Deployment Server IP (10.26.10.230) on port 5944, also the port 5494 is the one for the deployment server you can try. Which is now inactive following your SQL Server migration to a new dedicated DB server (SQL 2022).

The exception SocketException (10061) means the connection is being actively refused, most likely because the Deployment Server is no longer listening on that IP, or the IP reference was not updated post-migration.

Recommended Action Steps:

Step 1:

Verify the current IP address of the new DB/Deployment Server and ensure port 5494 is listening (netstat -an | find "5494").

Step 2:

Launch the MobiControl Admin Utility and go to Deployment Server Settings.

Update the host/IP address to reflect the new server IP.

Ensure port 5494 is correctly configured and reachable.

Step 3:

Restart the following services on the new DB server:

SOTI MobiControl Deployment Server

SOTI MobiControl Device Management Server

Step 4:

Optionally, validate backend configuration using SQL:

SELECT * FROM DeploymentServers;

SELECT * FROM SystemSettings WHERE SettingName LIKE '%ServerAddress%';

Replace any outdated entries pointing to 10.26.10.230 with the new IP or hostname.

Step 5:

After applying changes, re-run the "Test Now" from the Admin Utility to confirm successful connectivity.

EE
Emil Eek
6 months ago

Hello,

The deployment server is separate from the DB server and has not changed. The only change is the DB server.

Services has been restarted already with the same error.

The tables you are referring to, which database are they inside? I cannot find them in any of my Mobicontrol DBs.

S
SSMOD@SOTI
6 months ago

Thank you for the clarification. Since the Deployment Server remains unchanged and only the SQL Server has been migrated, the issue likely relates to a connectivity problem between the Deployment Server and the new SQL Server instance. Please review the following action points:

Verify SQL Connectivity:
From the Deployment Server, use SQL Server Management Studio or the sqlcmd utility to confirm that a connection can be established with the new SQL Server.
cmd:
sqlcmd -S <New_SQL_Server> -U <Username> -P <Password>

SQL Server Configuration:
Ensure that the SQL Server is configured to allow remote connections, TCP/IP is enabled in SQL Server Configuration Manager, and the appropriate port (typically 1433) is open and listening.

Update Configuration on Deployment Server:
Check the configuration files or registry settings on the Deployment Server—commonly found under:
HKEY_LOCAL_MACHINE\SOFTWARE\SOTI\MobiControl
Ensure the database connection string has been updated to reflect the new SQL Server details.

Review Log Files:
Examine the logs on the Deployment Server, usually located in:
C:\Program Files\SOTI\MobiControl\Logs\
Look for any SQL-related errors (e.g., login failures, connection timeouts, or network issues).

Database Schema Clarification:
In your case, the ServerInfo table contains relevant Deployment Server information. Please confirm the MobiControl version and the database name currently in use. Alternatively, you may run the following query to locate related tables:

SELECT name FROM sys.tables WHERE name LIKE '%Server%' OR name LIKE '%Setting%';

 

Solution
EE
Emil Eek
6 months ago

Hello,

The SQL DB connection was fine in MobiControl Administration Utility but nevertheless I tried to establish a connection manually via SSMS from the deployment server.

I could not find your referred registry value so I gave up on that and just pressed "Test Now" under system health. For some reason all services are now working correctly.

Could it be that you need to establish a manual connection to the DB for the service to start working correctly? That is the only thought that comes to mind. And in that case, why?

S
SSMOD@SOTI
6 months ago

Thank you for the update, and I'm glad to hear the services are now working as expected. Regarding your observation, here are a few possible explanations:

Manually connecting to the database may have helped confirm the connection path from the Deployment Server.

Using the “Test Now” function could have refreshed the system checks and helped restart the connection properly.

It's possible the services were temporarily stuck and the test helped them re-establish the link to the database.

I wonder, the possible reason for the correct connection could be Stale or cached connection was cleared by manual access., Services were in a waiting state, and the test forced them to retry the connection with database or Credentials may have refreshed during the test.

While this is not a standard requirement, these actions may have helped reset or trigger the correct service behavior. We recommend observing the system for next 24 to 48 hours to ensure everything remains stable.

Similar Discussions