web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Window could not start the Microsoft Dynamics AX Object Server 6.3$01 on local computer

(0) ShareShare
ReportReport
Posted on by 670

ERROR: the service did not respond to the start or control request in a timely fashion 

if anybody know this solution please help us 

aos-is-not-running.PNG

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Rohin Profile Picture
    4,624 on at
    RE: Window could not start the Microsoft Dynamics AX Object Server 6.3$01 on local computer

    Can you tell us whats your service status? it should be starting and takes some time to start.

    Please see below thread :

    community.dynamics.com/.../119241

  • account payable Profile Picture
    670 on at
    RE: Window could not start the Microsoft Dynamics AX Object Server 6.3$01 on local computer

    service status in Starting

  • Rohin Profile Picture
    4,624 on at
    RE: Window could not start the Microsoft Dynamics AX Object Server 6.3$01 on local computer

    Is this still in starting status. Please tell us more details like what you did before stop the services?

  • account payable Profile Picture
    670 on at
    RE: Window could not start the Microsoft Dynamics AX Object Server 6.3$01 on local computer

    before stop the services i did restart computer after that showing like this "service did not respond to the start or control request in a timely fashion "

    I already add ServicesPipeTimeout to regedit, but still not working

    Any other suggestion for this problem?

  • Verified answer
    account payable Profile Picture
    670 on at
    RE: Window could not start the Microsoft Dynamics AX Object Server 6.3$01 on local computer

    Finally I did my self

    now its AOS is running,please following my detail how to run for AOS  

    Method 1:

    I suggest you to modify the registry to increase the default time-out value for the service control manager. To increase this value to 60 seconds, follow these steps:

    1. Press Windows Key + R, type regedit, and hit enter.

    2Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

    3. In the right pane, locate the ServicesPipeTimeout entry.

    Note If the Services PipeTimeout entry does not exist, you must create it. To do this, follow these steps:

    a. On the Edit menu, point to New, and then click DWORD Value.

    b. Type ServicesPipeTimeout, and then press ENTER.

    4. Right-click Services PipeTimeout, and then click Modify.

    5. Click Decimal, type 60000, and then click OK.

    This value represents the time in milliseconds before a service times out.

    6. Restart the computer.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Tocauer Profile Picture

Martin Tocauer 4

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 3

#3
Willem van Duren Profile Picture

Willem van Duren 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans