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


mbartosh
2010-06-16T22:47:17Z
Visualcron 5.6.0. I have setup an eventlog trigger that is pointing to another server which is our sql server. I have been able to trigger a job on the local server, but when I specify the SQL server, the job does not trigger. I am using domain admin credentials, so credentials should not be an issue. I have narrowed the trigger criteria down to just application log and type: information. The trigger is set to look at the eventlog on the remote server every 30 seconds.

Has anyone gotten this to work? Is this a bug with this version.

Another problem I have is that there is no log that indicates that the job has even attempted to try to access the remote server to check the eventlog.
Sponsor
Forum information
Support
2010-06-17T22:47:19Z
We have forwarded this case our developers for testing. We will get back to you soon.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
mbartosh
2010-06-18T00:20:38Z
Thank you. Do you know if the eventlog function was working in an earlier release?
ErikC
2010-06-18T08:22:20Z
I had no trouble to access the log of an other sql server.
see this post 

Regards
Erik
Uses Visualcron since 2006.
mbartosh
2010-06-18T14:36:29Z
What version of Visualcron are you using? I am using 5.6.0.
Support
2010-06-19T14:49:35Z
1. have you tried to run the service as a local user? After some tests we found out that a special permission is required to access remote computers (using WMI technology). We are currently trying to track down which one.

2. we have looked back in previous versions and there is no change in remote WMI behaviour.

3. If your trigger has failed once it is deactivated. You need to activate it again. You can see the current status in "Next run" column.

4. Try using no filters on the event log. Then try to stop and start a service on the remote computer. You should then see that "Last run" has been updated (unless you are using a Condition) on the Job that prevents running the Job.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top