Wix Minimal UI doesnt show up - visual-studio-2017

I'm trying to create a simple installer with Wix, but the Windows Installer doesn't show up. So I've tried the basics, which is:
Add Wix v3 Setup project
Fill in Manufacturer
Build and open the .msi
It shows a popup with "Title" Preparing to install
Add reference WixUIExtension
Add <UIRef Id="WixUI_Minimal" /> so should it should show the UI
Build and open the .msi
Nothing appears and I have to kill the Windows Installer via Task Manager
What could be wrong?
Answer to Stein:
Prevalence: Do other MSI files work without issues?
The built-in VS Setup Wizard builds a .msi which works.
Timeout: How long do you wait for the MSI to initialize?
10 minutes
Source: Maybe post your whole source.
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">
<Product Id="*" Name="MinimalTester" Language="1033" Version="1.0.0.0" Manufacturer="MinimalTester" UpgradeCode="795294d8-45b1-4110-a80c-4a593e86bc68">
<Package InstallerVersion="200" Compressed="yes" InstallScope="perMachine" />
<MajorUpgrade DowngradeErrorMessage="A newer version of [ProductName] is already installed." />
<MediaTemplate EmbedCab="yes" />
<UIRef Id="WixUI_Mondo" />
<WixVariable Id="WixUILicenseRtf" Value="TestLicenseAgreement.rtf" />
<Feature Id="ProductFeature" Title="MinimalTester.Installer" Level="1">
<ComponentGroupRef Id="ProductComponents" />
</Feature>
</Product>
<Fragment>
<Directory Id="TARGETDIR" Name="SourceDir">
<Directory Id="ProgramFilesFolder">
<Directory Id="INSTALLFOLDER" Name="MinimalTester" />
</Directory>
</Directory>
</Fragment>
<Fragment>
<ComponentGroup Id="ProductComponents" Directory="INSTALLFOLDER">
<Component Feature="ProductFeature">
<File Source="C:\Source\TestApp\bin\Debug\TestApp.exe" />
</Component>
</ComponentGroup>
</Fragment>
Logging: Always make a log file for your installation session to debug.
=== Verbose logging started: 10/12/2018 08:43:43 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (EC:A0) [08:43:43:124]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (EC:A0) [08:43:43:125]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (EC:7C) [08:43:43:158]: Resetting cached policy values
MSI (c) (EC:7C) [08:43:43:159]: Machine policy value 'Debug' is 0
MSI (c) (EC:7C) [08:43:43:159]: ******* RunEngine:
******* Product: TestApp.Installer.msi
******* Action:
******* CommandLine: **********
MSI (c) (EC:7C) [08:43:43:166]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (EC:7C) [08:43:43:227]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (c) (EC:7C) [08:43:43:228]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Source\TestApp\bin\Debug\TestApp.Installer.msi' against software restriction policy
MSI (c) (EC:7C) [08:43:43:229]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (c) (EC:7C) [08:43:43:229]: SOFTWARE RESTRICTION POLICY: C:\Source\TestApp\bin\Debug\TestApp.Installer.msi is not digitally signed
MSI (c) (EC:7C) [08:43:43:231]: SOFTWARE RESTRICTION POLICY: C:\Source\TestApp\bin\Debug\TestApp.Installer.msi is permitted to run at the 'unrestricted' authorization level.
MSI (c) (EC:7C) [08:43:43:237]: Cloaking enabled.
MSI (c) (EC:7C) [08:43:43:237]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (EC:7C) [08:43:43:241]: End dialog not enabled
MSI (c) (EC:7C) [08:43:43:241]: Original package ==> C:\Source\TestApp\bin\Debug\TestApp.Installer.msi
MSI (c) (EC:7C) [08:43:43:241]: Package we're running from ==> C:\Source\TestApp\bin\Debug\TestApp.Installer.msi
MSI (c) (EC:7C) [08:43:43:243]: APPCOMPAT: Compatibility mode property overrides found.
MSI (c) (EC:7C) [08:43:43:244]: APPCOMPAT: looking for appcompat database entry with ProductCode '{A401E2B5-DBD1-41AC-8F84-BC9EAF39E728}'.
MSI (c) (EC:7C) [08:43:43:244]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (EC:7C) [08:43:43:253]: MSCOREE not loaded loading copy from system32
MSI (c) (EC:7C) [08:43:43:256]: Machine policy value 'TransformsSecure' is 0
MSI (c) (EC:7C) [08:43:43:256]: User policy value 'TransformsAtSource' is 0
MSI (c) (EC:7C) [08:43:43:256]: Note: 1: 2205 2: 3: MsiFileHash
MSI (c) (EC:7C) [08:43:43:256]: Machine policy value 'DisablePatch' is 0
MSI (c) (EC:7C) [08:43:43:256]: Machine policy value 'AllowLockdownPatch' is 0
MSI (c) (EC:7C) [08:43:43:257]: Machine policy value 'DisableMsi' is 0
MSI (c) (EC:7C) [08:43:43:257]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (c) (EC:7C) [08:43:43:257]: User policy value 'AlwaysInstallElevated' is 0
MSI (c) (EC:7C) [08:43:43:257]: Running product '{A401E2B5-DBD1-41AC-8F84-BC9EAF39E728}' with user privileges: It's not assigned.
MSI (c) (EC:7C) [08:43:43:257]: Machine policy value 'DisableLUAPatching' is 0
MSI (c) (EC:7C) [08:43:43:257]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (c) (EC:7C) [08:43:43:257]: APPCOMPAT: looking for appcompat database entry with ProductCode '{A401E2B5-DBD1-41AC-8F84-BC9EAF39E728}'.
MSI (c) (EC:7C) [08:43:43:257]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (EC:7C) [08:43:43:257]: Transforms are not secure.
MSI (c) (EC:7C) [08:43:43:257]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Source\TestApp\bin\Debug\Your.log'.
MSI (c) (EC:7C) [08:43:43:257]: Command Line: CURRENTDIRECTORY=C:\Source\TestApp\bin\Debug CLIENTUILEVEL=0 CLIENTPROCESSID=18924
MSI (c) (EC:7C) [08:43:43:257]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{60067773-7475-4FB5-B5D0-26E6934E64E2}'.
MSI (c) (EC:7C) [08:43:43:257]: Product Code passed to Engine.Initialize: ''
MSI (c) (EC:7C) [08:43:43:257]: Product Code from property table before transforms: '{A401E2B5-DBD1-41AC-8F84-BC9EAF39E728}'
MSI (c) (EC:7C) [08:43:43:257]: Product Code from property table after transforms: '{A401E2B5-DBD1-41AC-8F84-BC9EAF39E728}'
MSI (c) (EC:7C) [08:43:43:257]: Product not registered: beginning first-time install
MSI (c) (EC:7C) [08:43:43:257]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
MSI (c) (EC:7C) [08:43:43:257]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (c) (EC:7C) [08:43:43:257]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (EC:7C) [08:43:43:257]: Adding new sources is allowed.
MSI (c) (EC:7C) [08:43:43:257]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
MSI (c) (EC:7C) [08:43:43:258]: Package name extracted from package path: 'TestApp.Installer.msi'
MSI (c) (EC:7C) [08:43:43:258]: Package to be registered: 'TestApp.Installer.msi'
MSI (c) (EC:7C) [08:43:43:258]: Note: 1: 2205 2: 3: Error
MSI (c) (EC:7C) [08:43:43:258]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (c) (EC:7C) [08:43:43:258]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (c) (EC:7C) [08:43:43:258]: User policy value 'AlwaysInstallElevated' is 0
MSI (c) (EC:7C) [08:43:43:258]: Running product '{A401E2B5-DBD1-41AC-8F84-BC9EAF39E728}' with user privileges: It's not assigned.
MSI (c) (EC:7C) [08:43:43:258]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\Source\TestApp\bin\Debug'.
MSI (c) (EC:7C) [08:43:43:258]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '0'.
MSI (c) (EC:7C) [08:43:43:258]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '18924'.
MSI (c) (EC:7C) [08:43:43:258]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
MSI (c) (EC:7C) [08:43:43:258]: TRANSFORMS property is now:
MSI (c) (EC:7C) [08:43:43:258]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '200'.
MSI (c) (EC:7C) [08:43:43:259]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\AppData\Roaming
MSI (c) (EC:7C) [08:43:43:259]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\Favorites
MSI (c) (EC:7C) [08:43:43:259]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (c) (EC:7C) [08:43:43:259]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\Documents
MSI (c) (EC:7C) [08:43:43:259]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (c) (EC:7C) [08:43:43:260]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\AppData\Roaming\Microsoft\Windows\Recent
MSI (c) (EC:7C) [08:43:43:260]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\AppData\Roaming\Microsoft\Windows\SendTo
MSI (c) (EC:7C) [08:43:43:260]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\AppData\Roaming\Microsoft\Windows\Templates
MSI (c) (EC:7C) [08:43:43:260]: SHELL32::SHGetFolderPath returned: C:\ProgramData
MSI (c) (EC:7C) [08:43:43:260]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\AppData\Local
MSI (c) (EC:7C) [08:43:43:260]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\Pictures
MSI (c) (EC:7C) [08:43:43:261]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (c) (EC:7C) [08:43:43:261]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
MSI (c) (EC:7C) [08:43:43:261]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (c) (EC:7C) [08:43:43:261]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
MSI (c) (EC:7C) [08:43:43:261]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
MSI (c) (EC:7C) [08:43:43:262]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (c) (EC:7C) [08:43:43:262]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
MSI (c) (EC:7C) [08:43:43:262]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
MSI (c) (EC:7C) [08:43:43:262]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\AppData\Roaming\Microsoft\Windows\Start Menu
MSI (c) (EC:7C) [08:43:43:263]: SHELL32::SHGetFolderPath returned: C:\Users\Colin\Desktop
MSI (c) (EC:7C) [08:43:43:263]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
MSI (c) (EC:7C) [08:43:43:264]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\Fonts
MSI (c) (EC:7C) [08:43:43:265]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (c) (EC:7C) [08:43:43:274]: MSI_LUA: Setting AdminUser property to 1 because this is the client or the user has already permitted elevation
MSI (c) (EC:7C) [08:43:43:274]: PROPERTY CHANGE: Adding AdminUser property. Its value is '1'.
MSI (c) (EC:7C) [08:43:43:274]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (c) (EC:7C) [08:43:43:274]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (c) (EC:7C) [08:43:43:274]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (c) (EC:7C) [08:43:43:274]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\Source\TestApp\bin\Debug\TestApp.Installer.msi'.
MSI (c) (EC:7C) [08:43:43:274]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'C:\Source\TestApp\bin\Debug\TestApp.Installer.msi'.
MSI (c) (EC:7C) [08:43:43:274]: Machine policy value 'MsiDisableEmbeddedUI' is 0
MSI (c) (EC:7C) [08:43:43:274]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\Source\TestApp\bin\Debug\'.
MSI (c) (EC:7C) [08:43:43:274]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\Source\TestApp\bin\Debug\'.
MSI (c) (EC:A0) [08:43:43:275]: PROPERTY CHANGE: Adding VersionHandler property. Its value is '5.00'.
=== Logging started: 10/12/2018 08:43:43 ===
MSI (c) (EC:7C) [08:43:43:292]: Note: 1: 2205 2: 3: PatchPackage
MSI (c) (EC:7C) [08:43:43:292]: Machine policy value 'DisableRollback' is 0
MSI (c) (EC:7C) [08:43:43:292]: User policy value 'DisableRollback' is 0
MSI (c) (EC:7C) [08:43:43:292]: PROPERTY CHANGE: Adding UILevel property. Its value is '5'.

System Reboot: In this case a simple reboot solved the problem - which is great news.
Speculation: One could speculate as to why, and maybe it had to do with PendingFileRenames (file and folder names waiting to be
changed) or some lock in Windows Updates that affected the System
Restore point creation? Doesn't sound too likely. Just speculation.
A Deployment Mnemonic: To think about this - if you see the problem - a deployment mnemonic: What is locking (in use),
what is blocking (permissions), what is corrupt (disk, malware, configs, encryption), what are unexpected system states
(disk space, time & date settings, language, licensing, windows patch
state, path too long, PendingFileRenames, etc...), what are incompatible products
(things that can't co-exist), what is unreachable or misconfigured (what points to erroneous locations and resources: network server names,
disk paths, URLs, databases, services, UAT environments, PROD environments, etc...) and last but not least: what is missing (runtime, resource image, settings file, etc...)? Launch debugging.
And the older answer. Leaving in to perhaps spark ideas:
Prevalence: Do other MSI files work without issues?
Timeout: How long do you wait for the MSI to initialize?
Initialization & System Restore: The Windows Installer engine may create a system restore point before the GUI is shown. This can be quite slow, and your setup could appear to hang.
Source: Maybe post your whole source.
Logging: Always make a log file for your installation session to debug.
Sounds like you don't need it, but here is a: Sample, minimal MSI compile with WiX Votive.
Gut feel is that there might be an AppSearch in this dialog set that I am unaware of. Maybe try to have a look at the sources yourself first (WixUI_Minimal.wxs et al). Any other issues with your machine? Virtual? Up to date with hotfixes? Malware checked? Disk space? Event logs?

Related

AWS CLI: "Failed to execute script pyi_rth_multiprocessing"

I am receiving this error:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\User>aws configure
.
[1592] Failed to execute script pyi_rth_multiprocessing
C:\Users\User>
What could be the cause?
try contacting AWS, sometimes they can help with this as many people asked them before.

KB-Hotfix installation error in Microsoft Dynamics AX 2012

I am trying to install some KBs on AX but an error is occurring.
I checked the user's privileges and everything is OK
Log:
=== Setup logging started: 06/05/2020 17:56:03 === Running file: "C:\Users\XXX_IN~1\AppData\Local\Temp\AxSetupSP\AxSetupUI.exe"
RelatedFilesDir="C:\Users\xxxxxxxx\Documents\kb" AXSetup version
number: 6.3.6000.6729 Microsoft Windows NT 6.2.9200.0 (64 bit)
VM-SERV-HOMOLOG DOMAIN\xxxxxxxx Interactive: True
RelatedFilesDir=C:\Users\xxxxxxxx\Documents\kb Property
RelatedFilesDir set to: 'C:\Users\xxxxxxxx\Documents\kb' Property
SetupLanguage set to: 'EN'
=== Loading parameters from the command line or a parameter file === Initializing log file: C:\ProgramData\Microsoft\Dynamics AX\Dynamics
AX Setup Logs\2020-05-06 17-56-03\DynamicsSetupLog.txt
=== Starting evaluation of existing installation state === Evaluating installation state of Application Object Server instance 00. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 01. MSI file: ObjectServer64.msi
Installed: True Application Object Server instance 1 has been
installed with the name 01-XXX_AX60_R3_DB_TEST. Evaluating
installation state of Application Object Server instance 02. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 03. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 04. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
05. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 06. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 07. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 08. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
09. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 10. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 11. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 12. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
13. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 14. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 15. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 16. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
17. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 18. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 19. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 20. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
21. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 22. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 23. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 24. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
25. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 26. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 27. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 28. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
29. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 30. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 31. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 32. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
33. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 34. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 35. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 36. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
37. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 38. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 39. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 40. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
41. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 42. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 43. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 44. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
45. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 46. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 47. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 48. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
49. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 50. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 51. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 52. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
53. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 54. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 55. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 56. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
57. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 58. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 59. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 60. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
61. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 62. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 63. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 64. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
65. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 66. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 67. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 68. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
69. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 70. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 71. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 72. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
73. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 74. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 75. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 76. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
77. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 78. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 79. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 80. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
81. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 82. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 83. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 84. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
85. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 86. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 87. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 88. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
89. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 90. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 91. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 92. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
93. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 94. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 95. MSI file: ObjectServer64.msi
Installed: False Evaluating installation state of Application Object
Server instance 96. MSI file: ObjectServer64.msi Installed: False
Evaluating installation state of Application Object Server instance
97. MSI file: ObjectServer64.msi Installed: False Evaluating installation state of Application Object Server instance 98. MSI file:
ObjectServer64.msi Installed: False Evaluating installation state of
Application Object Server instance 99. MSI file: ObjectServer64.msi
Installed: False MSI file: ClientOba64.msi Installed: True MSI file:
Components64.msi Installed: True MSI file: HelpServer64.msi Installed:
False MSI file: SetupSupport64.msi Installed: True MSI file:
TraceParser.msi Installed: False MSI file: MRClient64.msi Installed:
False MSI file: MRServer64.msi Installed: False MSI file:
USPayroll64.msi Installed: True MSI file: USPayroll32.msi Installed:
True MSI file: RapidStartConnectorService.msi Installed: False MSI
file: RetailHeadquarters64.msi Installed: True MSI file:
RetailChannelDatabase.msi Installed: True MSI file:
RetailHardwareStation.msi Installed: False Check if current operating
system version is Windows 10 or higher. Yes
MSI file: RetailModernPOS.msi Installed: False MSI file:
RetailScaleOutDeployment.msi Installed: False MSI file: RetailSDK.msi
Installed: False MSI file: RetailServer.msi Installed: False MSI file:
RetailPOS.msi Installed: True MSI file: RetailPOSPlugins.msi
Installed: False MSI file: RetailSaltUtility64.msi Installed: True MSI
file: CommerceDataExchangeSynchService64.msi Installed: False MSI
file: RetailDatabaseUtility.msi Installed: True MSI file:
CommerceDataExchangeReal-timeService.msi Installed: True MSI file:
CommerceDataExchangeAsyncClient.msi Installed: True MSI file:
CommerceDataExchangeAsyncServer.msi Installed: True MSI file:
RetailOnlineChannel.msi Installed: False MSI file:
CommerceRuntimeSDK.msi Installed: False MSI file: VSTools64.msi
Installed: False Previously Installed Component: Application Object
Server (AOS) (01-XXX_AX60_R3_DB_TEST) Previously Installed Component:
Client Previously Installed Component: Office add-ins Previously
Installed Component: Web services on IIS Previously Installed
Component: .NET Business Connector Previously Installed Component:
Debugger Previously Installed Component: Reporting Services extensions
AxUtil call is complete. Getting known model databases from AOS
configuration. Verifying if the model database
"XXX_AX60_R3_DB_TEST_model" on server "SERVER-HOMOLOG" can be updated.
Using AXUtil to connect to database "XXX_AX60_R3_DB_TEST_model" on
server "SERVER-HOMOLOG". Calling AxUtil to get list of installed
models. Using AXUtil to connect to database
"XXX_AX60_R3_DB_TEST_model" on server "SERVER-HOMOLOG". AxUtil call is
complete. Installed models:
Layer: "Sys", name: "Foundation Upgrade", publisher "Microsoft Corporation", version "6.3.164.0", partition "N/A" Layer:
"Sys", name: "Foundation", publisher "Microsoft Corporation", version
"6.3.164.0", partition "N/A" Layer: "Sys", name: "Foundation Labels",
publisher "Microsoft Corporation", version "6.3.164.0", partition
"N/A" Layer: "Syp", name: "Hotfix-KB2964763-CL4307967-Foundation",
publisher "Microsoft Corporation", version "6.3.164.755", partition
"Foundation"
->> Listed here all installed KBs .....
Layer: "Syp", name: "Hotfix-KB4552332-4582330-Foundation", publisher
"Microsoft Corporation", version "6.3.6000.9892", partition
"Foundation" Layer: "Syp", name:
"Hotfix-KB4552334-4582327-Foundation", publisher "Microsoft
Corporation", version "6.3.6000.9887", partition "Foundation" Layer:
"Syp", name: "Hotfix-KB4552480-4582328-Foundation", publisher
"Microsoft Corporation", version "6.3.6000.9888", partition "Foundation"
Found update model(File:
C:\Users\xxxxxxxx\Documents\kb\Models\dynamicsax2012r3-kb4531474-syplabels.axmodel,
Layer: Syp, Name: SYP Labels, Version: 6.3.6000.9964, Partition:
SYP-Labels) Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Found update model(File:
C:\Users\xxxxxxxx\Documents\kb\Models\dynamicsax2012r3_cl4582181.axmodel,
Layer: Syp, Name: Hotfix-KB4531583-4582181-Foundation, Version:
6.3.6000.9517, Partition: Foundation) Found update model(File: C:\Users\xxxxxxxx\Documents\kb\Models\dynamicsax2012r3_cl4582362.axmodel,
Layer: Syp, Name: Hotfix-KB4531474-4582362-Foundation, Version:
6.3.6000.9964, Partition: Foundation) Evaluating applicability requirements for model file:
C:\Users\xxxxxxxx\Documents\kb\Models\dynamicsax2012r3-kb4531474-syplabels.axmodel
Required model (Layer: SYS, Name: Foundation, Version: 6.3.164.0) is
installed: True Update model file is installed: False Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available.
=== Checking parameters === Property InstallPath set to: 'C:\Program Files\Microsoft Dynamics AX\60' Property InstallPath32Bit set to:
'C:\Program Files (x86)\Microsoft Dynamics AX\60'
=== Starting UI phase === MSI file: DIXF_Service64.msi Installed: False MSI file: DIXF_AOS64.msi Installed: False MSI file:
DIXF_Client64.msi Installed: False Msi
C:\Users\xxxxxxxx\Documents\kb\MSI\VSTools64\VSTools64.msi Found False
Property ModelDatabaseInstanceName set to:
'SERVER-HOMOLOG:XXX_AX60_R3_DB_TEST_model' Property
InstallModelDatabase set to: '1' Property ModelDatabaseInstanceName
set to: 'SERVER-HOMOLOG:XXX_AX60_R3_DB_TEST_model' Property
InstallModelDatabase set to: '1' Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Model store state cannot be verified.
Getting schema build version for database XXX_AX60_R3_DB_TEST_model on
server SERVER-HOMOLOG Obtained schema build version string
"6.3.6000.9100" Getting contents of model file
C:\Users\xxxxxxxx\Documents\kb\Models\dynamicsax2012r3-kb4531474-syplabels.axmodel
AxUtil call is complete. Getting contents of model file
C:\Users\xxxxxxxx\Documents\kb\Models\dynamicsax2012r3_cl4582181.axmodel
AxUtil call is complete. Getting contents of model file
C:\Users\xxxxxxxx\Documents\kb\Models\dynamicsax2012r3_cl4582362.axmodel
AxUtil call is complete. Examining customized elements. Using AXUtil
to connect to database "XXX_AX60_R3_DB_TEST_model" on server
"SERVER-HOMOLOG". Getting contents of model VAR Model AxUtil call is
complete. Getting contents of model XXX Shared Objects AxUtil call is
complete. Getting contents of model Common Interface Application
AxUtil call is complete. Getting contents of model MMT AxUtil call is
complete. Getting contents of model ToolCommon (Conflict 1) AxUtil
call is complete. Getting contents of model ToolCommon (Conflict 2)
AxUtil call is complete. Getting contents of model VAP Model AxUtil
call is complete. Getting contents of model USR Model AxUtil call is
complete. Getting contents of model SecurityDevelopmentTool AxUtil
call is complete. Starting to calculate potential conflicts. Finished
calculating potential conflicts.
KB4531474: Allocated Charges amounts and FA transactions incorrectly
posted when we maintain Charges before PO Confirmation – PO line is a
Procurement category KB4531583: Updated depreciation calculation when
posting reduction entry with Direct-off type Property AosStart set to:
'0' Property InstallOtherModelDatabase set to: '1' Property
InstallModelDatabase set to: '1'
=== Setting up Model Database === Updating model database "XXX_AX60_R3_DB_TEST_model" on server "SERVER-HOMOLOG". Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Update model details metadata not available. Update model
details metadata not available. Update model details metadata not
available. Following files will be imported as part of this update:
C:\Users\xxxxxxxx\Documents\kb\Models\dynamicsax2012r3-kb4531474-syplabels.axmodel,
C:\Users\xxxxxxxx\Documents\kb\Models\dynamicsax2012r3_cl4582181.axmodel,
C:\Users\xxxxxxxx\Documents\kb\Models\dynamicsax2012r3_cl4582362.axmodel.
Using AXUtil to connect to database "XXX_AX60_R3_DB_TEST_model" on
server "SERVER-HOMOLOG". Calling AxUtil to import model file
"C:\USERS\xxxxxxxx\DOCUMENTS\kb\MODELS\DYNAMICSAX2012R3_CL4582181.AXMODEL".
AxUtil call is complete. AxUtil call returned errors: You cannot
import the Foundation (KB4531583) model into a Microsoft layer. Error
updating model database: Microsoft.Dynamics.Setup.AxSetupException:
AxUtil call returned errors:You cannot import the Foundation
(KB4531583) model into a Microsoft layer.
at Microsoft.Dynamics.Setup.Misc.ValidateAxUtilStatus(AxUtilContext
context) at
Microsoft.Dynamics.Setup.DatabaseSqlModel.DatabaseSqlModelInstanceCommon.ImportModelFiles(IEnumerable1 filenames, IEnumerable1 modelsToReplace) at
Microsoft.Dynamics.Setup.DatabaseSqlModel.DatabaseSqlModelInstanceUpdate.Execute()
An error occurred during setup of Model Database
(SERVER-HOMOLOG:XXX_AX60_R3_DB_TEST_model). Completed setup of Model
Database.
=== Setup was completed successfully.
=== Setup logging ended: 06/05/2020 17:58:37 ErrorLevel/ExitCode: '0' ===
Info:
Microsoft Dynamics AX 2012 R3
Edit 1:
I'm using axupdate (Application) .exe unzipped from the KB.
I check and the KB is part of the system. See the image below.
Edit 2:
I am trying to install all the latest KBs that were released as of 4/10/2020 by Microsoft.
I have a list for installation. From this list most KBs have the errors mentioned in the log above. However, I was successful in installing the latest 7 KB and 3 Hotifix kernel.
I don't understand how it was possible to install some KBs and others have errors.
Well ..
I identified that the .axmodel certificate had expired.
In this case the problem is in the publication of KBs released by Microsoft.
Thank you all for your help
Just to let you know - in case you don't already - Microsoft are now aware of the situation and are working on rereleasing all AX 2012 R3 KB's with a new certificate. They expect to have the first ones ready by Monday 18-05, is what I was told by a guy from Microsoft.
I recently tried to install KB 4602212 (2020 1099 fix) released 1/2021. The AX DEV environment was on 6.3.4000.2085 AX kernel. I ran into this error trying to install the HF. It was not an option to apply a newer AX kernel to their DEV environment since SQL server (AX SSRS components) was shared by DEV, TEST & UAT. The workaround was to copy AXUtillib.dll & AXutilLib.PowerShell.dll from an environment with newer kernel (6.3.6000.9100) from the C:\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\bin or the C:\Program Files\Microsoft Dynamics AX\60\ManagementUtilities folder and replacing these files in the AX DEV environment.
I ran into the same problem while installing KB3210144. For what it's worth, for AX R3 I have been directed by MS Support to download the AX Update installer from LCS. Inside your LCS Project (create a dummy project if you don't have any) scroll right to Project Tools / Updates
Where you can download the "Update installer for Microsoft Dynamics AX 2012 R3".
Unfortunately in my case, the tool found I already have the fix installed.

enabling opcache on mac catalina, php 7.4 installed with homebrew

I've modified the php.ini file to enable opcode caching and restarted apache but it is nowhere in sight with phpinfo(). php -v says:
PHP 7.4.1 (cli) (built: Dec 18 2019 14:46:18) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
Most other examples I see form this command say something like "with Zend Opcache".
No other .ini files except the one at /usr/local/etc/php/7.4/php.ini are being used, according to php.
I tried installing zend opcache with pecl but that says it's for versions 5.2.0 thru 5.5.0.
Searched through google for 30 min. but not getting anywhere.
OK, got it. Searched for the opcache.so file in Finder and added it's path to php.ini:
zend_extension=/usr/local/Cellar/php/7.4.1/lib/php/20190902/opcache.so

Build sqlproj on Azure DevOps

I'm trying to use Azure DevOps Pipelines to build my .NET Core 2.1 solution from GitHub. It includes a SQL project that has a TargetFrameworkVersion of v4.6.2. This project always fails to build.
Build FAILED.
/home/vsts/work/1/s/MySolution/MyDatabase/MyDatabase.sqlproj : warning NU1503: Skipping restore for project '/home/vsts/work/1/s/MySolution/MyDatabase/MyDatabase.sqlproj'. The project file may be invalid or missing targets required for restore. [/home/vsts/work/1/s/MySolution/MySolution.sln]
/home/vsts/work/1/s/MySolution/MyDatabase/MyDatabase.sqlproj(57,3): error MSB4019: The imported project "/usr/share/dotnet/sdk/2.1.403/Microsoft/VisualStudio/v15.0/SSDT/Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
1 Warning(s)
1 Error(s)
How do I reference or include those targets for the build server? It builds fine in VS2017. I've spent more than a day hunting and cannot find any information on this problem.
Thanks to Herman Cordes for directing my investigation.
The problem was the selected build server. SSDT is a Windows-only package, so I had to use a Windows VM instead of the default Ubuntu VM, and use the VSBuild#1 task instead of DotNetCoreCLI#2.
azure-pipelines.yml
pool:
vmImage: 'vs2017-win2016'
steps:
- task: VSBuild#1
displayName: 'vsbuild $(buildConfiguration)'
inputs:
configuration: $(buildConfiguration)
EDIT: The MSBuild#1 task also works.
Here is a solution for linux build agent
Easiest way to build DacPac file on a linux agent is done via MSBuild.Sdk.SqlProj
Go to your database project directory in parallel to .sqlproj file create a directory like DB.Build under it create DB.Build.csproj copy.pase the content as below
<Project Sdk="MSBuild.Sdk.SqlProj/1.1.0"> <!-- This will pull in the required tools and dependencies to build a .dacpac with .NET Core -->
<PropertyGroup>
<TargetFramework>netstandard2.0</TargetFramework>
</PropertyGroup>
<ItemGroup>
<Content Include="..\src\DB\masterdata\**\*.sql" /> <!-- link in the new .csproj to the .sql scripts in your existing database project -->
</ItemGroup>
</Project>
After run you will see dacpac file appears under DB.Build/bin/Release/netstandard2.0/DB.Build.dacpac
Here's my build agent output (Ubuntu agent on Azure devops)
Starting: SQL DB build Release
==============================================================================
Task : .NET Core
Description : Build, test, package, or publish a dotnet application, or run a custom dotnet command
Version : 2.187.0
Author : Microsoft Corporation
Help : https://learn.microsoft.com/azure/devops/pipelines/tasks/build/dotnet-core-cli
==============================================================================
Info: .NET Core SDK/runtime 2.2 and 3.0 are now End of Life(EOL) and have been removed from all hosted agents. If you're using these SDK/runtimes on hosted agents, kindly upgrade to newer versions which are not EOL, or else use UseDotNet task to install the required version.
/opt/hostedtoolcache/dotnet/dotnet build /home/vsts/work/1/s/src/RecommenderAPI.DB/RecommenderAPI.DB/RecommenderAPI.DB.Build/RecommenderAPI.DB.Build.csproj -dl:CentralLogger,"/home/vsts/work/_tasks/DotNetCoreCLI_5541a522-603c-47ad-91fc-a4b1d163081b/2.187.0/dotnet-build-helpers/Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll"*ForwardingLogger,"/home/vsts/work/_tasks/DotNetCoreCLI_5541a522-603c-47ad-91fc-a4b1d163081b/2.187.0/dotnet-build-helpers/Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll" --configuration Release /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:PackageLocation=/home/vsts/work/1/recommender-service-cicd/DacPac/
Microsoft (R) Build Engine version 16.5.0+d4cbfca49 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.
Restore completed in 51.72 ms for /home/vsts/work/1/s/src/RecommenderAPI.DB/RecommenderAPI.DB/RecommenderAPI.DB.Build/RecommenderAPI.DB.Build.csproj.
Using package name RecommenderAPI.DB.Build and version 1.0.0
Using SQL Server version Sql150
Deleting existing file /home/vsts/work/1/s/src/RecommenderAPI.DB/RecommenderAPI.DB/RecommenderAPI.DB.Build/obj/Release/netstandard2.0/RecommenderAPI.DB.Build.dacpac
Writing model to /home/vsts/work/1/s/src/RecommenderAPI.DB/RecommenderAPI.DB/RecommenderAPI.DB.Build/obj/Release/netstandard2.0/RecommenderAPI.DB.Build.dacpac
RecommenderAPI.DB.Build -> /home/vsts/work/1/s/src/RecommenderAPI.DB/RecommenderAPI.DB/RecommenderAPI.DB.Build/bin/Release/netstandard2.0/RecommenderAPI.DB.Build.dacpac
Build succeeded.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:01.71
Finishing: SQL DB build Release
Note: Make sure to restore you NuGet packages in step prior to build
Your ADO pipeline manifest should look like this:
...
- task: DotNetCoreCLI#2
displayName: 'Restore SQL Project'
inputs:
command: 'restore'
projects: '**/*DB*/*.csproj'
feedsToUse: 'select'
vstsFeed: 'db-feed'
...
- task: DotNetCoreCLI#2
displayName: 'SQL DB build $(buildConfiguration)'
inputs:
command: build
projects: '**/*DB*/*.csproj'
platform: '$(buildPlatform)'
arguments: '--configuration $(buildConfiguration) /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:PackageLocation=$(Pipeline.Workspace)/$(pipelineArtifactName)/DacPac/'
I was having the exact same issue building a SQL Server project on an Azure DevOps CI/CD pipeline. None of the pre-built build tasks would work for me!
I solved this by avoiding to add a SQL Server project to the solution.
I achieved this by using an MSBuild SDK, capable of producing a SQL Server Data-Tier Application package (.dacpac) from the set of SQL scripts. By adding this second project to the solution, I managed to continue taking advantage of linking the project to a live database through SQL Server Object Explorer on Visual Studio. I gave a more detailed explanation about my implementation in this answer.

deploy dotnet core cli mvc application to azure webservice

I want to deploy my .NET Core MVC application in an azure WebService. I have built the app locally with
dotnet publish
and moved the output code with the Kudu service in my wwwroot directory but the wabapp just gives me the errorpage:
deploy .NET Core CLI MVC application to azure web service
What am I doing wrong?
I tried with a sample project:
D:\dotnetDummy>dotnet publish
Microsoft (R) Build Engine version 15.3.409.57025 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.
dotnetDummy -> D:\dotnetDummy\bin\Debug\netcoreapp2.0\dotnetDummy.dll
dotnetDummy -> D:\dotnetDummy\bin\Debug\netcoreapp2.0\publish\ <-- output directory
after publishing locally, you want to move all files under output directory to wwwroot folder of your azure webapp, in this case your D:\home\site\wwwroot on Kudu site should look the same as D:\dotnetDummy\bin\Debug\netcoreapp2.0\publish
D:\dotnetDummy\bin\Debug\netcoreapp2.0\publish>dir /B
dotnetDummy.deps.json
dotnetDummy.dll
dotnetDummy.pdb
dotnetDummy.PrecompiledViews.dll
dotnetDummy.PrecompiledViews.pdb
dotnetDummy.runtimeconfig.json
web.config <-- output of dotnet publish
if you don't see web.config under wwwroot, I would guess there's a mistake during the move