Has anyone else experienced an issue with upgrading a local D365 F&O OneBox development environment from v10.0.13 (PU37) to v10.0.15 (PU39)? Specifically, in my situation everything updated as expected except for these 2 components:
- BIService
- RetailSelfService
Some background details:
I spun up a fresh D365 F&O developer OneBox using the v10.0.13 (PU37) downloadable VHD from LCS. After doing some minor testing and configuration (to verify that it was working properly), I upgraded the OneBox to v10.0.15 (PU39) using the software deployable package from LCS. I did not add any custom code to the OneBox before doing the update. It was a "plain vanilla" deployment with the out-of-the-box functionality and demo data included in the OneBox.
During the v10.0.15 update, I encountered 3 well known errors (i.e. other D365 F&O developers already posted solutions for these issues). Those errors halted the execution of the runbook, but I was able to resolve those issues using the blog posts that I found. In each case, I was able to restart the runbook execution and pick up where it left off. And eventually it completed all steps successfully.
However, BIService and RetailSelfService are still showing the old version numbers from v10.0.13. All other components show their new version numbers associated with v10.0.15.
I checked the logs, and I didn't find any obvious signs of failure. In particular, the UpdateRetailSelfService.log seems to indicate a successful update.
The BIService update was a bit more puzzling. I included it in the DefaultTopologyData.xml file when generating and importing the runbook.
But strangely, I don't recall seeing any execution steps to process the BIService update. But there are definitely files available in the installation folder related to BIService:
Can anyone suggest how to get BIService and RetailSelfService components to upgrade to their new versions for v10.0.15 (PU39)? As I mentioned, I haven't found any obvious error messages in the logs, but maybe I haven't looked in the right place.
