No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
Hello Everyone, Can someone suggest on this error that we are getting while enrolling android devices. Last Staging Error # 3 Possible problems :- A File or folder that is needed for staging could not be found. Original Error :- Batch decoding -Exception, Could not decode profile date The same Stagenow barcode working fine until last week and there isn't change anything but it now stopped working and getting below error attached in picture.
Has anyone else had this issue? I'm trying to enroll an Android 10 device but it fails to connect to the server. Cloud based server, running 13.4. Zebra TC57x running OS10. MobiControl is set as DO. TIA.
I am trying to enroll a Samsung x cover pro 2 via afw but once I enter my enrollment id into mobicontrol. I will get: Enrollment Failed. Please retry or contact your system administrator. I have tried enterprise and plus with the same result have also tried both google play install and from the website. I believe it has something to do with Knox as I never have this issues with my zebra's only with Samsung's and only every once and a while. Currently on V14.1.8.1064
Dear Community! Please help me. I'd like to enroll a Zebra MC3300, but "Enrollment failed". Parameters: Android 8.1 - Build number: 02-32-04-.00-OG-U001-STD SOTI Android Enterprise Agent: GoogleMobiControl1444_1051 VERY IMPORTANT: the Remote Control feature is necessary!!! I have no idea how can I manage the correct enrollment, earlier I had some success enrollment with this MC3300 device but only with Work Profile, only Remote View feature. Thanks in advance. Regards: SN
MobiControl 15.2.3.1033 Agent 14.4.1.1064 Samsung Device OEM Version QP1A.190711.020.A505FNXXS5BTJ4 Samsung devices updated to the latest firmware are returning a Device APIiD of 840. This value is missing from the database table [MobiControlDB].[dbo].[AndroidDeviceAPILkUp] Which leads to the following error in the logs. 2020-11-17 18:02:03,527 (0x00000ae0) [ERROR] System.Data.SqlClient.SqlException (0x80131904): The MERGE statement conflicted with the FOREIGN KEY constraint "FK_AndroidDeviceAPI_APIId". The conflict occurred in database "MobiControlDB", table "dbo.AndroidDeviceAPILkUp", column 'APIId'.The statement has been terminated. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Soti.MobiControl.Platforms.Android.Devices.DeviceApi.Providers.Implementation.AndroidDeviceAPIDataProvider.AndroidDeviceAPI_Merge_ByDeviceIds(ICollection`1 deviceAPIDatas) at Soti.MobiControl.Platforms.Android.Devices.SupportedApisUpdateHandler.Handle(Int32 deviceId, IEnumerable`1 supportedApis) at CSOTIDatabase.UpdateDeviceDSE(CSOTIDatabase* , CDBDevice* device, Boolean aUpdateCustomData)ClientConnectionId:83d5e0b8-f454-4170-97ab-a19854ab0cafError Number:547,State:0,Class:16 This error is preventing those devices from enrolling completely. As this was urgent I had a guess at what should be in that table and came up with the following. APIId = 840 Description = MCW.enums.DeviceAPI.SamsungKnoxV34 APIName = SamsungKnoxV34 The change works in so far as the devices will now enroll but does not display the proper API name in the web console. Is there a script that needs to be run to add these new API levels to the database properly? N.B This appears to be the same issue as https://discussions.soti.net/thread/enrollment-problem-with-client-14-4-1-1064-on-server-15-1-0-3416/
Hi. I have a trouble with enrolling devices to my SOTI server. Here is a screenshot with messages which I can't get rid of and enroll any device, using google mdm account in SOTI. Device: Samsung J5Android version: 9Knox version: 3.4Playstore version: 22.4.25-21Soti Server version: 15.1.0.3413 Soti mobile version: 14.1.4 Build 1010 At the beginning, there were any problems with enrolling device. I've could enroll more than 50 device in the same day.Later, only 10 a day. Next day there were no problems to continue enrolling.After few weeks, only one device a day.Now, I can't enroll any device. Sometimes, I need to wait few days, sometimes more than a week to enroll.This problem started from June and still persist. There is no any problems with SOTI license or Samsung ELM, because device is always succesfully enrolled without google account. What i've tried:- create a new rule with another mdm google account and enrolling device: success.- enroll device without google account: success.- reboot server, reboot device: still not working.- check if hash for mdm google account is the same. Are the same, but device still stuck in same message. - enroll devie in another server and without google account: success.Is there any google account limitations for how much devices you can enroll via MDM? Thanks.
I have enrolled some Android 9 and 10 using the same add rules, with no problem et all. Unfortunately the Samsung A10, when in Android 10, hangs on the step to add account. It does not matter how many times we touch/click the message to add account, it does not proceeds further the installation. Usually, touching exhaustive on Google account it flows, but not for this case. Is there any work around to add the managed google account ?
Hi!, Problem: - I have a problem with google account identities status is "Account Activation Pendding" after successful enrollment. - At MobiControl WebConsole show log "Error message received from device (Managed Google Play Account Status:'EMPTY_TOKEN Got response but there was no token!')" - At device show "Pending Actions" Google account Completing configuration for your Work Profile *** Before that, I had a device that was successfully registered. Without any problems * Addition detail - I set up device and install Mibicontrol from "afw#mobicontrol" before final success set up device complete
Hello, we have a mobicontrol on version v 13.3.34 54 and of course we migrate (device are zebra TC75X android 7.1 Enroll type android +) We have made a backup of the database of mobicontrol install it on a new server. Actually, we made the upgrade on a test server with the version of mobicontrol 14.4.49 all port are open of course and 80% of my test are Ok. This is the good new :). But I don't know why but for some device ALWATS Zebra TC75X android 7.1 when i try to enroll it , i have an error message I type the URL or enrollmentId in the client of mobicontrol (zebra TC75X) and I have an standard error -> contact your admin system .. mobicontrol Client on device are on version 13 6 1476 In the log file of DSE I have this : [2020-09-10 11:00:06.311] ERROR [General] (20): Unable to locate device with id '100002119'. Mapping for device with id '8867948f33f105010019146522504865' is invalid and will be removed. [2020-09-10 11:00:06.311] ERROR [General] (20): ************************************************************************* * Exception: Device '8867948f33f105010019146522504865' does not exists. * ************************************************************************* [AccessControlException: Device '8867948f33f105010019146522504865' does not exists.] at Soti.MobiControl.Controllers.DeviceController.GetDeviceByExternalId(String deviceId, Boolean loadDetails) at Soti.MobiControl.Api.Implementation.Com.DeviceConfigurationFacade.GetConfiguration(String deviceId) I've try to factory reset device, reboot, but actually it's not possible to enroll 4 devices and i don't know why .. Some people can tell me what's happen ? thanks fpr your help
I can install the Enrollment Profile without issue, but when I go to actually enroll a MacOS Catalina device I get this error. I've tried it on three different systems so far today and all give the same error. It says: Profile Installation Failed. The profile "MobiControl Device Enrollment (net.soti.mobicontro.enrollment.phase1:uuid-here)" could not be installed due to an unexpected error. <NSCocoaErrorDomain:3840>
Trying to enroll some Amazon Fire 7 (2019) tablets into Mobicontrol, however the "Amazon" agents both install but error out afterwords saying they are not compatible. Is there a compatible agent for these devices?
Hello everyone! I'm having problems enrolling devices in my MobiControl server, the kind of devices I'm enrolling is: Android Plus. Without Google Account. Models are: Samsung G532M, G532MT, J320M. After they are enrolled to the server, they're agent are not compatible with my actual version of MobiControl, even after I checked the version that has been configured with the device add rule. How can I fix this?
I am trying to enroll my device onto the Soti MobiControl on an IoS device. I have successfully installed the enrollment profile but when it comes to enrolling the device I get the attached error. Any ideas on what is going wrong?
I have followed the steps to enroll an apple BYOD device but get the following error when I try to connect using the url on the apple device. Including setting up the apple push notification service and setting up the rule appropriately. "Your device is not authorized to enroll using the specified enrollment details" Could you please tell me what I might be doing wrong
I have two Zebra VC80X devices that I deleted from the management console and performed a factory reset on each. Now when I try to re-enroll them with MobiControl Stage they are both getting a "Duplicate Device ID" error and they won't enroll. I checked and rechecked that the devices have been deleted from the management console so I'm at a loss as to why it keeps saying Duplicate Device ID. Please help.
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points.
Highly experienced members with valuable inputs. Should have more than 700 points.
Beginners taking the initiative. Should have more than 500 points.
New contributors starting their journey. Should have more than 250 points.
