MS Dynamics AX object server 6.2 SERVICE (AX 2012) does not start-up automatically. You need to stop the service and again restart. We tried to insert a delay in the service start-up, but still the same problem persists.
Also when we stop the service, the service goes in the loop. The start & stop buttons are disabled and the only way to sort out the issue is to re-start the server.
Anyone is aware of the solution?
*This post is locked for comments
we call this a dependancy
1. Open the registry editor:
Start -> Run -> regedit
2. Navigate to the specific service you are trying to delay:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
3. If there is a “DependOnService” value, simply modify it and add the service you want to start before the one you are editing in the registry.
If no “DependOnService” value exists create one:
Right click service name -> New -> Multi-string value
Enter the name DependOnService then modify this new record and add the service you want to start before the one you are editing.
To verify you have the right service name to enter open up Services, right click the service in question, and choose properties. Use the Service name and not the Display name. For instance the IIS Admin Service name is “IISADMIN”.
4. The server will require a restart to apply the change. Once restarted you can open Services, right click the service you edited, choose properties, then the Dependencies tab and you will see the change.
Hi Pradeep
The AOS service depend from SQL Server and RPC.
You have one Server with both SQL and AOS ?
How much memory?
Usually, AOS Service don't go up because SQL is in starting.
Also, when the AOS Service starting, are updated the Assembly on XppIl folder.
So, try to check your AX Sizing.
As workaround, you can also build a powershell batch that start the AOS when SQL are available.
Regards
#1
André Arnaud de Cal...
292,468
Super User 2025 Season 1
#2
Martin Dráb
231,287
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
