Hello,

Here is an excerpt from AutoRun.tg I was using with WinCron v3.6:
--------------------------------
#
{
-start -time 10:00:00 AM
-command o:\1.bat
-action -inc 1 0 0 0
}

#
{
-start -time 11:05:00 AM
-command O:\2.bat
-action -inc 1 0 0 0
}

{
-start -time 11:34:00 AM
-command O:\3.bat
-action -inc 1 0 0 0
}

{
-start -time 2:34:00 PM
-command O:\4.bat
-action -inc 1 0 0 0
}
--------------------------------

I've installed WinCron v4.2 and changed the lines in AutoRun.tg as follows:
--------------------------------
#
{
-start -cron 0 10 * * *
-command o:\1.bat
}

#
{
-start -cron 5 11 * * *
-command O:\2.bat
}

{
-start -cron 34 11 * * *
-command O:\3.bat
}

{
-start -cron 34 14 * * *
-command O:\4.bat
}
--------------------------------

The jobs do not fire on WinCron 4.2 with the new syntax. Is there something wrong with my script?

Thanks for your help!

-Rob

For good measure, I have removed the code from AutoRun.tg and put it in User.tg. I've also added a "-name" to each function.

After restarting the wincron service, the jobs still do not fire.

Would it be possible for you to copy/paste the results from the wincron status window here?

That's really odd that nothing is running. I would like to analyze the output.

How do I open the status window when WinCron is run as a service?

I see no icon in the system tray.

If you are running it in LocalSystem, you should see the little WinCron clock in the systray; double click that.

If you are running WinCron in a USER account (as a service) we'll need to add a logfile directive to start logging to a file.

You would add this as the first job in User.tg.

{
-start -once
-action -logfile "c:\wincron.log"
}

here's a test to run...

In user.tg, put the following:

{
-start -once
-action -logfile "c:\wincron.log"
}

{
-start -cron * * * * *
-action -print "Fire job at %c%"
}


Then use the Control Panel to Stop the WinCron service, then restart it.
You can then list the wincron.log file to see what's going on.

I just did it and this is what it looks like:

Z:\>type c:\wincron.log
Trigger:JOB:227: Thursday, February 05, 2004 13:56:12.
Trigger:JOB:228: Thursday, February 05, 2004 13:56:12.
Fire job at 02/05/04 13:56:12

Z:\>

It is running under a USER account.

I've added (to User.tg) the exact code you provided in your last post.

I've stopped and started the WinCron service out of Control Panel.

No log file was generated!

Hmm. this is really odd.

Would it be possible to rerun these tests from the LocalSystem account? I'm interested in what the WinCron display has to say.

I think we're on to something...:

Text flys by in the status window and then:

WinCron.exe Exception: access violation (0xc0000005), Address: 0x77f64d8a

I try again and this time it did not give me an access violation, however this is what showed up in the status window:

--------------------
Ready.
Completing WinCron installation...
WinCron installation complete.
Running as user 'Administrator' in account 'SYSTEM'
Using email profile 'Seagate'
-+-+-+-+-+-+-+-+
Config.tg: Environment setup complete.
Loading c:\progra~1\tomase~1\wincron\autorun.tab.
1 jobs loaded.
Running as SYSTEM
AutoRun.tg: Complete.
Checking for WinCron update at 02/05/04 17:25:01...
Error in file c:\progra~1\tomase~1\wincron\System.tg
Error: Object doesn't support this property or method: 'objNodeList.nextNode', ; in line 99
Abort called.
Stopping...
Engine Stopped.
--------------------

Is it a good guess that something didn't go well with the upgrade from 3.6 to 4.2?

Also, do a Start/Run:
"C:\Program Files\Tomasello Software\WinCron\WinCron.exe" -application

And let it run for 5 min.. then copy/paste the results here.

"C:\Program Files\Tomasello Software\WinCron\WinCron.exe" -application

Same result as in my last post.

Ah, I understand what happened.
The Microsoft component on your system "Msxml2.DOMDocument", is old. It certainly shouldn't crash, but that's the problem.

Here are the workarounds...

1. (short term) Find this line in System.tg and comment it out.
   If CheckTime(205, false, "%SYS.MINUTE% %SYS.HOUR% * * %SYS.DOW%") Then Return("WinCron Update")
   -- like this --
   #If CheckTime(205, false, "%SYS.MINUTE% %SYS.HOUR% * * %SYS.DOW%") Then Return("WinCron Update")
2. Update your copy of "Msxml2.DOMDocument".
   I'll post a link here after I find it.

Either one of the above should solve your problem.

In the mean time, I'll spin a new WinCron build that includes an updated version of the Microsoft component "Msxml2.DOMDocument".

I apologize for the slipup. I thought all versions of the "Msxml2.DOMDocument" object were compatible

Could you please tell me what OS you are running and version level. Do you keep up to date on all your patches?

Luke, thanks so much for all of your help!

I've commented out the line and it seems to be working just fine now. I'll know for sure tomorrow morning when a live job runs.

We try to keep as up to date as we can. Sometimes we have to use an outdated OS to accomodate old software.
So, here is the version (according to Control Panel/System):

Microsoft Windows NT 4.00.1381

Thanks again!

-Rob

I appreciate your patience on the matter.

Almost certainly NT’s version of this component (if it even exists) is way out of date.
I should have a patch that includes this component shortly. Please watch for WinCron 4.2.1

Rob,

Okay, WinCron version 4.2 has been patched to include the MSXML library. Please download WinCron here and all will be well.

Thank you again for reporting this.

Luke,

I thought I'd do some Q/A for you since I'm sure you don't have a similar system to test on.

Although we did not need to patch (commenting out works fine), I've gone ahead and installed the patched version of WinCron 4.2.

After uncommenting the line and restarting WinCron, I am still experiencing the same error as before.

If you release a second patch for this problem, I'd be happy to test it for you once more.

-Rob

Great!

WinCron version 4.2 (release 2) has been patched to include the MSXML 4.0 library. Please download WinCron here and test.

Let me know what you find.

I reproduced the problem you were seeing on one of my test machines and was able to verify that the WinCron Version 4.2 (release 2) fixes the problem.

You should be good-to-go now.

Thank again.