Views:

Applies to Product – Dynamics 365 Lifecycle Services


What’s happening?
The customer is unable to retain the virtual machine (VM) for build processes, and the Presto extensions are reported as disabled, impacting their workflow.
 

Reason:
The underlying cause of this is related to the VM not being retained post-build, which leads to the disabling of the Presto extensions.
 

Resolution:

  1. Perform a database refresh to address this with the VM and the disabled Presto extensions.
  2. If the issue persists after the database refresh, consider scheduling a remote session to investigate the VM setup and check the configurations related to the Presto extensions.
  3. During the remote session, verify the status of the VM extensions and review any error messages for clues about the failure reason.
  4. If necessary, remove and reinstall the extensions to resolve any issues related to their functionality.