I tried to set up an event trigger, and as soon as it was added, it caused a VC restart every time it tried to reload the jobs. This is the error as it appeared when the trigger was added. (I had to copy backups of the settings files into the settings folder to get the server up long enough to connect to and to do a proper import, since it would load some of the settings but not others.)

7/16/2009 5:46:30 AM Err An unhandled error has occured (please send the information below to support@visualcron.com):

Server version: 4.9.26.36962 - (2008-09-07)
Protocol: 5.0.0
OS: Windows2003


System.Management.ManagementException: Invalid parameter
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementPath.SetWbemPath(IWbemPath wbemPath, String path)
at System.Management.ManagementPath.CreateWbemPath(String path)
at System.Management.ManagementPath..ctor(String path)
at System.Management.ManagementScope..ctor(String path, ConnectionOptions options)
at 4gT4OrzWH2fLQyOhmU.GIB2bEB3soYeYXNkxi.sn2KsHhl2k()
at 3rDVf39RgyXEIx7sBCw.BYIp5Q9lmxW18wjM9c1.Z9e9bTS2h()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
7/16/2009 5:46:30 AM Debug Starting restarter...

Do you have any ideas what might be causing the problem? Given the difficulty it causes, it's hard to just try tweaking the trigger one way or another to see what works.

What kind of event Trigger is it?

---

Sorry - it was an event trigger to monitor the Event log for an error.

It seems to work ok on our test server running version 5 - I haven't tested it extensively yet, but at least it doesn't instantly crash visualcron upon activation, which looks promising. I'll let you know we encounter any further issues with it.

I think I see what happens with the trigger that leads to the VC restarts - this happened on v5 as well, after I had done some fiddling around with the trigger. I had been testing it with both the local and a remote event log, and it looks like perhaps when changing back and forth, it can cause some problems. Perhaps, once the trigger is created for either local or remote, the same trigger shouldn't be modified to the other?

Can you post your settings here and we will try to reproduce it.

---

I emailed the settings; I didn't get the customary automated response, and just want to make sure that you get it.