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.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I know that the AOS can sometimes be slow to restart but I have noticed that on most of out AOS servers the restarts take so long that, a) I get an error: Windows could not start the Microsoft Dynamics AX Object Server 6.0... Error 1503: The Service did not respond to the start or control request in a timely fashion., b) I have to check/refresh the services list for another 5 minutes before the status moves from "starting" to "started". Rarely it will restart within a few minutes, no error messages.
Any idea what could be the cause of the 10 minute reboot cycle?
I have a similar issue. No reason found yet.
I think this is normal behavior, depending on the machines power and the application situation. Sometimes it takes only minutes, sometimes it takes some more minutes :)
If the AOS service detects that its xppIL directory is out of sync with the compiled objects stored in the database, it will purge the xppIL directory and re-download the entire directory again (2000+ objects) from the database. This process can take several minutes, and the detection process also seems to take several minutes. You can actually watch the files being downloaded. The xppIL directory is located under the server's bin directory.
This process is important for AOS clusters to keep their object code in sync between all of the AOS nodes. The compiled object code is stored in the database now which is shared among all AOS instances.
I am facing the same issue. Is anyone found the solution ? plz share your ideas here.
I know it is not much of a help for you guys, but I have heard that the AOS restart is much faster in the comming R3 release.
I do not think this is an issue as it is by design. It is also described in the installation guides that starting the AOS may take a while and that a message may appear that the service did not respond in a timely matter.
Can you explain why this is an issue for you? Apart from the somewhat longer downtime during a restart?
It is by design, there is little you can do about it. The only thing is: disable all unnecessary AIF services because these will also be recreated when CIL is out of sync.
Also only use the CIL Compile if necessary....
If the changes made are not batchable/AIF Services/Enterprise Portal/Workflow related, but only X++ why should you use CIL?
1. restarting a server which has just been restarted (CIL should still be in sync)
2. restarting a server after you deleted all files in XPPIL folder in the bin folder on server installionfolder.
you'll notice the difference in starting time 1 will be faster then 2. And 2 is what will happen if CIL is out of sync.
try below link
Do you know if there's any good documentation on the OOTB AIF Services? I'm hoping to go through figuring out what's safe to disable, but can't seem to find any documentation on what each service is used for, so can't predict what's safe to disable, or even what I'd need to test after disabling to confirm any ill effects.
Thank-you again / in advance.
As long as you don’t use any of the new stuff (retail pos, mobile apps etc) and you don’t administer your environment with use of these services.... you can actually stop them. Most of them will require some development because the service group will auto deploy them.
Business Applications communities