SBX - Search With Button

SBX - Forum Post Title

Error while starting AOS: the service did not respond in a timely fashion

Microsoft Dynamics AX Forum

Ysrael Fortuno asked a question on 28 May 2015 5:55 AM
My Badges

Question Status


Hi Guys,

Good Day!

We're having trouble on starting AOS, here's the error message "the service did not respond in a timely fashion"

********* Event Log  ***************

Log Name:      System
Source:        Service Control Manager
Date:          28-May-15 1:25:18 PM
Event ID:      7024
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
The description for Event ID 7024 from source Service Control Manager cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Microsoft Dynamics AX Object Server 6.2$01-MicrosoftDynamicsAX

The resource loader failed to find MUI file

Event Xml:
<Event xmlns="">
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7024</EventID>
    <TimeCreated SystemTime="2015-05-28T10:25:18.300426900Z" />
    <Correlation />
    <Execution ProcessID="748" ThreadID="836" />
    <Security />
    <Data Name="param1">Microsoft Dynamics AX Object Server 6.2$01-MicrosoftDynamicsAX</Data>
    <Data Name="param2">%%90</Data>

Douglas Noel responded on 28 May 2015 6:12 AM
My Badges

Hi Ysrael,

this message comes from the Windows ServerControlManager (SCM) always if changing the state (from stopped to runnijng, or running to stopped) will take more time than the current allowed limit (default on windows is 30 seconds).

Sometimes the AOS service need more than this 30 seconds. Just ignore this message. The service will going on starting.

If you don't like the message you can increase this 30 second default within the registry

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

create a DWORD value 'ServicesPipeTimeout' (or use an existing one) and specify the new limit using milliseconds.

e.g., 1 minute would be an decimal value oif 60000 to be entered.




SBX - Two Col Forum

SBX - Migrated JS