Release : 11.5
Component : CA Automation Point
To monitor any remote Windows server events created by an application, Automation Point (AP) requires that the event messages dll for the application be registered locally on the AP server.
To enable successful event monitoring for the previous version of SolarWinds Orion these steps had been done:
1. Copied the Orion EventLogMessages.dll from the Orion Server to the AP Server.
2. On the AP server under registry key "HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application" created a new sub-key with the name of the Source/Provider Name ("Alerting Engine") . Under the new sub-key added an Expandable String Value (REG_EXPAND_SZ) with name "EventMessageFile" assigned to the full path of the EventLogMessages.dll file.
The Orion upgrade added an additional component "SolarWinds.BusinessLayerHost Action" resulting in the AP server errors "The description for Event ID (3003) in Source (SolarWinds.BusinessLayerHost Action) could not be found ...".
To resolve the problem a new registry key similar to above was created for the new component i.e.
Under "HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application" create new sub-key with the name of the new Source/Provider Name "SolarWinds.BusinessLayerHost Action" and under that new sub-key add an Expandable String Value (REG_EXPAND_SZ) with name "EventMessageFile" assigned to the full path of the EventLogMessages.dll file.