Views:

Applies to Product -Dynamics 365 Lifecycle Services


What’s happening?
Customers may encounter issues related to the upgrade process to version 42, including errors during the application of update packages, as well as requests for early access to first release packages due to delays in general availability.


Reason:

  1. Errors during the upgrade process may occur due to timeouts or issues in specific steps of the update script execution.
  2. Delays in the general availability of software versions can impact testing schedules and lead to requests for early access to first release packages.
     
Resolution:
  1. For Upgrade Issues:
  2. Navigate to the directory of the deployable package.
  3. Backup the script file associated with the update.
  4. Clear the contents of the script file to ensure it is empty.
  5. Verify that the script file is indeed empty.
  6. Resume the deployment operation from Lifecycle Services (LCS).
  7. Confirm that the issue is resolved and proceed with the upgrade.
  8. For First Release Package Requests:
  9. If the general availability of a version is delayed, inform the customer that the first release package may be provided for testing purposes.
  10. Share the SAS token for the first build package if available, allowing the customer to download it for regression testing.
  11. Ensure that the customer understands that the first release build may differ from the final general availability version if any fixes are released before the GA.