Liquid error: Value cannot be null.
Parameter name: key
Liquid error: Value cannot be null.
Parameter name: key
Community member
Comments
-
@Shahrukh please get a new VM. There is a lot more on these VMs than just F&O. Unless you're making inventory on everything that is installed on the VM and making sure to keep it updated, you're likely missing updates to a lot of things. Getting a new VM takes care of all of these things, making sure you're compliant and secure.
-
Hi Joris dG, We are currently on PU32 and upgrading our local VHD to PU42. I know this is a good idea to download the new VHD. But can you please tell me if we install .NET 4.7.2 and then VS17 and its required components manually. Will it work? And will this be a successful upgrade? Or there is only option available to download the new VHD?
-
-
@Wim although we are rolling out .NET updates to other topologies, the dependency on this version comes from our Visual Studio tools. Since those are only present on Tier1, this requirement is only for Tier1.
-
Is the .NET framework 4.7.2 also needed on AOS servers/orchestrator servers/Reporting servers/... in a TIER2 on-premise environment? Or is is only needed in a DEV VM (related to the new Visual Studio Tools). Thanks in advance!
-
daxture.blogspot.com/.../d365fo-update-to-pu36-10012-and.html has been updated to reflect the correct solution of the issue you may experience after updating VM to 10.0.12. As Joris mentioned that error message is FO related and is not related to .Net version.
-
@Artem you may be mixing issues. If you don't have .NET 4.7.2 - then the PU37 update cannot install at all, it will fail. Any errors inside F&O would be unrelated.
-
We have .NET 4.7.2 installed, still getting this issue: daxture.blogspot.com/.../d365fo-update-to-pu36-10012-and.html Running newly deployed VM on Update36.
-
-
*This post is locked for comments