You’re offline. This is a read only version of the page.
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
Computer:
Description:
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
%%90
The resource loader failed to find MUI file
Event Xml:
<Event xmlns="schemas.microsoft.com/.../event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7024</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2015-05-28T10:25:18.300426900Z" />
<EventRecordID>66834</EventRecordID>
<Correlation />
<Execution ProcessID="748" ThreadID="836" />
<Channel>System</Channel>
<Computer>Live-Envi.sanaco.com</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">Microsoft Dynamics AX Object Server 6.2$01-MicrosoftDynamicsAX</Data>
<Data Name="param2">%%90</Data>
</EventData>
</Event>
*This post is locked for comments
I have the same question (0)
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.
regards
Douglas
Share
Report
All responses (
Answers (
3,905
