Fixed - Agent direct download issue v15.4

G
Glen
City Care Ltd

Hi All,

Accidentally deleted my original post when trying to post a fix... so apologies to all that was following my other post

Quick Background

Since upgrading MobiControl to v15.4 we notice an issue with direct downloading the agent when trying to enroll a device.

We would constantly get the following error when we hit the download button on the mobile device when enrolling and it would fail

 

This is a fix for that issue that worked for me. So use this at your own risk. 

I will summarise the fix, so if you need a bit more info let me know as it can get technical 

For this fix, you will need to be able to access and edit your SQL database for MobiControl

Edited 3 years ago
SOTI MobiControl
ANSWERS
G
Glen
3 years ago (edited 3 years ago)

Had to break this up as the forum posting system does not like this and what made me accidentally remove my last post

Step 1. Checking the agent APK file ID

 - Open your Mobicontrol web console and navigate to 'Servers'

 - Go down to Global Setting and hold 'Ctrl + Shift' and left click on 'Mobicontrol'. This will open the advance file browser 

 

- Once the file browser is open, in the drop down select 'Android device agent'

- Find the Agent that you are trying to access. in my case this was the Samsung one - ID 31710

- Note the ID number for this APK as we will need it later

 Step 2. Checking the Database

- You will now need to log into your SQL server and locate the MobiControl database

- Expand the database and expand the tables and find the table dbo.ApkType

- Right click and select 'Select Top 1000 Rows"

- In the Query window add the following on a new line, where Samsung% is the name of the agent you are looking for. In my case I am looking for the Samsung APK

      WHERE NAME like 'Samsung%'

- Parse the query then execute. I got the following result below. 

This is the packages the database knows of for samsung. Remember the ID number of the APK we got from step 1, this references the PackageName. In my case im looking for 31710, last line.

Now remember my original issue. The download was trying to look for package 31298 and fails to download

Now if we try to look for this ID 31298, in the File browser back in step 1, this ID number does not exist. And hence the issue as the APK file does not exist

NOTE - BACKUP your Database before you make any changes

For my fix, I needed to delete the records that that referred to the APK ID that do not exist.

In my case, i had to remove 3 lines, leaving the only valid one ID 31710

 

After removing these line, it fixed my issue

G
Glen
3 years ago

Hopefully this helps and, so I am told, has been raised internally with Soti as a bug to the development team 

Similar Discussions