By default, if a Windows service takes longer than 30 seconds to start, the system
warns 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 within 30 seconds can cause the service to stop. If an AOS repeatedly
does not start, you might want to configure the registry to give Windows services
more time, such as 120 seconds, to start before prompting with an error that a
service did not respond to a start command.
WARNING: This section contains steps that tell you how to modify the registry.
Be aware that serious problems might occur if you modify the registry
incorrectly. It is recommended that you back up the registry before you modify it.
If a problem occurs, you can restore it.
Regards,
Hossein Karimi
AX,365,NAV(tutorials: tips and tricks)
Sunday, July 22, 2018
Post-Install Recommendation
+10 years of experience with hands-on lead-level background in the full life cycle of software development with demonstrated cross-functional team leadership skills.
Programming:
• ERP :Microsoft Dynamics AX 2012
• Language :X++, C#, C++, XAML, Asp.Net, Html, VB.Net, Android
• Environment : Windows XP, Windows 8, Windows 10, Windows Server
• DataBase : Oracle 9i,10g,11g and SqlServer and SQLlite
Subscribe to:
Post Comments (Atom)
-
In Reporting Services, reports and resources are processed under the security identity of the user who is running the report. If the report ...
-
The below select query will give the both the Sales Line record count and the sum of sales quantity. static void Test_Data(Args _args) ... -
To integrate Microsoft Dynamics AX and Analysis Services, you must connect Analysis Services to the Application Object Server (AOS). To do s...
No comments:
Post a Comment