Installing upgrade package does nothing?

[RichStephens]

Using one of the new 10.0.39 local VMs downloaded from LCS. I'm trying to upgrade it to 10.0.40. I download the upgrade package, unzip it (making sure it's not locked) and run the Invoke-D365SDPInstall command using the -QuickInstallAll option.

The command runs, but the upgrade doesn't run. I just get an error log like this:

========= Beginning trace at: 2024-07-03T14:00:49.1705920Z =========
--- Installer Version: 7.0.7279.40
--- Runbook ID:
--- Mode: QUICKINSTALLALL

[14:00:49.2498] Generating runbook with the following parameters:
[14:00:49.2498] RunbookId: Runbook20240703100049
[14:00:49.2498] UpdatePackagePath: C:\Temp\40Update
[14:00:49.2498] GenerateBackupSteps: True
[14:00:49.2498] GenerateDVTSteps: True
[14:00:49.2498] GenerateETWSteps: True
[14:00:49.2498]
[14:00:49.2656] Exception[196610] found.
[14:00:49.2656] Runbook doesn't contain any steps to execute
[14:00:49.2656] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.RunbookData.Validate()
[14:00:49.2656] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AXUpdateInstallerBase.GenerateQuickInstallRunbook(IRunbookGenerator runbookGenerator, RunbookGeneratorParameter parameter)
[14:00:49.2656] at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AXUpdateInstallerBase.Install(String updatePackageFilePath, Boolean versionCheck, String serviceModelFile, Boolean parallel, Boolean devInstall, Parameters parameters)
[14:00:49.2656] at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.InstallUpdate(String[] args)
[14:00:49.2656] at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.Main(String[] args)
[14:00:49.2656] Exiting with exit code [196610]
=========== Ending trace at: 2024-07-03T14:00:49.2656151Z ==========

I've never had this happen before. The upgrade packages usually run smoothly from this command. It's like there's some step missing in the process? What am I missing?

[Splaxi]

Knowing that 10.0.40 is a special case, as they are changing things with the nugets.

Could you try the pure installation, by following the instructions directly from Microsoft? This will help is understand whether the instructions we are sending or the 10.0.40 package might be corrupt.

[RichStephens]

Knowing that 10.0.40 is a special case, as they are changing things with the nugets.

Could you try the pure installation, by following the instructions directly from Microsoft? This will help is understand whether the instructions we are sending or the 10.0.40 package might be corrupt.

I attempted to run the update manually using the instructions found here: https://alexdmeyer.com/2020/11/25/how-to-fix-the-devinstall-option-is-not-applicable-to-the-current-deployable-package-error/

However, when I did (note that I am running a command prompt as Administrator), I got the following errors:

C:\Temp\40Update>AXUpdateInstaller.exe generate -runbookid="OneBoxDev" -topologyfile="C:\Temp\40Update\DefaultTopologyData.xml" servicemodelfile="C:\Temp\40Update\DefaultServiceModelData.xml" -runbookfile="C:\Temp\40Update\OneBoxDev-runbook.xml"
Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet)
at System.Security.CodeAccessPermission.Demand()
at System.Security.Permissions.FileIOPermission.QuickDemand(FileIOPermissionAccess access, AccessControlActions control, String[] fullPathList, Boolean checkForDuplicates, Boolean needFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
at System.Xml.XmlDownloadManager.GetStream(Uri uri, ICredentials credentials, IWebProxy proxy, RequestCachePolicy cachePolicy)
at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)
at System.Xml.XmlSecureResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)
at System.Xml.XmlTextReaderImpl.FinishInitUriString()
at System.Xml.XmlReaderSettings.CreateReader(String inputUri, XmlParserContext inputContext)
at Microsoft.Dynamics.AX.AXUpdateInstallerBase.TopologyData.InitFromFile(String filePath)
at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AXUpdateInstallerBase.Generate(String runbookID, String topologyFilePath, String serviceModelFilePath, String runbookFilePath, String updatePackageFilePath, Boolean generateDVTStep)
at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.InstallUpdate(String[] args)
at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.Main(String[] args)

Don't know what this means. I can't imagine what permissions I might be missing when running the command as Administrator?

[FH-Inway]

Since the last call from AXUpdateInstallerBase in the call stack is at Microsoft.Dynamics.AX.AXUpdateInstallerBase.TopologyData.InitFromFile(String filePath) and the rest seems to be standard .NET stuff, I think this is another issue where it cannot access the topology file. Maybe it was open in another program that blocked access to it? Or the zip file was not unblocked prior to unpacking it?

[RichStephens]

The zip file was unblocked. I don't believe I had the file or folder open anywhere else.

[FH-Inway]

I encountered this issue as well, see https://www.yammer.com/dynamicsaxfeedbackprograms/#/Threads/show?threadId=2807181274095616

The issue is most likely not with d365fo.tools, but the AxUpdateInstaller.exe or (more likely) the setup of the VHD.

To quote from the link:

The issue is that AXUpdateInstaller.exe list command does not do anything. Not even a log file is generated and at first glance, I could not find anything in the Windows event logs.
As a workaround, I copied the DefaultTopologyData.xml file from another VHD environment based on 10.0.37 version were I installed 10.0.40 preview successfully in the past (there, the list command works). With that copy, I was able to successfully install the 10.0.40 upgrade on the 10.0.39 VHD.
I got a weird timeout error regarding a log file access during the step of the management reporter upgrade. After restarting the environment and rerunning the step, the issue did not occur again.
I also set the ServiceDrive environment variable when trying to get the list command to work. Not sure if that is required for the rest of the upgrade to work or not.

Invoke-D365SDPInstall uses the internal Update-TopologyFile function to create the topology file. This surprised me, I thought it would also use the AxUpdateInstaller.exe list command. But since both fail, I guess both have the same root cause.

d365fo.tools/d365fo.tools/functions/invoke-d365sdpinstall.ps1

Lines 222 to 223 in 72bd033

	#Update topology file (first command)
	$ok = Update-TopologyFile -Path $Path

I will do some more digging, but a workaround could be that we add a known good topology file to d365fo.tools. This topology file can then be used as a fallback in case Update-TopologyFile cannot create/update one.
We should also add some kind of warning to the users in case Update-TopologyFile cannot identify any installed service models.

[FH-Inway]

Here is what digging brought up so far:

• AXUpdateInstaller.exe list and Update-TopologyFile both use the Microsoft.Dynamics.AX.AXInstallationInfo.dll assembly that is included in the package.
• That assembly uses the files in the C:\Logs\InstallationRecords\ServiceModelInstallationRecords folder to determine the service models that need to be added to the topology file. That folder does not exist on the 10.0.39 VHD.

So there currently does not seem to be a way to install an update on a fresh 10.0.39 VHD without some additional steps/workaround.
My suggested workaround is:

• Replace the DefaultTopologyData.xml file with a file from another VHD. If you do not have one, you can try using https://gist.github.com/FH-Inway/d0bfdac84620cf5f3d2a2f96a9226ad7. Note that you may have to change the value of the <Name> tag under the <Machine> tag to match the name of your vm.
• Run the following commands:

$Path = Read-Host "Enter the path where the package was unpacked to"
$RunbookId = Read-Host "Enter a runbook id"
Invoke-D365SDPInstall -Path $Path -Command Generate -RunbookId $RunbookId
Invoke-D365SDPInstall -Path $Path -Command Import -RunbookId $RunbookId
Invoke-D365SDPInstall -Path $Path -Command Execute -RunbookId $RunbookId

[FH-Inway]

PR #844 with some changes to make the workaround easier/obsolete.

[RichStephens]

Those instructions appear to be working. Thanks gents!

[FH-Inway]

Version 0.7.15 contains the change from #844. Invoke-D365SDPInstall can now be used as usual on the 10.0.40 VHD.

[fhoo]

Just to clarify the "as usual" statement: the fix is working nice with the -Command RunAll parameter. -QuickInstallAll still fails as this is just forwarding this option to AXUpdateInstaller without handling the topology issue.