I've never heard of or had this problem, and I run multiple once a minute cron jobs from Witango.
If you can reproduce your production environment exactly and not have the same result, then I suspect that your production environment may have a problem. Check the revisions on all the files, or do a fresh install. And try deleting and recreating the cron.ini. You may also try moving the once a minute job to the top or bottom. If none of that shakes out the problem, you should send your Witango/server folder to WT, however if they (or you) can't reliably reproduce the error it's going to be rather difficult to figure out what is wrong. It may also be a system resource, but that thought does seem a little unlikely. Robert -----Original Message----- From: Fogelson, Steve [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 07, 2004 11:09 PM To: Witango User Group (E-mail) Subject: Witango-Talk: Crontab problems Windows 2003 Web Edition, R:Tango .062 (Standard Edition), Oterro 2.6 and 3.0 Pentium IV Single 2.8 MHz Xeon w/ Hyperthreading enabled - 1 gig RAM I am having trouble with crontab entries that are set to run every minute. They always give an "unrecoverable os exception" after the "crontab entries are parsed". Occasionally it causes Witango to restart, all of the time it eventually finishes the restart process. The taf runs fine after the server "started excepting user requests". If I remove the entry that runs every minute from the crontab file, Witango starts without any of the above mentioned errors. I thought it might be related to a ODBC action, so I reduced the taf to just an exit action and it still has the problem. Recently I had to setup another test server. I copied the same sites, tafs, config, crontab, etc to this test server. The Witango startup runs with no errors on this server. But the server is quite a bit slower P III dual 700 MHz - 1 gig RAM with Windows 2000. My questions are: 1) Is anyone having similar trouble with crontab entries that run every minute? 2) Could this be processor speed related? Witango tries to process crontab entries before it should (in the startup process)? 3) Could this be platform related? Win2K vs. Windows 2003 Web Edition. 4) Could this be Witango related? And may have been fixed in .065 or 5.5 Beta. 5) Any other ideas? Thanks Steve Fogelson Internet Commerce Solutions ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
