While installing AOS component in Ax 2012 R3, I came across this error:
After a couple of days untiring work I finally came to installed AOS component.
Problem: When the Dynamics AX 2012 AOS is installed, it is creates a new Eventlog for the Workflow Service i.e. Microsoft Dynamics AX Workflow, but in this scenerio it does not which is causing this problem as reported from log file.
Solution:
1. I opened log file, which specify this info
2017-09-12 11:10:11Z >>Install: 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. Name given: 'Microsoft Dynamics AX Workflow', name of existing log: 'Microsoft-Windows-Diagnostics-Performance/Operational'.
I was able to install the Dynamics AX 2012 AOS by renaming the existing conflicting Eventlog name from the registry editor:

Renaming as above would create 'Microsoft Dynamics Ax Workflow':

Now try installing AOS again, and enjoy your day :)
Comments
Post a Comment