web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / Dynamics 365 for Finance and Operations Technic... / Issues after installing bin...

Issues after installing binary updates on local dev machine

Views (3418)
nmaenpaa Profile Picture nmaenpaa 101,160 Moderator

Recently I've seen many people struggling with different issues after updating their local dev machine (VHD) with D365FO binary updates (for example 8.1.3 PU23 or 10.0 PU24). It might be that ISV binaries don't show up in AOT, or code changes don't take effect without building the whole package. Or data management export / import doesn't work.

The reason for these problems has been an incomplete installation of the update package. By default, if you don't change the setup files, installing the deployable package will only update AOSService component on the machine. All other D365FO components including DevTools, DIXFService and many more will stay on the old version. This version mismatch will cause numerous issues.

When you install Microsoft's D365FO update deployable packages manually from command line, you must update the DefaultTopologyData.xml in the package before generating the runbook and running the installation. This is clearly mentioned in the documentation but many people seem to have missed it: https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/deployment/install-deployable-package#collect-topology-configuration-data

It doesn't exactly help that the xml comment in DefaultTopologyData.xml says: 

<!-- DefaultTopologyData are only for dev vhd, which we only support AOS update-->

You should ignore this statement and add all your D365FO components in the file.

If you accidentally updated only AOSService component, the situation can be fixed easily. Just update the DefaultTopologyData.xml file, generate a new runbook and run the update installer with this new runbook.

Comments

*This post is locked for comments

  • Greg's Mom Profile Picture Greg's Mom
    Posted at
    Thank you very much for this. We struggled with an update to our on-prem developer VMs where mostly things were working fine but data management framework was not. We ended up manually copying some DLL files around to resolve the problem but we were not happy with that solution so I'm glad to find this post.
  • Florian Hopfner Profile Picture Florian Hopfner 2,451
    Posted at

    To make the documentation even clearer, you might want to consider updating the part where it says "5. Repeat steps 1 through 4 for every other VM that is listed on the Environment page." Since local dev machines are not listed on the environment page, one could get the impression that the steps for updating the DefaultTopologyData.xml file should not be done for them.