There's a new home for Articles. Find Articles on Our Product Support Page.
When trying to install a new on-prem server with MobiControl 15.4.1 Build 4828 on a Microsoft Server 2019, where the DB is located on a separate Server 2016 with SQL Server 2016 SP3 we face an error during the installation phase. All System Requirements are verified to be met according to the help section area (Link) Error seen on the installation Wizard and part of the log seen below. Any idea why this might be happening? 2021/11/02 07:37:43.070(0x00001ff0): EVENT: Add shared file: type=9, name=trimble_apk_enrollment.png2021/11/02 07:37:43.102(0x00001ff0): EVENT: Add shared file: type=9, name=unitech_apk_enrollment.png2021/11/02 07:37:43.117(0x00001ff0): EVENT: Add shared file: type=9, name=urovo_apk_enrollment.png2021/11/02 07:37:43.117(0x00001ff0): EVENT: Add shared file: type=9, name=vuzix_apk_enrollment.png2021/11/02 07:37:43.133(0x00001ff0): EVENT: Add shared file: type=9, name=winmate_apk_enrollment.png2021/11/02 07:37:43.149(0x00001ff0): EVENT: Add shared file: type=9, name=xplore_technology_apk_enrollment.png2021/11/02 07:37:43.164(0x00001ff0): EVENT: Add shared file: type=9, name=zebra_apk_enrollment.png2021/11/02 07:37:43.180(0x00001ff0): EVENT: Add shared file: type=9, name=zebra_concierge.png2021/11/02 07:37:43.180(0x00001ff0): EVENT: Add shared file: type=9, name=zebra_ET1_GB.png2021/11/02 07:37:43.195(0x00001ff0): EVENT: Add shared file: type=9, name=zebra_MC36_apk_enrollment.png2021/11/02 07:37:43.211(0x00001ff0): EVENT: Add shared file: type=9, name=zte_apk_enrollment.png2021/11/02 07:37:43.227(0x00001ff0): EVENT: Add shared file: type=48, name=AzureTOUResources.zip2021/11/02 07:37:43.305(0x00001ff0): EVENT: Reading file "C:\Users\USERID~1\AppData\Local\Temp\2\{37D25AE5-5AA3-4A50-A848-A8EAA76B1726}\{C3D9886D-256E-42B7-8026-8625E505C3C4}\InstallerInfo.xml" in order to determine the build number.2021/11/02 07:37:43.305(0x00001ff0): EVENT: Determined the build number: 4828.2021/11/02 07:37:43.321(0x00001ff0): EVENT: Reading file "C:\Users\USERID~1\AppData\Local\Temp\2\{37D25AE5-5AA3-4A50-A848-A8EAA76B1726}\{C3D9886D-256E-42B7-8026-8625E505C3C4}\InstallerInfo.xml" in order to determine the build number.2021/11/02 07:37:43.399(0x00001ff0): EVENT: Determined the build number: 3829.2021/11/02 07:37:43.414(0x00001ff0): WARNING: DBLoad: Failed to read SSL Mode from Settings table rc = 22021/11/02 07:37:43.414(0x00001ff0): WARNING: DBLoad: Failed to read root CA from Settings table rc = 22021/11/02 07:37:43.430(0x00001ff0): WARNING: DBLoad: Failed to read iOS Intermediate CA from Settings table rc = 22021/11/02 07:37:43.430(0x00001ff0): WARNING: DBLoad: Failed to read iOS Profile signing cert ID from Settings table rc = 22021/11/02 07:37:43.430(0x00001ff0): WARNING: DBLoad: Failed to read cloud link cert ID from Settings table rc = 22021/11/02 07:37:44.820(0x00001ff0): WARNING: DeleteCertWithSubjectContainCN Failed to delete from 'ROOT', hr=12021/11/02 07:37:44.883(0x00001ff0): ERROR: CryptImportKey failed with 52021/11/02 07:37:44.883(0x00001ff0): ERROR: CMCCertUpdate::CreateRootCert: Failed to import the MobiControl root certificate ID 1.2021/11/02 07:37:44.883(0x00001ff0): ERROR: OLEDB error: [80004005, 3903] The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION.2021/11/02 07:37:44.883(0x00001ff0): ERROR: SQL state: [3903] 250002021/11/02 07:37:44.899(0x00001ff0): ERROR: CMCDbAccess::CheckResult:The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION.
This is an update to my original problem with upgrading to v15, as the original post has been locked, so I thought I'll share the fix that Soti support gave that fixed our problem as I dont see any other posts about this issue. https://discussions.soti.net/thread/has-anyone-experienced-sql-errors-when-updating-to-15-3-dacpac-dac-message-warning-sql72015 Summary TL;DR So we had a SQL72015 error every time we tried to upgrade to v15.x from v14.5. And was told we had to wait for SQL 2019 support in v15.4, which we did, but unfortunately that still same error and could not upgrade. Logged new ticket with Soti support and after investigating the issue, they gave the following SQL fix that solved our issue. Use the following SQL query at your own risk, this is what was provided to us to fix my issue. This may not work for everyone 1. Take server snapshot and db backup of your Mobicontrol server. 2. Launch SQL server Management studio and login 3. Right click on MobiControlDB and click on 'New Query' 4. Paste the sql query and execute it. 5. Restart MC services (Deployment Server and Management Server) -----code---- DELETE FROM dbo.Container;SET IDENTITY_INSERT dbo.Container ON;INSERT INTO dbo.Container( Id, Name)VALUES( 0, 'No Container'),( 1, 'KNOX Container'),( 2, 'Android Profile Container');SET IDENTITY_INSERT dbo.Container OFF; -----code----
Hi, Just wondering if anyone know if Mobicontrol support SQL 2019 yet? Requirement page still says "consider using Microsoft SQL Server 2016 or later" and list SQL 2016 and SQL 2017 as minimum requirements but the last i heard was that Mobicontrol doesnt support SQL 2019 yet. I did see on the download page 15.4 show up yesterday but today it has gone back to 15.3.3. Do we know when they are releasing new version and will this have SQL 2019 suppost?
Hi All, So I'm looking at moving MobiControl into my originations AWS cloud. My device count is too big for using SQL express, we keep hitting the max DB size and memory limits of SQL express. If following the Soti Sys requirements guide, it would seem that SQL Standard is the preferred database engine to migrate to. SQL Std is quite a large investment, especially as this would not be a shared DB instance for other applications. So my question is, can we use SQL Web edition to host the SOTI database? It has the larger memory, CPU and size limits that I'm looking for, but at half the monthly licensing cost in AWS. Can anyone confirm that they have tried this and that it is Kosher, both with SOTI support and with MS licensing? Thanks Dan
Hello, the SotiServer is running on a WinServer 2012R2 we are planning to upgrade to WinServ2016. We do have a sql server 2016 but only Version 13.0.1742.0 no Service Pack 2 installed right know. We also have an on premise SotiServer Version: 14.2.1.4394 we plan a upgrade to Version 15.1.3. 15.1.X Recommended specs: Component Recommended Level for 15.1 Software Microsoft SQL Server 2014 Microsoft SQL Server 2016 (Service Pack 2 Cumulative Update 1) Microsoft SQL Server 2017 So we could upgrade our SQL Server to SP2. But would the 15.1.3 SotiServer Version also run with SQL Version 13.0.1742? What is best practice here? Update Windows Server to 2016 Update SQL Server Update SotiMobicontrol Server We would like to know what you would suggest. Thank you very much. Kind regards Michael
We have MobiControl 14.1 We have the sql database on seperat windows server for DB. A SQL 2014. My question is: can running the SQL DB also on an "Windows Server 2016 CORE" Version? Which version SQL can used for DB ? SQL2016 ?
Are there any SQL DML scripts that should be run as a means of housekeeping prior to upgrading MobiControl? Should we shrink the database prior to upgrade?
Hi, We are planning to upgrade our MobiControl installation. We curently have the MobiControl databases on a standalone SQL server which has other production databases. Since the database user must be a SysAdmin or a DbCreator for the upgrade process to complete, we have concerns that the upgrade process might affect in some way the other databases or the SQL server itself (stop/start). If anybody already successfully went through such upgrade scenario, please share.
I have tried Mobicontrol connected to SQL Server 2017 running in Linux. It is working fine so far. Have you ever tested that enviroment? Will Soti support SQL Server in Linux?
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