We recently had two applications that did not trigger on schedule saying that the event did not have adequate security privileges to trigger the application. Error received: Event XXXX did not trigger application XXXX at XXXX. Unable to process your request. Ensure you have adequate security privileges.
CA Workload Automation DE (dSeries)
The Event authorization failed when executing the Event due to the user the Event used to trigger the Application does not have appropriate permissions.
The Event's execution or trigger user should have the appropriate permissions on the application. By default, the server uses the name of the user defining the Event as the Event prefix and execution user.
You can set up the default Event prefix on the Desktop Client main menu; Click Window, Preferences, Desktop Client, Services Perspective, Event, and enter the default prefix in the Prefix field.
Also, In Event properties, you can either specify the Execution user or check Inherit trigger user option.
This explains the Execution user or Inherit trigger user in Event properties;
(Optional) Specifies the execution user of the Event. When the Event is triggered, the Application triggered by the Event runs with the security permissions of the execution user.
Default: Name of the user defining the Event
Inherit trigger user
- When the Event triggers, the execution user requires the appropriate permissions to read the Application triggered by the Event.
- When each job runs in the Application, the execution user requires the appropriate permissions to run the job on the agent and to read any global variables specified in the job.
Overrides the execution user for Events triggered manually. If this option is set, the execution user is set to the user that manually triggered the Event.
Note: (Desktop Client only) To apply this option to all the Events you define, from the main menu click Window, Preferences, Desktop Client, Services Perspective, Event, and select the Inherit trigger user check box.