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

For reference purposes, I first posted this problem on Monday, December 15, 2008 7:58 AM. Although I've been using a workaround (namely, using VC in a virtual machine on my host machine), I can no longer continue using it this way. It's too cumbersome and hard on resources.

To restate my original problem: whenever I attempt to use a simple process event trigger using one of the listed processes currently running on my machine, I get this error message:

Error message: A trigger was inactivated due to an error: Not supported The trigger was connected to the job: Test1

My setup:

Visual Cron Version: 4.9.40
Build: 21541
OS: Windows XP Home with latest service packs/patches
I log in as one of two administrators in an administrator account
WMI working as tested per your instructions

(Note: I don't know if this is relevant or not, but just in case: I forgot to deactivate VC when I did a complete reformat and re-install of Windows XP on the same machine last year. When I re-installed VC, it notified me that the trial had expired and the activation code I trying to re-activate, was already activated. I contacted you, had my original activation code deactivated, and re-activated VC as per instructions. It re-activated with no problem, except the one I'm presenting here. I don't know if these two events are related.)

I've attached a series of screen shots (File: VC4_9.jpg), numbered consecutively from 1 to 4, the order in which I carried out the operations to activate this trigger.

You have a terrific product, and I would be most grateful if you would revisit this minor problem with me and help me solve it.

With regards,

Glen Petrant

gpetrant attached the following image(s):
Forum information
Scroll to Top