Pre deployment
Upgrade Strategy
We recommend updating of all Eftsure packages regularly, at least as often as Dynamics 365 service upgrades, since new features and fixes are shipped with every new release.
To troubleshoot any issue(s) during deployments, stop the following services which usually have a file lock on D365 files:
- IIS Manager: AOSService application pool ,
- Windows Service: Microsoft Dynamics 365 Unified Operations: Batch Management Service.
Before deploying of any new version of Eftsure inside Dynamics 365, we highly recommend the following steps to ensure Eftsure packages are safely deployed all the way to Live environments.
This step is where most deployment support tickets get created, please follow steps below.
Clean Packages
Database synchronisation will not be required until after the new packages are deployed.
We recommend cleaning packages before any attempt to deploy any new version of any Eftsure package. To clean packages, Kill the following processes:
- D365 batch (batch)
- IIS Service (w3wp)
- IISExpress (iisexpress)
- xppcAgent (xppcagent)
Then delete the following any of the Eftsure packages / folder, if they exist in AOSService\PackagesLocalDirectory folder:
- Eftsure,
- EftsureInsideExFlow,
- EftsureInsideXe,
- EftsureInsideTAS,
- EftsureInsideCorpay,
- EftsureProjectManagement
Make sure the folder no longer exists on disk,
Disable Gated Checkins if necessary
Checkin deleted folder, make sure folder has been deleted from DevOps.
Enable Gated Checkins if necessary