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 dear Soti Team,We are currently experiencing some problems with some Android 9 (Android Plus) Honeywell CT60s. We noticed that many devices are displayed as offline in the web view. We then noticed that the Mobicontrol Agent can no longer be opened on the devices and that the agent takes up the entire memory space of the device (15GB). The device can therefore no longer be administered.I read in the forum that this could be a bug in the SQL database on the device:https://discussions.soti.net/kb/android-enterprise-and-oem-specific-agents-are-crashing-after-agent-upgrade/Agent 14.3.4.1006 is currently installed on all affected devices.It is possible to copy a new agent via USB and install it over the device. I was able to install the following version: HoneywellMobiControl1442NewGen_1039.However, the problem persists, presumably because the defective and cluttered SQL database is still present in the background.Unfortunately, we have the feature control with "Disable removal of Mobicontrol Agent" active, which is why we are unable to completely remove the agent beforehand.Is there any way we can remove the complete Mobicontrol Agent installation in order to start a fresh installation of the agent? Unfortunately, Mobicontrol is still functional enough to prevent us from uninstalling it.It would be very bad for us if we now have to reinstall devices worldwide. Cheers Maik
Hi! Is there some way of issuing an adb shell intent command to a device running MobiControl to issue a script on the device? Does MobiControl have an intent receiver? The reason for this is that we have devices with a crashing agent as soon as we exit the lockdown manually, the devices are offline and can't be put online again so we want to be able to send script notify kiosk off to the devices.
Like the title says, for some reason the deployment sever crashed in the middle of the night and there was nothing to see in the Utility Manager of Soti. When seeing the logs, Im guessing that my server requirements aren't good enough. This is part of the MCdeplSvr.log. Opinions? 2019-01-25 00:01:44,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:45,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:46,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:47,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:48,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:49,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:50,499 (0x00001ff0) [INFO] CWinLogFile::WriteAllLog() PulseCheck enter: SendPulse=02019-01-25 00:01:50,499 (0x00001ff0) [ERROR] CWinLogFile::WriteAllLog() CommMgr::Pulse: Pulse timeout (index=960 ()), disconnect2019-01-25 00:01:50,499 (0x00001fec) [ERROR] CWinLogFile::WriteAllLog() ConnThread: index=960 (): Error 1236 receiving data2019-01-25 00:01:50,499 (0x00001fec) [INFO] CWinLogFile::WriteAllLog() Excessive queue length: 42, Threads: 233, Working: 233 (in 233). Add 1 new thread(s).2019-01-25 00:01:50,499 (0x00001ff0) [ERROR] CWinLogFile::WriteAllLog() CommMgr::Pulse: Pulse timeout (index=988 ()), disconnect2019-01-25 00:01:50,499 (0x00001fdc) [ERROR] CWinLogFile::WriteAllLog() ConnThread: index=988 (): Error 1236 receiving data2019-01-25 00:01:50,499 (0x00001ff0) [INFO] CWinLogFile::WriteAllLog() PulseCheck exit: SendPulse=0, total=916, sent=0, disconnected=2, finished in 0 ms2019-01-25 00:01:50,499 (0x00003e94) [INFO] CWinLogFile::WriteAllLog() Worker thread started2019-01-25 00:01:50,499 (0x00003e94) [DEBUG] ServerUtils::OnDeviceDisconnected() OnDeviceDisconnected: ConnId [1023]2019-01-25 00:01:50,499 (0x00003e94) [DEBUG] ServerUtils::OnDeviceDisconnected() OnDeviceDisconnected: Cannot find device associated with ConnId [1023]2019-01-25 00:01:50,499 (0x00003e94) [DEBUG] ServerUtils::OnDeviceDisconnected() OnDeviceDisconnected: ConnId [960]2019-01-25 00:01:50,499 (0x00003e94) [DEBUG] ServerUtils::OnDeviceDisconnected() OnDeviceDisconnected: Cannot find device associated with ConnId [960]2019-01-25 00:01:50,499 (0x00003e94) [INFO] CWinLogFile::WriteAllLog() Too many working threads 234/234, shutting down thread2019-01-25 00:01:50,499 (0x00003e94) [INFO] CWinLogFile::WriteAllLog() Worker thread terminated2019-01-25 00:01:50,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:51,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:52,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:53,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:54,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:55,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:56,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:57,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:58,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:01:59,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:00,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:01,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:02,936 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:03,718 (0x00001fdc) [INFO] CWinLogFile::WriteAllLog() Excessive queue length: 42, Threads: 233, Working: 233 (in 233). Add 1 new thread(s).2019-01-25 00:02:03,718 (0x00001b44) [INFO] CWinLogFile::WriteAllLog() Worker thread started2019-01-25 00:02:03,718 (0x00001b44) [DEBUG] ServerUtils::OnDeviceDisconnected() OnDeviceDisconnected: ConnId [988]2019-01-25 00:02:03,718 (0x00001b44) [DEBUG] ServerUtils::OnDeviceDisconnected() OnDeviceDisconnected: Cannot find device associated with ConnId [988]2019-01-25 00:02:03,718 (0x00001b44) [INFO] CWinLogFile::WriteAllLog() Too many working threads 234/234, shutting down thread2019-01-25 00:02:03,718 (0x00001b44) [INFO] CWinLogFile::WriteAllLog() Worker thread terminated2019-01-25 00:02:03,937 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:04,937 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:05,937 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:06,937 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:07,937 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:08,937 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:09,937 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:10,937 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:11,937 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:12,937 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:13,937 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:14,937 (0x00002ab8) [DEBUG] CJobDispatcher::DoWork() Throttled jobs: 80 m_nJobs: 101 m_nJobsInQueue: 02019-01-25 00:02:15,187 (0x00001fdc) [INFO] CWinLogFile::WriteAllLog() New connection entry, index=1023, name=*, host=95.129.123.180, sock=5204, port=569812019-01-25 00:02:15,187 (0x00001fdc) [DEBUG] CCommConnectionList::AddConn() CCommConnectionList::AddConn: index=1023 seg=16 segidx=152019-01-25 00:02:15,187 (0x00001fdc) [INFO] CWinLogFile::WriteAllLog() Excessive queue length: 42, Threads: 233, Working: 233 (in 233). Add 1 new thread(s).2019-01-25 00:02:15,187 (0x00003508) [INFO] CWinLogFile::WriteAllLog() Worker thread started2019-01-25 00:02:15,187 (0x00003508) [INFO] CWinLogFile::WriteAllLog() Too many working threads 234/234, shutting down thread2019-01-25 00:02:15,187 (0x00003508) [INFO] CWinLogFile::WriteAllLog() Worker thread terminated
Hi, Last Sunday, I upgraded MobiControl from 14.0 to 14.0.2 and it's been a nightmare since. I had no issues with 14.0, but the upgrade to 14.0.2 has been regretful. Apart from dealing with SSL certificate issues, the biggest problem is MobiControl services continuously stopping for no reason. Right now, the Management Service continuously crashes every 5 to 15 minutes or so. Event Viewer shows the following: Faulting application name: Soti.MobiControl.ManagementService.Host.exe, version: 14.0.2.264, time stamp: 0x5a20b632 Faulting module name: clr.dll, version: 4.7.2558.0, time stamp: 0x59d414b7 Exception code: 0xc00000fd Fault offset: 0x000000000001358b Faulting process id: 0x1190 Faulting application start time: 0x01d3938af831b940 Faulting application path: C:\Program Files\SOTI\MobiControl\Soti.MobiControl.ManagementService.Host.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: 51619607-ff7f-11e7-80ce-005056acfd5b Faulting package full name: Faulting package-relative application ID: MobiControl's Management Service log mentions the following failures: * Exception: A task was canceled. * [InternalLogicException: Failed to send HTTP request to proxy target] at Soti.MobiControl.Ngui.WebConsole.Handlers.ConsoleApiProxyHandler.d__4.MoveNext() * Exception: Cannot access a disposed object. Object name: 'System.Net.HttpListenerRequest'. * [ObjectDisposedException: Cannot access a disposed object. Object name: 'System.Net.HttpListenerRequest'.] Here's a new one I haven't seen before (yet more certificate errors): Exception: The message could not be processed. This is most likely because the action 'http://tempuri.org/ICacheProxyService/GetByKeys' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding. * I noticed this occurs when a technician loads the WebConsole on their first login/session (and then subsequently receives an HTTP 404 error). We then have to wait a few minutes for the service to restart, or restart it manually if the application crashed too many times. On average, the service crashes at least ten (10) times in an hour. I've tried upgrading the .NET Framework runtimes to 4.7.1 to no avail. I also upgraded Java to the latest 1.8u161 and saw no improvement. Searching the web for this type of error yields many results, including one about a Microsoft-supplied hotfix and another about switching .NET JIT compilation modes. Virtual machine specifications: Windows Server 2012 R2 Standard Microsoft SQL Server 2014 SP2 Express 2 vCPU cores with 8GB of memory 2-tier Enterprise PKI for certificates, trusted by all computers One thing I'd like to mention is that MobiControl's WebConsole is served via a NGINX reverse proxy with its own public SSL Certificate from Let's Encrypt (separate machine) while port 5494/5495 is NAT'ed directly to the MobiControl server. This setup worked flawlessly on 14.0. The only certificate I have overridden in MobiControl is the "Deployment Server Extensions and Web Console" while the insecure RSA1 1024-bit original MobiControl Root CA and related certificates still handle everything else. I'm more than eager to change them to our PKI certificates, however I'd like to sort out the current issues at hand first. Anyone else experiencing issues with the latest update or can provide some insight into the matter?
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
