After you install an AOS instance, you must wait for the Microsoft Dynamics AX Object Server Windows service to start.
By default, if a Windows service takes longer than 30 seconds to start, the system displays a message informing you that the service did not respond to a start command. The AOS Windows service can take longer than 30 seconds to start, and the lack of a response in 30 seconds can cause the service to stop. Therefore, if an AOS instance repeatedly does not start, you may want to configure the registry to give Windows services more time, such as 120 seconds, to start before the error message is displayed.
Be aware that serious problems can occur if you modify the registry incorrectly. We recommend that you back up the registry before you modify it. If a problem occurs, you can restore it.
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey: \HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control
- Right-click Control, and then click New > DWORD (32-Bit) Value.
- Right-click the new key, and then click Rename. Enter the name ServicePipeTimeout.
- Right-click the key again, and then click Modify.
- In the Value data text box, enter 120000, and then click OK. The AOS Windows service now has 120 seconds to start before the system displays an error message.
If the AOS instance does not start after you implement this registry key, use the Microsoft Dynamics AX Server Configuration utility to verify that the AOS instance is using a unique port. Port conflicts prevent AOS instances from starting.