Topology file management

[MatthieuHz]

Hi everyone,

I'm trying to understand how those Service Models are managed :

With #878 issue fix, it shouldn't be a problem anymore but when I execute Invoke-D365SDPInstall -Path $(UnZipPath) -Command RunAll -verbose, this DefaultTopologyData.xml file is generated :

And this error occurred :

Whereas I don't have Retail elements anymore in IIS :

Thank you ! :)

[FH-Inway]

Hey, thanks for reporting. Can you share more information about the environment where this is done? If it is a local VHD environment, what vhd image version was used to set it up? If it is a cloud hosted environment, when was it deployed and with what version? Were updates installed on the environment before?

From what I see in the posted logs, the change from #878 is unrelated. Otherwise, there would have been messages in the log about using a fallback. This seems to be an issue where the Microsoft standard update logic does not correctly identify the installed components.

[Microsoft.Dynamics.AX.AXInstallationInfo.AXInstallationInfo]::GetInstalledServiceModel() determines the installed components by looking at the files in the C:\Logs\InstallationRecords\ServiceModelInstallationRecords folder. See #843 (reply in thread) (this was in July last year - Microsoft may have changed the update logic since then).
This is also used by the AXUpdateInstaller.exe list command . You can use that to check what the Microsoft update functionality thinks is installed on the environment.

As a workaround, you can edit the topology file to remove the retail components. Then run Invoke-D365SDPInstall with the -TopologyFile parameter and the path to the modified file along with the -UseExistingTopologyFile switch to tell the command to not change the topology file anymore.
See example 8 of the Invoke-D365SDPInstall documentation.

[MatthieuHz]

Hi @FH-Inway !

Thank you for your quick answer 😉

Sorry for the lack of informations, it's on a VHD, yes. It was on the 10.0.41 VHD version.

On one side, during a 10.0.42 SPD, I faced this issue but you were saying on Yammer that it was related to another problem : https://www.yammer.com/dynamicsaxfeedbackprograms/#/Threads/show?threadId=3172972962234368

My second test was on 10.0.41 VHD with 10.0.43 SDP, I believed that it was fix for this 10.0.43 update.

Here is my logs folder on my 10.0.43 updated VHD :

Here is the AXUpdateInstaller.exe list :

Maybe I didn't understand well but I thought Retail components have been removed since 10.0.41 VHD.

I don't want to manage a TopologyFile because I just need to ignore Retail elements but, yes, it's working (maybe I didn't update enough components). Here is the TopologyFile I used for 10.0.43 SDP :

<?xml version="1.0" encoding="utf-8"?>
<!-- 
  To populate topology data for command line package installation, refer to:
    https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/install-deployable-package#collect-topology-configuration-data
-->
<TopologyData xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Name>AX topology</Name>
  <MachineList>
    <Machine>
      <Name>localhost</Name>
      <ServiceModelList>
        <string>AOSService</string>
        <string>DevToolsService</string>
      </ServiceModelList>
    </Machine>
  </MachineList>
  <BackupScript>
    <FileName />
    <Automated>false</Automated>
    <Description>Please backup your environment now, set this step to complete once you finished backup</Description>
  </BackupScript>
</TopologyData>

I'm a bit confused. I'll try to delete files in C:\Logs\InstallationRecords\ServiceModelInstallationRecords, update again without TopologyFile and come back to you.

Thank @FH-Inway !

[MatthieuHz]

That's it ! We need to delete those files to avoid TopologyFile management 😉

Maybe it's fixed in 10.0.43 VHD, I won't be able to check this in the next few weeks

Thank you @FH-Inway !

[FH-Inway]

Glad it worked out for you.

Yeah, ever since the 10.0.39 VHD, updates have gotten messy. You are right, starting with the 10.0.41 VHD, the Retail components have been removed. I'm not sure why they are discovered on your environment. One guess is that I think there were several versions of the 10.0.41 VHD (but my memory may be wrong here). Maybe you got an earlier version where the components were not removed yet? The other guess I have is that the failing 10.0.42 upgrade may have somehow (maybe with an older d365fo.tools version that did not have the fixed fallback?) installed the Retail components insofar as to make them discoverable by the AXUpdateInstaller.exe list logic? Not sure how that would work.

Not directly related to your issue, but since it got me thinking, here is a timeline as I understand it regarding the update issues in general:

• Microsoft releases the 10.0.39 VHD
  • it is discovered that the InstallationRecords folder content is missing there, which prevents the update process as we knew it so far
  • improves topology file handling for Invoke-D365SDPInstall and fixes issue on 10.0.39 VHD #844 is implemented to handle this case with a fallback topology file
• Microsoft releases the 10.0.41 VHD
  • the InstallationRecords folder content is still missing; in addition, the Retail components were removed - this causes the update with the fallback topology file to fail
  • Separate out retail components from fallback service models #880 is implemented to handle this case with a fallback topology file that does not include the Retail components
• Microsoft releases the 10.0.43 VHD
  • the InstallationRecords folder content exists again, but the file for the AOSService component (which is responsible for the update of the application modules) is missing
  • I'm waiting on feedback from Microsoft if they will fix it. If not, I consider adding yet another workaround in d365fo.tools to account for that. See https://www.yammer.com/dynamicsaxfeedbackprograms/threads/3262996664000512 Until then, the workaround is to manually add the component to the topology file. Or use DefaultTopologyDataWithoutRetail.xml

@Splaxi fyi

[FH-Inway]

Since no feedback way provided by Microsoft on the 10.0.43 VHD issue with the missing AOSService component and the next update 10.0.44 will soon be relased, I created #887 to address this issue.

https://knowyourmeme.com/memes/ok-now-press-space-to-jump