Question Status

Suggested Answer
Tony YW asked a question on 18 Feb 2013 11:32 AM

 I tried to install Dynamics AX 2012 R2 on a stand-alone configuration.  All pre-req were met.  However, after about 20 minutes the installation failed with following error.   I can't find anything in the event log other than this statement:

Installation of component "Trace Parser" failed. Review the log file "C:\Program Files\Microsoft Dynamics AX\60\Setup Logs\2013-02-17 22-09-27\DynamicsSetupLog.txt" for details.

Here is the relevant part in the DynamicsSetupLog.txt file.

 

2013-02-17 22:24:31Z Registering tracing manifest file "C:\Program Files\Microsoft Dynamics AX\60\Server\Common\TraceProviderCrimson.man".
2013-02-17 22:24:31Z WEvtUtil.exe install-manifest "C:\Users\TUser2\AppData\Local\Temp\tmp40EA.tmp"
2013-02-17 22:24:35Z  **** Warning: Publisher {8e410b1f-eb34-4417-be16-478a22c98916} is installed on
2013-02-17 22:24:35Z  the system. Only new values would be added. If you want to update previous
2013-02-17 22:24:35Z  settings, uninstall the manifest first.
2013-02-17 22:24:35Z  
2013-02-17 22:24:35Z  
2013-02-17 22:24:35Z Tracing manifest file has been registered successfully.
2013-02-17 22:24:35Z Component installation task completed successfully.
2013-02-17 22:24:35Z Waiting for the Application Object Server to start ...
2013-02-17 22:34:35Z ******************************************************************************************************

2013-02-17 22:34:35Z Component installation task stopped due to an error.

2013-02-17 22:34:35Z ******************************************************************************************************
2013-02-17 22:34:35Z ******************************************************************************************************

2013-02-17 22:34:35Z An error occurred changing the status of the service 'AOS60$01' to 'Running'. See the event log for more details.

2013-02-17 22:34:35Z ******************************************************************************************************
2013-02-17 22:34:36Z ******************************************************************************************************

2013-02-17 22:34:36Z Microsoft.Dynamics.Setup.AxSetupException: An error occurred changing the status of the service 'AOS60$01' to 'Running'. See the event log for more details.
2013-02-17 22:34:36Z    at Microsoft.Dynamics.Setup.Components.Aos.StartStopService(Boolean start, Boolean setErrorOnException, Boolean waitForFinish)
2013-02-17 22:34:36Z    at Microsoft.Dynamics.Setup.Support.SetupQueue.WaitForAOSIfNecessary(IEnumerable`1 componentsToCheck)
2013-02-17 22:34:36Z    at Microsoft.Dynamics.Setup.Support.SetupQueue.HelpServerInstaller.AosStatusHealthy()
2013-02-17 22:34:36Z    at Microsoft.Dynamics.Setup.Support.SetupQueue.HelpServerInstaller.HelpServerMsiInstall()
2013-02-17 22:34:36Z    at Microsoft.Dynamics.Setup.Support.SetupQueue.HelpServerInstaller.PerformWork()
2013-02-17 22:34:36Z    at Microsoft.Dynamics.Setup.Support.SetupQueue.InstallationClass.DoWork(Object sender, DoWorkEventArgs e)
2013-02-17 22:34:36Z    at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

2013-02-17 22:34:36Z ******************************************************************************************************
2013-02-17 22:34:40Z S260FinishedInfo

Please let me know what is wrong. 

Thanks.

 

Reply
Suggested Answer
Tommy Skaue responded on 27 Feb 2013 6:05 AM

It probably just timed out while it was indexing. Default settings for how long Windows will wait for a service to start before returning a "timeout" to the calling program is normally too low for the AOS. The installation guide explains how to increase this timeout, but for your convenience please take a look here:

technet.microsoft.com/.../ee355089.aspx

Installing the components in a "controlled" order is a good strategy too. :-)

Tommy Skaue | Dynamics AX Developer from Norway | http://yetanotherdynamicsaxblog.blogspot.no/ | www.axdata.no

Reply
Martin Dráb responded on 18 Feb 2013 10:13 PM

The log says: "An error occurred changing the status of the service 'AOS60$01' to 'Running'. See the event log for more details."

So... do you see details in the event log? Are you able to start the AOS?

Martin "Goshoom" Dráb | Freelancer | Goshoom.NET Dev Blog

Reply
Francisco Silva responded on 20 Feb 2013 4:28 AM

Hello Tony!

Do you have administration rigths in the server where you are installing AX? Does The AX Service Account have administration rigths in this server?

The best way to install AX is installing first the "Databases", "Application Object Server (AOS)" and the "Client" componentes. Will be better to find problems.

Dont forget to mark this as answer!

Francisco Silva | | http://fsilvajunior.blogspot.com.br

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply
Tony YW responded on 25 Feb 2013 4:43 PM

Sorry, I was pulled to do something else.  Now I am back to this task again.  

Once again, I am doing an installation on one machine.  It always failed at creating AOS.  Now after it failed, I rebooted the machine and I could see AOS service is running in the service manager.  So I went ahead.  Now I am in the step of Compile Application.  I got an error:

An unhandled error has occurred.  To view details about this error, enable debugging in the web.config file or view the Windows event logs.  Windows event log has an error stating The X++ web session initialization failed.  Please make sure the checklist has been run.  I am not sure what checklist this is referring to.  And I do not know how to modify the web.config file in order to show more verbosed details.  By the way, I located the web.config in C:\Program Files\Microsoft Dynamics AX\60\Setup\EPDeploymentService.  Is this the correct web.config?

Thanks for your suggestion.

Tony

Reply
Pradeep Itnal responded on 27 Feb 2013 4:29 AM

Agree with fsilva-jr, Install Ax , component by component. First install DB, AOS, Client. Then Debugger, Visual Studio AddIns.

Reply
Suggested Answer
Tommy Skaue responded on 27 Feb 2013 6:05 AM

It probably just timed out while it was indexing. Default settings for how long Windows will wait for a service to start before returning a "timeout" to the calling program is normally too low for the AOS. The installation guide explains how to increase this timeout, but for your convenience please take a look here:

technet.microsoft.com/.../ee355089.aspx

Installing the components in a "controlled" order is a good strategy too. :-)

Tommy Skaue | Dynamics AX Developer from Norway | http://yetanotherdynamicsaxblog.blogspot.no/ | www.axdata.no

Reply