File synchronization failed - why?

Solved Locked

Hi All,

I have created a file sync rule which copies a file TO the root of the device. But I keep getting the error: File Synchronization failed ...

Device File = %sdcard%\url.CapMgmt
Server File = \\ServerName\folder1\folder2\url.CapMgmt

I'm completely new to this software.
What could be wrong?
File is accessible, but can't be delivered to the device.

I've also noted that in the logs says %%sdcard%% (see DS log below)

DS log says:

2021-03-25 09:43:01,724 (0x00000364) [ERROR] [ 14] Comm.Client.1 [354401112252426]: SendFileAsync(%%sdcard%%\url.CapMgmt): Device reported error PackageFileIoError
2021-03-25 09:43:01,724 (0x00000364) [ERROR] startTransfer: File transfer error reported from device. All files of the same rule will discard. Rule: 24, device: '354401112252426'


Any advice is welcome.

4 years ago
Android
ANSWERS
RC
Raymond Chan Diamond Contributor
4 years ago (edited 4 years ago)

MobiControl device agent itself is nothing more than a normal app, which has read/write permissions to its own app folder and all the standard public folders shared by all other apps.    However, the device agent has access to certain MDM API's requesting the system/kernel modules to perform some tasks (e.g. pushing app) on its behalf.

So, for file-sync rule, the write operations on the device file-system are basically allowed for the agent own folder and various public folders shared by all apps.

    

Solution
RC
Raymond Chan Diamond Contributor
4 years ago

The likely cause in your case is that the Mobicontrol device agent has no write permission to your current target device directory.  

MD
Matt Dermody Diamond Contributor
4 years ago
K
KAS001
4 years ago

Hi Raymond,

Thanks for your reply. and what could cause this issue that the agent has no write permissions?
We where able to push some apps. So I would think the agent has sufficient rights no?

Or is pushing apps and file sync using a different approache of security/permissions?

K
KAS001
4 years ago

Hi Matt, also thank for your reply.

Checking version, we are using MC V15.2.3.1033
Though thx for the article reference Matt.

K
KAS001
4 years ago

okay, thx for the clerification on this.