Troubleshoot installation issues with AOS

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

The following section provides information that can help you troubleshoot issues that you may encounter when you install Application Object Server (AOS).

An error occurred during the install custom action step within the AOS Server installer

If the AOS installation fails, you may receive the following message: “An error occurred during the install custom action step within the AOS Server installer.” This error may indicate that the event logs on the computer have conflicting names. In this case, the following message also appears in the log file: “Only the first eight characters of a custom log name are significant, and there is already another log on the system using the first eight characters of the name given.”

When AOS is installed, an event log that is named Microsoft Dynamics AX Workflow is created for the Workflow service. The custom action in Windows Installer that creates the Workflow event log does not verify whether an event log already exists that has the same first eight characters in the name. If another application has already created an event log that has the same first eight characters in the name, the operation to create the Workflow event log may fail. Therefore, the custom action fails, and Windows Installer rolls back the installation.

To work around this issue, you can rename the conflicting event log and attempt to install AOS again. Event logs are listed as subkeys under the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog. After AOS is successfully installed, you can rename the conflicting registry key to its original name.