Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


nirchi
2010-07-27T22:00:24Z
Greetings,
I am attempting to create and run a job with an event log trigger and having what seem to be permissions issues. When I attempt to save the job, I receive the following "Message from server" pop-up error box:

A trigger was inactivated due to an error: Unhandled error in EventLog event (4): Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) The trigger was connected to the job: <my job name>

The VC Server (Server A) resides on Domain A. The Event Log I am attempting to watch/trigger with this job resides on Server B on Domain B. The job is using user credentials for a Windows domain account (UserA@DomainA) on Domain A. Server B is running Windows Server 2008 R2 and the windows domain account has been added to the local "Event Log Readers" group on Server B.

What's odd is I can pull up the Event Viewer console on Server A and connect to Server B's Event Log without a problem.

Is there a cross-domain issue here or is there some other permission(s) I need to set on Server B in order for the VC event log trigger to work against the remote machine?

Thanks in advance!
Nirchi
Sponsor
Forum information
Support
2010-07-27T22:08:51Z
For some reason the Local System account needs to be a member of Administrators group when doing this. So, you need to add the System account to that group. This requires a restart.

Another alternative is to change the user that runs the VisualCron service to a user that already belongs to that group.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
nirchi
2010-07-28T17:17:01Z
Henrik,
Thanks for the quick response.

Making UserA@DomainA the owner of the VisualCron service and adding UserA@DomainA to the Administrators group on Server B did the trick; however, Server B is a production server. There are some security concerns around giving User A administrator privileges on server B.

I'm not sure I fully understand why UserA@DomainA needs to be a member of Server B's Administrators group in order for this to work.

Are there any other options that are less of a security risk?

Nirchi
Scroll to Top