Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I have two AOS instances, and batch group linked to both AOS, how can I make a batch to run on both AOS's, whenever AOS1 is down to run on AOS2 and vice versa, because it is only working on AOS2 despite that batch group is linked to both AOS.
It seems you posted in a very old discussion and your question was not directly related to that discussion. I separated your question into it's own thread.
Do you have batch processing enabled for both AOSes in Server Configuration form in System Administration module?
Thanks a lot Nikolaos for your reply and for separating my thread, yes both instances are selected as batch servers.
Does it by default routes the batch job to second AOS incase the first is stopped and vice versa ?
All AOS servers that are configured as batch AOS will look for Waiting batch jobs that have such batch group that is configured for processing for that AOS.
So nothing is routed from the first AOS to the second AOS. Both AOSes just look for batch jobs that they could start processing.
Thanks a lot Nikolaos, we had to do full CIL on AOS1 in order to run batch jobs on it, it was not running batches before of previous failed CIL.
That's true, the batches won't work if you don't have any CIL generated. I wonder how you could have failed CIL in your prod environment but still were using it for actual operations. Definetely asking for trouble.
Seems your environment maintenance process has some flaws if your one AOS didn't have functional CIL and the other did.
When you deliver code to prod, you must shut down all AOSes. Assuming you use modelstore delivery (MS recommendation) all AOSes get the CIL from model database when they start. If you use some other delivery process, you must run full CIL generation on one AOS, and all other AOS instances must be switched off. After succesful CIL generation, you start other AOSes and they fetch the CIL from the model database.
If you fail to do this, you face issues like the one you had. Or some AOSes run different CIL version than others.
Thanks a lot again Nikolaos for clarifying the CIL, yes we were only generating CIL on one instance without turning off the other instance.
Business Applications communities