A user experienced an error when running an automated action with EventID 5005 due to UAC being enabled. The user then ran the action as a specific user that had rights to start VMs in vCentral, and it was suggested that the action could be run from a Monitor server instead. Any logs can be shared by opening a ticket or in private with support. ControlUp has a log4net script action available to investigate this issue further. The registry key EnableLUA will be read if the script is set to "controlup console/monitor".
Read the entire ‘Investigating Automated Action Error with EventID 5005 in ControlUp’ thread below:
Running an automated action fails with EventID 5005
Error: Automated action execution failed run because User Account Control (UAC) is enabled on this computer which is running ControlUP Monitor.
UAC is indeed enabled and there is no chance to disable UAC!
I am pretty sure I ran auto actions at customers with enabled UAC.
you running this script action as a specific user and is that user logged on to the machine?
Yep for the specific user.
No for logged on on the machine (assuming you mean Monitor)
Because the Script is using PowerCLI I selected the user with the rights to start VMs in vCenter…it might not be related to uag at all and that the error is incorrect, can you grab an agent log4net?
Sure, is there a chance you can pass over an cuAgent.log4net file? I just have Console and Monitor log4net in the toolbelt
But… Isnt the auto action fired by cuMonitor.exe?yes but running it is done via the agent
@member you got an agent log4net for Markus?
Debug level set to verbose in this one, so it might be very chattyAwesome! Thank you.
Yeah I will send it to the customer so I assume I open a ticket with the output.
@member there is a new log4net script action available in the library! Very easy. Just run it on a cuagent.exe process or cumonitor process and it will start and stop automatically
once you have the log4net logs you can share them in private with me or open a support ticket with it. Please don’t share them in public.
if the script action is set to "controlup console/monitor" then the following registry key is read:
> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA
If that value = 1 or true, then the script action will fail with the error message you mention.
Honestly, I don’t really know why this was put in place.
Great find Dennis! Thanks.
We will switch the script from "controlup console/monitor" to run it from an monitor server. Do you see if that will also read this reg key?
if you pick a specific machine, the registry key will no be a factor
Continue reading and comment on the thread ‘Running a ControlUp Automated Action fails with EventID 5005’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers