Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
This post originally appeared on https://dynamicsnotes.com/failing-dynamics-365-fo-deployments-last-resort-workarounds/.
There are times when a deployment fails and even a re-try does not help. In these cases, a service ticket should be opened to the Microsoft engineers.
However, there are cases when this is not feasible or helpful. For example:
In these and other cases, it may be OK to just step over the failing step and let the deployment finish (in non-production environments).
The following steps can be used to workaround. Again, this is almost “hack” territory, but sometimes is needed…
Note, sometimes I have found that marking this step is not enough. If that is the case, you can also edit the PowerShell file that the step calls into and essentially comment out all the code. The PowerShell file will be in the service directory under AOSService\DeployablePackages.
Again, this is a hack, but sometimes desperate times call for desperate measures.
Business Applications communities