Microsoft bug in 10.0.43 version related to handling ISV licenses. Microsoft is working on hotfix now.
Microsoft bug in 10.0.43 version related to handling ISV licenses.
Microsoft is working on hotfix now.
Hopefully it will be a part of first Proactive Quality Update for 10.0.43 which is planned (there is not yet confirmation from Microsoft):
When it comes to technical details of this problem, it seems that during import of new license file it sets to "true" the parameter "allowCrossDomainInstallation" in the system table "SysConfig". This is parameter which allows to use license across different domains / tenants. Import of license should not set this parameter to "true", it should remain unchecked. So during import of Dynaway license file it sets to "true" this parameter for first license which is in the license file: "DynMP". And then second license from the file: "DynMPUsers" which requires as prerequisite the license "DynMP" cannot see that license "DynMP" has been imported and then whole import fails.
Below there is the standard Microsoft code where Microsoft during import of license sets parameter "allowCrossDomainInstallation" to "true".
The solution is to skip this Microsoft code by enabling flight class which is visible above: "SysLicenseDisableV2ISVLicenseFlight".
There are two ways to do that depending on the type of environment:
I. Environments in which you have access to related virtual machine and Visual Studio and SQL Server Management Studio.- Run below query in SQL Server Management Studio:
use AxDB;
insert into dbo.SYSFLIGHTING(FLIGHTNAME, ENABLED, FLIGHTSERVICEID) values ('SysLicenseDisableV2ISVLicenseFlight', 1, 12719367) - Restart IIS.
- Import license file again – it should work now.
II. Environments in which you do not have access to related virtual machine and Visual Studio and SQL Server Management Studio.
- Please contact Microsoft and ask them to enable flight class " SysLicenseDisableV2ISVLicenseFlight".