Yes, and as you can see sbbs is tryint to execute the command-line you specified, which as I recall, is executing a batch file. This is likely failing because you have "Native Executable/Script" set to "No" (as I previously stated and you quoted). Try changing that setting to "Yes".
Probably not, but if you determine the *context* of those errors (e.g.
by looking at the terminal server log output or the event thread log output), you could determine more about *why* those errors might've occurred. The error.log file alone is often not enough to root-cause an issue, it's just an indication that there is a problem and that you may have more research to perform to find and fix. --
Rob,
Yes, and as you can see sbbs is tryint to execute the command-line you specified, which as I recall, is executing a batch file. This is likely failing because you have "Native Executable/Script" set to "No" (as I previously stated and you quoted). Try changing that setting to "Yes".
Already tried that...no dice.
Probably not, but if you determine the *context* of those errors (e.g. by looking at the terminal server log output or the event thread log output), you could determine more about *why* those errors might've occurred. The error.log file alone is often not enough to root-cause an issue, it's just an indication that there is a problem and that you may have more research to perform to find and fix. --
I try to force the timed event to run, and all it does is give an error 255, and it quits.
Re: Re: Event Won't Run
By: Daryl Stout to Digital Man on Sat Jan 15 2022 08:47 pm
Rob,
Yes, and as you can see sbbs is tryint to execute the command-line you specified, which as I recall, is executing a batch file. This is likely failing because you have "Native Executable/Script" set to "No" (as I previously stated and you quoted). Try changing that setting to "Yes".
Already tried that...no dice.
What does the event log output say when that happens?
What does the event log output say when that happens?
Yeah, it wouldn't matter if it was at the scheduled time or forced, sbbs can't execute the command-line you've configured. You've messed it up some
Re: Re: Event Won't Run
By: Digital Man to Daryl Stout on Sun Jan 16 2022 02:45 am
Rob,
What does the event log output say when that happens?
Exited with Error Level 255.
I may end up doing a fresh install of 3.19b -- and that will take
awhile.
I went through the batchfile, and apparently I can sacrifice 5
doorgames, as their maintenance takes the longest time. Those
include local versions of Trade Wars 2002 and Trade Wars Services
(for version 2 of the game), Trade Wars Gold, VGA Planets, L.O.R.D.
II Complete New World (local) and Terra Firma. Those doors also
have gotten little usage recently, and there's a version of Trade
Wars 2002 Game Services on Valhalla BBS that's available for those
"needing a Ferrengi fix". I'm able to run a local version of L.O.R.D.
4.06 and L.O.R.D. II with no nightly maintenance issues.
There are also several other doors that do have maintenance, but
they don't take as long to run, and appear rarely used anyway.
I may end up doing a fresh install of 3.19b -- and that will take
awhile.
I went through the batchfile, and apparently I can sacrifice 5
doorgames, as their maintenance takes the longest time. Those
include local versions of Trade Wars 2002 and Trade Wars Services
(for version 2 of the game), Trade Wars Gold, VGA Planets, L.O.R.D.
II Complete New World (local) and Terra Firma. Those doors also
have gotten little usage recently, and there's a version of Trade
Wars 2002 Game Services on Valhalla BBS that's available for those "needing a Ferrengi fix". I'm able to run a local version of L.O.R.D. 4.06 and L.O.R.D. II with no nightly maintenance issues.
Re: Re: Event Won't Run
By: Digital Man to Daryl Stout on Sun Jan 16 2022 02:45 am
Rob,
What does the event log output say when that happens?
Exited with Error Level 255.
Native Executable/Script: No
Use Shell Or New Context: No
I'm asking you to paste the event thread log output at the time of the problem, just like I did here, as an example.
I may end up doing a fresh install of 3.19b -- and that will take
awhile.
I doubt that is necessary.
BTW, reviewing your configuration:
Native Executable/Script: No
Use Shell Or New Context: No
*Both* of those should be set to Yes when executing a shell script or batch file on Windows.
Like the SCFG help screen says (for the "Use Shell" option):
Rob,
I'm asking you to paste the event thread log output at the time of the problem, just like I did here, as an example.
I'll have to get that data off of the BBS computer...
as I reply to QWK
Mail off of another system. But, it basically won't let me create any new timed events...as all of them return an error level of 255 when I try to
run them.
I may end up doing a fresh install of 3.19b -- and that will take awhile.
I doubt that is necessary.
I decided just to zap the doors that took forever for their nightly maintenance to run. They weren't being used much anyway.
I'm asking you to paste the event thread log output at the time of the problem, just like I did here, as an example.
I'll have to get that data off of the BBS computer...as I reply to QWK
Mail off of another system. But, it basically won't let me create any new timed events...as all of them return an error level of 255 when I try to
run them.
I decided just to zap the doors that took forever for their nightly maintenance to run. They weren't being used much anyway.
Mon Jan 10 12:34:23 2022 master/a3cb54710
term Node 1 <Daryl Stout> !VDD WriteFile(0xf60, 1) FAILURE (Error=38)
Sysop: | Shaun Ewing |
---|---|
Location: | Blue Mountains, Australia |
Users: | 193 |
Nodes: | 16 (0 / 16) |
Uptime: | 163:53:09 |
Calls: | 143 |
Calls today: | 1 |
Files: | 187,815 |
Messages: | 324,321 |